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.
Hi Mabula
I'm totally loving APP! I'm consistently amazed by what you have managed to achieve so far. I know i will be using APP for many years to come, so please keep up the good work 🙂
I have a couple of small improvement ideas i just thought of.
1. The file list already gives the exact time that each frame was shot. But it would be good to see beside it, a column that gives the time in seconds between one frame and the next. This way, it would be easy to see a visualisation of the inter-frame delay. This could be useful in determining if one needs to tweak their dithering settings, which for the newer CMOS cameras (of which i don't own!) is pretty important, as they usually use shorter exposures.
2. I sometimes like to do a few different stacks and compare them. For example, a regular Average stack, A Bayer Drizzled one, and an x2 Drizzle one. But each time i have to do the new Integration, APP still has to re-load all the light frames again. And if you have a lot of subs, this can take up quite a lot of time. Would it be possible to keep the already loaded frames in memory until, say, the user closes APP? That could really speed up doing multiple stacks! 🙂
Ciarán.
