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.
Several months ago I created a darks library for my ASI2600MC, 30 exposures each grouped using temp, gain and exposure times. Those darks have served me well and I am getting ready to update the library with fresh darks.Â
My question is can I load all the new individual dark fits frames into APP, and then use (2)Calibrate at its default settings to create a full library of master darks and then trash the original dark fits frames? It would save storage space and the masters might speed up future stacking. Also do you recommend keeping BPMaps in a library?
Thanks,
Frank
You can do that if you're sure they all work well. Personally, when I have the space, I tend to keep the single subs as well and throw those away a year later. Sometimes an algorithm can change (in any processing software), requiring a rebuild of the masters. Doesn't happen often though.
