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.
I like this feature as I like to add filter used and instrument to the FITS headers. But: then the tool creates a .meta second file, and that file is four times the size oif my bin 1 ASI294 FITS file. That is a problem .... Â
Can the be a way to just batch modify the header data for individual frames without duplicating (and blowing up the size of) the file (like ASTAP can?). That would be super handy!
Â
I will ask Mabula for this, I would've expected it to do that actually.
Dear @heylers,
First of all, what APP version are you using ?
With 2.0.0-beta22 the Batch Modify FITS metadata/CFA tool will also ask you how to save the file with the adjusted FITS header. If you save the data with a higher bit depth, the size will logically be bigger.
If you modify a 32bits mono fits file and tell the save dialog to save it as 32bits float FITS, the size is virtually identical to the original file. Same, if I save a 16bits CFA file to 16bits FITS, also the size is the same except for some bytes. The actual metadata/header is so small it has no bearing here.
To adjust the header directly in the original file is not done by purpose and by request by users in the past. It is always convenient to keep the original file with the original header intact for whatever reason. If the FITS header modification is correct, simply delete the old original fits file if you no longer need it.
Mabula
Â
Â
I'm on beta22. I see it now, on save. My bad!
