Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
Ok, I did try to search forums for this, but I have created a full library of darks, bias, bad pixel calibration files. My bias I use the same gain, my bad pixel I use at the same gain... and then my darks I have a huge assortment I made of various gains and exposure lengths.
Â
For example on my 1600mm, I have 139 gain @ 60 second exposures. I will add my bias, my dark, and my bad pixel map, and my flats if I have them. They are all 32b while my lights come in as 16b fits. Is this okay to do?
Â
I was trying to find the mean ADU of my bias and dark today for a calculator and while I was expecting it to be around 300-400 ADU. But I don't seem to find that with these 32b calibartions?
Â
in APP, my mean shows this.
Dark 139 gain @ 60s:Â 4.867E-03Â which would be .004867 ADU?
Bias 139:Â 4.551E-03 which would be .004551 ADU?
Â
How can I get the 16b ADU of this? or am I missing something? I saved them as 16b and it shows like 4000+ adu.
Â
My lights that are 139 gain @ 60s show a mean ADU of around 522 ADU.
Ok, nevermind, I had accidently applied a stretch to it... so if I save my 32b calibration files to 16b, I can see the bias now showing a mean 297 ADU, and my lights are around 522 ADU.
Â
I am assuming it will still work fine leaving my calibrations as 32b while my lights come are 16b and it works just fine?
@jjones Yes 32b calibration files are fine. It just means that the pixel values get spread over a larger range, leading to smoother calibration files. That reduces the chance of artefact "jumps" in the calibrated lights.Â
ok, so I guess my next concern is it seems like nothing is actually applying calibration wise. I have a simple example, I loaded 20 lights of the horsehead nebula. I also loaded my master bias and my master dark. They were taken with same gain of 139 and same exposure length of 60 seconds.
I integrate and up top is the (linear, l-calibrated, l-c-registered, l-c-r-normalized) and when I switch between those there is no change in image? I zoom into pixel peep and see no pixel change at all on them. should I see changes? This is mono data, and I just have it left on the default 15% BG stretch.
ah, brain fart again.... I think I figured it out again. That applies when viewing original fits, not your final output file that went through stacking, correct? I can see a slight change in those files when viewing linear and l-calibrated now with the calibrations applied. You can close this... lol.
Â
