UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
Hi,
I'm not sure that this is actually an APP problem but hoping you might be able to shed some light and/or suggest a workround.
For a long time I've been saving my APP-generated images as 16-bit TIFs then opening these in Abobe Camera Raw for final sharpening and denoising, then finally saving as PNG files.
All of a sudden I am seeing this error when I try to open my TIFs in Camera Raw:
I think this problem is probably more an issue with Camera Raw as I am now getting the same error message even when trying to open APP-generated TIFs that I know opened satisfactorily in Camera Raw in the past!
I've upgraded to latest Camera Raw (v13.3) shortly after I first saw this error message but this has not helped.
I've also tried saving APP files as 16-bit PNG and opening in Camera Raw but this approach also fails.
It seems this error has been a frequent problem with PS in the past but all the suggested solutions I've found thus far seem to involve opening the offending files in some other application and then saving them in an alternative format such as JPG.
The TIF files that Adobe is reporting as an issue all seem to open OK with apps such as IRFANview, ASTAP, and even Paint and Photos!
Any light that you can shed on this issue will be appreciated.
Mike
Hi Mike, sorry but you'd have to contact the developers of Adobe I think (not sure but they may have support tickets?). I've not seen people mention this specific issue, so my guess is that that specific application has had a change that breaks this particular data.
Hi,
Just a quick update in the hope that someone with more in-depth of knowledge/experience of Photoshop Camera Raw plug-in might be able to add some further in-sight.
Under Photoshop Edit Preferences/File Handling/Camera Raw Settings, there is a section for changing TIFF/JPEG file handling:
: by changing this option from 'Automatically open TIFFs with settings' to 'Automatically open all supported TIFFs', I now seem to be able to open my problem files but it seems only by right clicking the file in Explorer and using Open with...Photoshop.   Oddly, opening Photoshop and using the 'File/Open as..' menu item does not seem (always?) to work.
As I have not had this problem of opening 16-bit TIFFs in Camera Raw prior to Beta 3 I still feel something subtle has possibly happened in APP in this area.
While on the topic of TIFFs, I notice that the APP/Save file menu has added some more ICC profiles. As I don't have a wide gamut display I think only the sRGB options really matter to me but I am intrigued by the difference between sRGB v4 Preference and sRGB v4 Appearance.  Apologies if I've missed anything Mabula might already have said on this issue.
Mike
FWIW, Thanks to your advice I feel I somewhat on the way to more successfully combining Ha with LRGB data, and in using the new Star Reducer tool.
 Incidentally, is there a reason why Star Reducer tool on saving does not automatically add a suffix to the file name?
Regards
Mike
Â
Good to hear your processing is working better now! I don't have a great knowledge about the differences between those color profiles, I would have to look into that. For the star reducer, that's a good one indeed, I think it should be mentioned in the FITS header though, is it?
Hi Vincent,
The only difference between pre- and post-Star Reducer image in the FITS header that I see is in 'adaptive pedestal from data calibration'. In the instance I am looking at the value changed from 0.02285 to 1497.4747 which seems a very considrable amount but visually the image is OK.Â
Looking at the largest stars in my image post processing I see some processing artifacts which I guess is to a degree is inevitable if one knows what to look for. I imagine Mabula had some form of quality criteria in mind when he embarked on this extension. It would be interesting to know what standard he was expecting so as to see how well my use of the tool approaches the target!
Having become familiar with the APP way of adding suffixes to the file name after tool operation it seems inconsistent to me not to do the same with SR.
Regards
Mike
Ok, good point I'll pass this on to Mabula!
