June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options
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
