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 wondering why my subs are all 5184 x 3456, but the Master frames are built at 5344 x 3516? Â Can that cause trouble when subtracting and dividing frames?
Hi Greg,
Excellent question đ
The images/frames of your DSLR camera are always crops of your entire sensor. All DSLR manufacturers make a crop of the entire sensor to present you with the image that you shot.
This cropping is done ath the end of the RAW conversion of the data.
The image dimensions of your calibration frames are the image dimensions of the entire sensor. That is the reason why you see this difference.
What happens in calibration of a light frame in this instance:
1) your light frames are read in the raw converter, this reads your entire sensor, so this raw image raster of your light frame is your entire sensor: 5344x3516
2) this data is monochrome CFA data, undebayered.
3) the calibration CFA frames are then used in the right order to calibrate the light frame. So your light frame raw raster data with dimensions 5344x3516 is calibrated with 5344x3516 calibration frames. So calibration is done on the entire sensor.
So this means that you have a 100% guarantee that this is done perfectly, it will not cause trouble with dark subtraction or division by flat frames đ
4) After having applied all calibration frames, your data will be debayered.
5) Finally, the fixed sensor crop is performed on your light frames. So from all 4 borders some data is removed. This leaves you with the 5184x3456 image dimensions for you light frames.
Let me know if this is clear.
In addition: so this means that APP calibrates your data in the raw converter at the right moment. Other applications that use DCRAW (almost all other programs) simply can't do this.
Mabula
Yep, I now am getting this error and can't use the masters. This was not a problem last week, and only started when I updated to ver. xx3 from xx2 yesterday. I get this from all Masters.
Â
Done playing for today. Maybe I did something different here, I'll double check tomorrow. Probably user error.
Â
Hi Greg,
Thank you for showing the screenshot.
The problem why you get this message in this case:
you are trying to apply the master calibration frames created from the original raw calibration files to fits files with the extension cal-ch2Â
- The master calibration frames created from the raw files will only work if you apply them to the original raw light frames.
- Then the image dimensions of the light and calibration frames are identical (the whole sensor image dimensions) and you will have the assurance that calibration works like it should, pixel per pixel.
The files that you are trying to calibrate, in this instance, seem to be calibrated already (-cal extension) and I think you have split them into the 3, R,G,B, channels as well (-ch2) so this is monochrome data and it has undergone the sensor crop already.
So if you still need to perfom calibration on this data, apply the calibration first to the (cr2,nef) raw files. And then you can save the calibrated files while splitting them into the 3 color channels.
Let me know if this clarifies things đ
Mabula
Oh geez, I see that now. I loaded the wrong subset! It was late😩
Thanks for the reply. It's nice to get answers so quickly.
đ you're most welcome..
