May 27 2026 APP 2.0.0-beta45 has been released !
Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.
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 am a newbie with APP, and have downloaded version 2.0.0-beta 13. I'm trying to get through calibration, have generated Flat and Dark-flat files, but cannot get a bad-pixel map generated. The problem is that all of the process documentation is in videos and the interface has changed since those videos were made so that following the process cannot be done. For example there is no "create bad pixel map" button and it is not clear what items in the interface need to be selected or un-selected to do this.
1) how do I get the BPM made?
2) Is there ever going to be some documentation of how to use the system? It seems that just generating a couple page document describing how to get the basic processes done would be a big help, and need not wait for a complete documentation—a formidable job.
Jerel
Hi Jerel,
the BPM requires both Flatframes and Darkframes
(don't confuse these with Darkflatframes). The Darks will need to have the same exposure time & temperature as Your lightframes, while Darkflats will have the same exposure time & temperature as Your flatframes. APP will integrate Darks, Flats and darkflats and create Masters. When BPM creation is selected in tab 2 it'll also create the BPM
A BPM can actually be created on its own, by providing darks. Flats are not required, you can do it of course, but cold pixels are not really a thing anymore in many modern sensors. If you create a few darks that are long exposures and preferably at higher temperature, that would be best. APP will then see all the possible defects of the sensor and correct them (if it sees them, otherwise no harm is done to your image).
Jochen and Vincent: Thank you for getting back on this. I'm slow to reply as we've been out of internet—because weather.
I get the part about selecting files (your replies were helpful). and about enable BadPixelMap. What I could not find was a "do-it" button to tell APP to calculate (there was a button like that in the previous version). I'm sure there's a "duh-obvious" step to tell it to proceed, but I'm stuck at "Duh" This is where I think even a simple document to describe the operational structure of APP would help.
I did find a work-around. I had a few crummy light images, and using the Flat-Darks also as Dark, I just ran the whole procedure (tabs 1–6) and got an image which was not as bad as I expected, and as by-products got a BPM along with MF, MD, and MDF files.
I can see that the interface layout is set up to be clear and efficient, but maybe not obvious to the beginner. I'm looking forward to learning this elegant tool, and appreciate your support.
Jerel
The "do-it" button would be the "create masters and apply to lights". This is what normally is happening, but you can also load in your calibration data without lights and press the button.
@vincent-mod Ahh, got it. Thank you.
