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 am in the process of making a Good Bad Pixel map using 100 dark frames of 5 min subs at an ambient temperature of 25 degrees C for my Nikon D5300a. As it also needs flat frames so I am a bit confused. Do I need to separately use flat frames for the broad and narrow bands? Or there is no relation between Bad Pixel Map creation and flat frame bandpass (broad band or narrow band)? Mostly, I use either a UV-IR cut filter or a dual narrow band filter. First I will make Bad Pixel Map using Broad Band Flats.
Please let me know.
Thanks
Not really necessary to use different filters, just use a broadband flat. And you can create one from just a few dark frames, best is to make them as bad as possible (in the sense of a warm sensor and long exposures). A BPM is not going to hurt your data, it just corrects what it could detect if there.
