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.
This is a common problem for me and no doubt others.Â
Scenario - I have 5 sessions of data covering RGB or SHO.Â
Say 25 Ha, 25 OIII but only 10 SII.Â
I want to use Average integration for Ha and OII but Median for SII.
But I cant because the script forces me to choose one integration method for all frames.Â
So what do I do?
Can we have a facility to allow the optimal Integration Method to be used for each stack please.Â
UPDATE. Just done some testing to compare Median (No rejection) vs Average (Adaptive Rejection (Kappa 6-Low/4-High) and a bit surprised by the results for SII with only 10 frames.
In both cases the Average integration stacks were better quality - although differences were slight. I also noticed the rejection maps for Median showed noticeably more rejected data. Guess it could be data dependent but based on this I will now consider using Average integration for >= 10 frames where previously I would have wanted >=20 frames.
