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,
What is the recommended way to non-destructively save a linear APP-image to continue image processing in another tool, like eg. PhotoShop or Affinity Photo?
Or put in another way, does saving a stretched image in APP always mean losing some of the original image information, and thereby limiting what can be achieved with further processing in other tools?
Currently in my workflow, I do the bulk of the processing in APP, (eg. Integrations, RGB combine and LPC) and after a light stretch, I save the image in a 32-bit TIFF format and continue tweeking the tiff-image in Affinity photo. Even though TIFF is a lossless format, I just want to verify if there is something to be gained from saving a non-streched image in tiff-format or even just use the the linear fits-file from APP directly as input to Affinity (which is an option). This certainly would require more work and your recommendations here would be very helpful.
Thanks,
Anders
Hi Anders,
Good question, I think stretching will remove data as the preferred way in APP is always to use the linear data. I asked Mabula for a double check on that. I'd say that if you can process linear in another package, I'd probably do that. But I'll see what Mabula has to say as well.
I’m still learning Affinity, but thus far I have gotten much better results when importing stretched tiff versus linear tiff.
I would be interested to hear your experience with linear files.
Yes, so you indeed do limit your data with stretching. However, it is a good starting point, usually, for touch-ups in another package as the stretching APP does may be somewhat better. But, if the other package is able to stretch, you can always compare both and try to make them produce the same result. If that works, I'd likely do that and then save the result in the other package to a stretched one.
Thanks Vincent and Jeff for your input.
After some further tests and comparisons, I tend to agree with you. Loading a linear fits-file and stretching it in Affinity, I have found it difficult to even come close to the result I’m able to achieve quite easily in APP.
So revising my thinking, it may be a good idea to make the most of APP stretching facilities that applies to the whole image before exporting to a tiff format. Importing it into Affinity is still very useful to be able to take advantage of powerful generic image processing features like layering and masking for further enhancements.
I do not use APP for any post processing. I create the stacks in APP and then combine and process the .FIT files in another piece of software.
