June 24 2026 APP 2.0.0-beta46 has been released !
Improved internal memory configuration (lower ! memory usage), fixed beta45 startup issue, fixed Set Save Directory & 2-panel mosaics.
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 have used APP for the first time today and I love it. I stacked 25 light frames of M42 and it turned out great, and today I tried using calibration frames with some new data too. However, about 40% through the calibration process, it ended saying there was an error creating BPM and a master. I can retry and take a screenshot of the error message if more detail is needed. Should I manually create a BPM first? If so then do I still add flat and dark frames? Help is appreciated. Thank you!
Clear skies
@sjlan5 Hi Tony,
A screenshot of the error message would help indeed. However, which calibration frames did you use? Were they taken with the same camera and software as the lights?
As for creating a BPM: there is no need to do this manually. APP will take care of this automatically if darks (and bias as well if you choose to use them) are loaded when processing the lights.
@wvreeven Thanks for your reply. I used all calibration frames, flats, darks, dark flats, and bias. Also yes, same camera and software. I just started the calibration again, when the error message pops up I will attach a screenshot here.
@sjlan5 Just for me to understand this correctly: you are using the same calibration frames as you used for M42 and for M42 it worked but not for your subsequent target?
@wvreeven I took the calibration frames with the light frames last night. Also, I attached the error message
Â
@sjlan5 I see in your screenshot that you have loaded JPG images as lights. Is that intentional? You should use the native camera format as much as possible. What camera did you use to shoot these images? Were the M42 files also JPG files? What happens if you try to integrate the lights without using any of the calibration frames?
When I shot my light frames I simply uploaded them from my camera to my desktop and put them in a file. I shot the lights with a Nikon D5100, a little old but works great. I believe all the calibration frames and lights are JPG images, but it came out of my camera like that. I integrated the lights on their own without calibration frames and it turned out fine, I'll attach an image
 M42 stacked without calibration frames
Â
@sjlan5 Yes, the camera isn't the problem. But you really should make sure that the images are taken in the native NEF format of the camera. The fact that the images are JPG most likely are the cause of the issue. First of all JPG files are 8 bit. Secondly they are compressed. This both leads to loss of data which APP cannot recover from. The fact that it worked with the M 42 images is due to not using calibration frames.
I see. I was shooting in fine quality setting on my camera and it says they are JPG images, and when I turn it to RAW it says NEF. So if I retry and shoot with RAW instead of fine it should fix it?
@sjlan5 That's correct. Shoot with RAW so you get NEF images and APP will take care of the rest.
@wvreeven Awesome, thanks for the help
