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.
Dear Mabula, all,
While trying to calibrate data, I ran into a critical warning during the process to generate a master flat image.
I think I found the source of the issue, but I cannot solve it. A few days ago I generated a BPM and master bias for my camera. I used data obtained from a Nikon D600 dSLR full frame camera, via an ASIAIR unit to do so.Â
Using the MB frame I want to calibrate some older flat frames I made in 2021 and generate a master flat. I know this is not ideal, but I could not find the MB I made back then, so I figured using the current MB is better than nothing.
Anyway, there is some issue in combining these old flat frames and the newer MB frame. It states that it cannot properly perform the flat field calibration properly and that the flat frames require a MB with the same ISO/gain as the flat frames. But this IS the case, since my MB frame and the flat frames are both shot with the same camera and at ISO400.
The only difference is that the MB is generated with Nikon D600 data obtained using an ASIAIR. The flat frames are obtained from my Nikon D600 camera directly. I see in the dimensions header that there is some difference between the MB frame and the flat frames. Next to the flat frames it gives a range of resolutions... But when I look at the resolution from the flat frames in windows explorer, it exactly matches the MB frame (6034 x 4028).
Â
Am I doing something wrong, or is this possibly a bug in APP?
I am using the most recent version, 2.0.0-beta29.
Best regards,
Rob
Any help would be appreciated. Thanks.

