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, I have noticed that when I integrate mono captures as R,G,B the integration times for the R, G and B stacks show up correctly individually. However when I finally do the composite RGB image by invoking 'combine RGB', the integration time for the final RGB image, shows as 0.0 seconds instead of integration_time(R)+integration_time(G),integration_time(B).
is this a known issue?
Hi @outer-space,
Well this is a difficult technical question actually and not an issue in principal. If you would combine stacks of a certain exposure time with a composite tool, I think the summed exposure time of the individual channels does not say too much anymore, since the composite formula will almost never coincide with the summed value for exposures like you indicate. I wil think about this a bit more and have added this to our issue list.
Mabula
