MAY 4 2026: APP 2.0.0-beta44 has been released !
New improved internal memory controls should now work on all computers
May 1 2026: APP 2.0.0-beta43 has been released !
Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.
Apr 29 2026 APP 2.0.0-beta42 has been released !
New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...
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.
Hello,
I'm currently trying to stack my first light images (Skywatcher Evostar 72ED) of M13. I have 100 lights and 30 darks and bias frames. The image quality is not very good due to the fact that I still waiting for my field flattener to arrive. To get something out of my images I only stack 70 out of 100 light frames but during the normalization process all 100 frames are processed. Why is this done if only 70 of them are used at the end? The quality score of an image is calculated during the calibration in step 2 so it is already there when the normalization process (step 5) starts and at the end (step 6) only 70 of my images are used for integration.Â
For me it could have saved 30% of the time the normalization step took saving about 15 minutes or so.Â
Maybe somebody could bring some light into this.
With best regards,
Mario.
The quality score does change when subsequent steps are processed, when APP knows more about the data because of those steps, things can change.
