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.
Oh that is a new one. Can you tell me what exactly you did before getting this result (your processing steps) and what kind of data you're combining? Is everything behaving normally otherwise?
@vincent-modÂ
Thanks for your response, Vincent. I am APP user from its first hour. Never experienced this behaviour before. With these data it apperared repeatedly. So I finally combined the channels in PS. I combined 4 stacked files of L, R, G and B data of this frame: https://astrob.in/full/abifgz/0/ . All other functions of APP behave normal.
Peter
Â
Edit: I just tried it once more and this time is was Ok (after it had been wrong at least 10 times before in different editing sessions). So if my issue is singular and nobody else has experienced it yet maybe is better to wait if and when and how often it will reappear or not.
That is interesting. I'm almost thinking you may have an issue with your system maybe, you aren't using an external disk to work on?
The system is stable since many versions of APP 🙂 I have a 2048GB internal SSD that is 1/3 filled as a workspace for APP and another 1024GB SSD for the other "hungry" programs like PS and LR. So the system should not be the culprit. I will try to reproduce the fault and come back to you with maybe more information. I was able to finish the image with SNR 110.3 +11.3 VdB 152 and DeHt-5 last weekend and in my eyes it is another proof for APP's phenomenal ability to produce superflat, gradientfree and well calibrated masters that allow a very deep processing:
Full Res.:> https://astrob.in/full/abifgz/0/
Pffff, that is a very very nice result. Maybe you ran into some memory hickup somehow.. hope it'll stay away.
@vincent-mod
Hope so too. Memory hickup while combining the channels is not on my list to be honest. We'll see, I'll keep you updated. Thank you once more for the support, Vincent.
Â
CS Pete
Yeah, not really on my list either, just guessing out load. 🙂 Seems weird it only pops up that time, that's why my mind was going there. Anyway, thanks for reporting and continuing to look out for it! If it happens again, I'll ask for the data, maybe we can then replicate it.

