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 have a fairly large set of files I am trying to integrate up using 1.082. Â There are 760 L, 149 R, 131 G, 108 B, and 376 Ha. Â All files register properly and no errors are generated when the integration runs. Â It takes a while given the large number of large files (camera is QHY600 which has 122 MB FITS files). Â I am running on Ubuntu 20.04 with 64 MB of RAM 56 MB of which is assigned to app. Â It is a Ryzen 8 core (16 processes - 15 assigned to app).
After the integration completes I have 4 beautiful integrated FITS: RGB and Ha but the L FITS is basically all white with three black horizontal lines one pixel wide. Â I was a little worried app might choke on so much data but there is nothing in the console to indicate a problem.
Is there a way to integrate in smaller batches and then register and integrate the integrated files?
That is a strange result, but yes you can chop the data in chunks. Which is what I would advise anyway when you have a lot of data. If each stack consists of something like 40-50 at least, all calibration should work fine and the resulting calibrated stack can then be combined later on with the other subsets.
Stacking into 7 sets of 110 each came out OK but when I tried to stack the subsets the gradients produced artifacts - I think because outlier rejection was behaving badly with only 7 images and cutting out some portions of the images as the gradients moved around due to meridian flips etc.
I was able to stack the majority of the images - I removed 60 and then another 60 subs based on the quality score and background levels and while 760 and 700 images didn't work once I got down to 640 subs it stacked fine without artifacts.
Ok interesting, that might indicate a data problem somehow as usually the gradients shouldn't pose that much of an issue (unless really super apparent).
