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 spent seven hours on a cloudy night creating an assortment of calibration frames to include flats,dark flats and darks (30,60,90,120,180,300 sec) at ambient and 0C degrees.
When I created a BPM using the 31x 2 sec flats, 30x 2 sec dark flats and the 20x 180 second darks, it generated what I believe is a good BPM with 2.7% bad pixels. (I used auto settings). However, after I saved the BPM to a folder, and then tried to load it into APP, I get the message that it "does not appear to be a Bad Pixel Map" as it lacked the BPM metadata. When I clicked YES to load it anyway it loaded OK -it appeared identical when zoomed in- (third image, below) but it no longer displays the metadata as it does in the first image, below. Did I do something wrong? Will the BPM work in future processing attempts as it should? Thanks!
Mmm that is weird, you didn’t change anything in between for the BPM? It should just be created and that’s it. No further processing should be done on it, or loaded into another program and then saved again. Things like that might change the fits data.
Well, that is what I suspected. Although it was automatically saved to the directory folder after it was created, I did 'save' it again, and added a suffix to identify it (e.g. "-0C"). Will it need to stay in the original folder or can it be moved to a "Bad Pixel Map" folder without changing the name?...would simply moving it change the metadata? Thanks for the reply!
No that should be fine, also renaming it would be ok I think as the fits header is what matters. But to be on the safe side for now, just save it in a folder for you to keep. A BPM can be used for at least a year on all your data, it never degrades data.
@vincent-mod Thanks again...slowly getting more familiar with APP! I just now processed my first ever meridian flip in APP...no issues.
Here is an image from July!
Excellent! Good to hear. 🙂 I would make the background less dark though, but the signal is great!
