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.
Perhaps someone can explain me why. When I stack my lights, darks, flats and darkflats in APP, I get picture nr. 1. I had same tested in PI with WBPP, and as you can see on picture nr 2, it's all fine. Could someone tell me what things I might be doing wrong in APP
Â
@ancalime That's hard to say without more info. Which calibration data did you use? Which settings in APP? Which version of APP? Did you try to load the unprocessed PI file into APP and stretch it?
Normally I load my files, ie. 200 120s lights, 30 darks, 30 1s flats and darkflats (or flatdarks) in the 1st tab of APP. I subsequently leave all at tab 2 default, and press tab 3 and analyse the stars. When the stars are analysed, I uncheck the odd looking frames. I then leave tab 4 at defaults, tab 5 at defaults, and in tab 6 I leave intergrate on automatic, No LNC and I leave MBB as is, which is not enabled. When all is finished, I get the very overcorrected stack. APP wersion 1.083. See below the unprocessed PI stack loaded and stretched in APP. Also, I always have this workflow, but never had this kind of overcorrection
Â
hmmmm.... i also just decided to check all the frames... turns out that I have a few pure white frames in it.... guess we all make mistakes sometimes
Â
If I may chime in, I think I see the same in the PI result, just way less of a stretch. Can that be the case as well?
I fished out 10 pure white frames. I guess I forgot to get them out when I did APP, it might explain it. Without those, and in PI, it was a simple DBE and bob was again my uncle... havent tried in APP without those nasty white frames. But I think it's been an error on my side all along
Â
