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.
I am running APP on a Mac Pro 2009 with Catalina. Power saving is on 3 hrs for system and monitor. But when the screensavers kicks in it seems that processing (integration) is halted to resume on re-activating the screen.
Is this correct?Â
@donald It is correct that the screensaver stops APP. This is a known issue and Mabula has been looking for a solution for quite some time now. For now, please disable the screensaver before starting processing with APP.
Ah ok. APP is now analysing the light frames in the integration process but this continues as I activate the power saving for the screen.
Update: no it does not. It halts after some time, it does not seem directly.
quite confusing, now trying no screensaver but powersave on sreen... let's see what that does...
Ok that works. The process goes on when you activate power save after deactivating screen save!
So that's what the problem is! I have been wondering what triggered the odd "slowdowns" I have seen at times. I didn't consider it being a screensaver issue! Glad I read this thread...
