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 guys,
thank you for the update! Â Great performance improvement. Â I see that there are many changes. Â I now also can see that the FITS files are only 72 dpi. Â Where can I change this? Â
I use both RAW Nikon Z6 - Olympus EM1 MkII (Camera) and FITS (ASI294MM). Â All produce more than 72dpi.
Any help appreciated.
Â
HendrukÂ
Â
@nordiclightphoto DPI is a measure for how many dots per inch will be used when printing an image. It has no effect on the actual file that is produced when saved. If you intend to print the images then you can convert them to TIFF and modify the DPI value with an external tool.Â
So Wouter, does that mean that I can leave it at 72 DPI in APP and not lose any data, then increase it before I save a final version if I will print it? I tested at both 72 & 300 DPI and saw that the file size seems identical. Or even leave it at 72 DPI and increase it in e.g. PS, if I am going to do some final touchups there?
Thanks. And I forgot to add that my first impression of the new features is fantastic - I just have to learn how to use them. I can already see that much more of my processing both should and is going to be done in APP than I have been! A great release...
@wvreeven Thanks Wouter. Â So what you are saying is that when I use a FITS file in PS / Affinity Photo (it can read FITS files) the resolution is not comprised? Â Or do I need to bump up the DPI in APP when exporting it as a tiff? Â I have seen that by the export you can increase the DPI.
In other words FITS is resolution independent? Â Â
@nordiclightphoto As a matter of fact, ALL image dimensions are DPI independent. DPI only defines how the image will be printed. Not how many pixels there are in the image. A higher DPI only means that the printed image will be smaller on paper. If the DPI is too low then you'll see the individual pixels on paper.
When processing astronomical images, the only thing that matters is the spatial resolution of the telescope/camera combination, how well guiding has been performed, seeing etc. But a camera always produces the same number of pixels and that number only changes if the camera is binned or if the image is scaled. DPI is completely independent of this.
