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 Benjamin @bbhar940301,
Looking at the screenshots, something is very off here... most likely there is an issue with the calibration data. Did you check the lights in the calibrated view? Simply load a light from the frame list with the calibrated view using the right mouse click menu. Probably the issue will become obvious.
Also, I see from the screenshots that you have lights of 60 seconds and 900 seconds and you are applying the same masterdark to both? That might be related to your problem as well.
Mabula
@bbhar940301 try to use COSMIC RAY option in star analysis with a value of 25.
APP could try to analyse hot pixels as stars.
APP is able to process short R, G, B and long exposure SII, Ha OIII without any problem. I use this option for my images from my remote telescope CDK600 in Chile.
@philippe-bernhard, thanks for helping out, indeed that could solve it as well. But I suspect a data calibration issue as well somehow.
@bbhar940301, were you able to solve the issue?




