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.
I suspect this question reflects a lack of understanding about bpm's! I have no problem with the processes of creating a bpm, creating master files or a fully integrated stack of data. When I create a bpm am just loading flats without any bias frame calibration and darks of course - is that right?
Â
Pam
Hi Pam,
So you load in your flats, darks and bias for the bpm creation. For the darks it's best to take your longest exposures.
Ok - got it.
Thanks for such a speedy response Vincent!
Pam
You're welcome. I am going abroad again though so this might be my last week of speedy responses. Hope I'm online asap after that though.
No worries Vincent. However!  I remain confused about some aspects of creating a bpm. Sarah Wager, in her tutorial simply loads flats and darks using hot pixel kappa of 2 and cold pixels 50% albeit in an older version of APP than I am using. When I do the same I get a calibration warning that 'to be able to perform accurate flat field calibration the provided flats need to be calibrated by (in my case) a masterbias of the same ISO/gain value as the flat frame.' If I create a master bias and load that together with flats and darks I don't get that message - is that right?
I notice that Sara Wager when looking at the details of her bpm suggests that the bad pixel percentage and hot pixel percentage should be around 3% whereas mine is 2.483% - is that ok or is something amiss?
Pam
Hi Pam,
Yes that's fine, I'm note sure but it might be that Sara already calibrated her flats... or it's a change from past versions. Anyway I include them and the masters are created including the BPM. Those percentages are fine, you can try to use the BPM instead of a masterdark in previous data to see if it's effective.
Thanks again Vincent - I will check out by using a bpm instead of a masterdark on earlier data.
Â
Pam
