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.
Hi,
I just tried to stack some long exposure (30 to 90 sec.) of comet Neowise and got strange pixel trails in an opposite direction of the startrails. Would this be solved if I had made darks and bias etc.?
Thanks,
Arnaldo
Very likely yes, these can be bad pixels.
@vincent-mod Thanks for your reply... Is there any way to minimize them without darks etc.?
You can try to use cosmetic correction in tab 2, switch the options on for hot pixels, I'm not entirely sure if that works without any calibration data (never tried that). Brin the hot pixel kappa down to maybe 2.5 or lower to make it more aggressive.
@vincent-mod Thanks! I’ll just give it a try... And maybe I’ll make some darks too... If they are bad pixels, they might appear at the same place anyway!?
Yes that's why darks work. If you make some proper darks a BPM will be made automatically as well, this you can use on all your data taken with the same sensor. It removes bad pixels and never hurts the data, so always use one is my advice.
@vincent-mod from now on... I will 😉 Thanks for the advice!
Good suggestion Steve, you can try that indeed and make a bpm with those.
