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.
EDIT by Mabula: solved by enabling 3) analyze stars, cosmic ray/noise reducer
Hi. After many successful years with APP, I'm hitting problems stacking images properly.
I take what looks like a decent series of images, which, individually look fine, but when i stack them, I'd just getting a blurred mess. I ache a screen shot of an individual file, and the combined stack.
These shots are from a batch of 100 images I took of M51. The full stack of 100 was just a series of burred lines. These are from random selection of 10, just to show whats happening
I hope someone can help because I'm at my wit end with this
Thanks
In 3) analyse stars, you need to enable the cosmic ray/noise reducer and set the lower limit area size to 15-20. Then try again, it will probably work as expected then.
The stacked result looks to have a lot of noise, so I suspect that no Bad Pixel Mapping is used, maybe also no darks for some reason? I think that APP is locking onto hot pixels instead of stars to register on here.
Let me know if this helps.
Mabula
Thanks Mabula
I did use darks, flats, dark flats and BPM in the calibration stage. Maybe I should run some new darks and generate a new BPM from them, and rerun the process.
I’ll give it a try. Thank you
Hi Mabula
The advice about Step 3 worked perfectly - thank you so much 🙂
Here's the final image with the best 75 frames stacked
Hi Dave @davehux,
That looks really great ! Thanks for the feedback, I am happy to read that my suggestion solved it.
I will try to improve this behaviour in star analysis for sure going forward. Ideally, the noise reducer should become redundant.
Mabula
