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.
Hello,
one of my techniques to get smaller stars or to do HDR images like M42 is using two stacks with different exposure time and/or ISO settings. These are stacked separately and combined with layer masks in Photoshop.
For the two separate stacks to overlap perfectly, they have to use the same reference frame.
However, for a 30 seconds exposure at ISO 800 you don't wand to integrate the 4 minute ISO 1600 reference frame. So therefore I select a single long exposure light frame as the stacking reference, but unchecked it in the file list to be not included (in Deep Sky Stacker this works perfectly).
I tried this in APP, but I had a Java error during integration.
Maybe this was a single failure, but since integration takes quite a long time, I have not thried once more.
Should this theoretically work in APP?
Thanks!
Chris
Yes I think that can work, you can load all frames in and then going to tab 4) register. There you manually select the reference (top button). And then all the way down you save the registered frames.
It works. However, I only had good results by deselecting the reference frame after the Normalise step was completed. As far as I understand the frames are normalised with respect to the reference frame, so if that frame is not available it makes sense that APP gets confused 😉
It would be nice especially for cases like this that the alignement reference frame and normalisation reference frame could be separately selected.
BTW regarding speed: in order to test the impact of some of the settings I occasionally run the Integrate step at lower scale without LNC, this can be much faster than settings at full scale with many iterations for the LNC.
