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.
If you change out one of your calibration files, like a flat file, after star analysis, registration and normalization is done, why is it that APP start over from scratch doing all these steps over again?
In what way is a flat file (or any calibration file) used for star analysis and registration? 🙄Â
Not sure, I never actually tested that, why would you want to change a calibration file during the process and after everything is calibrated?
This was actually a curiosity question and not a big deal, but what happened was that my integrations looked like crap. I realized that I had used the wrong flats. I should of course have checked that up front. So I thought I could just replace them and rerun the integration (and possibly normalization), but no such luck. APP started doing star analysis. That, and registration, take a couple of hours with a lagre stack.Â
So maybe you could ask Mabula why it is like that. There is probably a good reason. I'm just curious.Â
Oh yes, didn't mean to say it isn't interesting. 🙂 We discover bugs sometimes precisely because people use the program slightly differently. The next version of APP will have the ability to skip steps, so if you save, for instance, the star registered frames, you can load them in later again and tell APP to skip star analysis. This may not fix this particular situation though, so if that remains to be the case please let us know and we will fix it.
I did a little testing just now to see if I could recreate what happened. 20lights, one of each type master calibration files. First I did a full integration using all standard settings.
There seem to be three scenario:
1. Adding a new flat and unchecking the other, press integrate and APP start integration as expected. (But I'm not sure which flat is actually used)
2. Delete the existing flat (using clean) and then add a new one. Press integrate and APP starts with registration then normalization and integrate. (Here I belive the new flat is used.)
3. Delete the existing flat (using clean) and then add a new one. Then press "reassign masters to lights". All existing analysis are deleted and APP starts with analysing stars.Â
There is probably good reasons for all of this, but if there isn't......Â
