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.
Hey APP Team
I have noticed a bizarre anomaly, and I can re-produce this.
If I load up all of my flat frames from all filters (L, R, G, B, Ha, OIII, SII) and load up all of my dark flats for each corresponding filter, and then ask APP to create calibration frames, it successfully creates all MDF files, but during the master flat creation it always fails on Luminance, stating it could not find a Master BIAS, Master Dark Flat at the corresponding ISO/GAIN etc etc. It always does this when it gets to luminance, and if I hit continue, it continues to create the remaining R, Ha, OIII and SII successfully.
If I load up my MDF files, and run therough the same process again by loading up my Flat files, it proceeds without any issue whatsoever, even though it is the same MDF files that was created in the first step.
It only does this when performing an MDF create and then an MF create within the same cycle.
Regards
Simon
Interesting! I'll notify Mabula about this, we may have to ask for your data to test this as well.
Â
Added question; does your luminance data have a different instrument name by any chance as shown in the table in APP? If so, we've solved this issue in that case in the APP 2.0 beta.
Hi Simon @stastro,
Thanks for sharing your issue. Which version is manifesting this? The 1.083.2/4 version or the new 2.0.0-beta1 version?
I ask, because I think it is fixed in the 2.0.0-beta1 version?
Mabula
Added question; does your luminance data have a different instrument name by any chance as shown in the table in APP? If so, we've solved this issue in that case in the APP 2.0 beta.
In my case no, they all have "ASI Camera (1)" for all flats and dark flats with all filters
Â
Ok, then it's likely another issue that was also solved in the beta. 🙂
Ok, then it's likely another issue that was also solved in the beta. 🙂
Have not hit it in the BETA, just ran through the same process albeit with 50% of the flat frames versus the last time, but all filters processed successfully
Â
Hi Simon Todd @stastro,
That is great to hear ! I am confident that this issue is 100% fixed with the beta, but please let us know if something odd does happen again in the calibration 😉 Thanks for reporting !
Mabula
So it looks like the issue is resolved for sure, I did the same number of flats and dark flats and it processed them all successfully, silly me forgot to add in the master dark so it did not porcess all the way through with my lights 😀
