Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.
It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
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.
Hello APP devs,
my full-frame sensor size is 6338x9576. When I capture a Light image and view the metadata, it lists the size correctly as:
HDU1 - NAXIS1 = 9576 / length of data axis 1
HDU1 - NAXIS2 = 6388 / length of data axis 2
In my capture program, I am able to set a smaller frame size for capture from this camera. This is helpful when a reducer doesn't produce a full-frame image and I have to crop in. In my recent session, I set the frame size to be 4168x6224 (the middle area). The Light from this session shows the correct metadata as:
HDU1 - NAXIS1 = 6224 / length of data axis 1
HDU1 - NAXIS2 = 4168 / length of data axis 2
[ref:A] the 4168x6224 images were captured at (1110,1676) location. I have also captured my flats using these dimensions.
I have a library of calibration images (Darks, bias etc.) that were captured with the full sensor size. The metadata for these files show correctly as:
HDU1 - NAXIS1 = 9576 / length of data axis 1
HDU1 - NAXIS2 = 6388 / length of data axis 2
Q1. using [ref:A] above, can I extract the 4168x6224 subframe in APP from the full-size calibration files (Darks, Bias) to apply to my 4168x6224 sized lights? How can I do that? I understand BPM may be re-calculated with the cropped Darks / Bias frames. Does APP allow me to crop with exact pixel range and location? AFAIK, batch crop doesn't let me do this.
Q2. Is it a sound approach? will it work? Yes/no why?
All in all, I am trying not to redo my entire calibration library for my cropped capture of Lights.
Looking forward to your thoughts & many thanks for your time!
Hi @outer-space,
The approach is sound I would think, you need to crop away 1676 on the left and 1110 from the top from your original masters with dimensions 6338x9576 and make sure that the resulting masters have the correct dimensions of 4168x6224. Best check to know if it works correctly, is to check if the Bad Pixel Map properly removed the hot pixels in a light. You can check this with the calibrated image viewer 😉
The Batch Crop tool should allow you to do this, you can simply add the correct offsets in the offset fields like this (APP 2.0.0-beta17) and the crop will show correctly on those masters to crop:
So left offset would be 1676, right offset would 1562, Top offset would be 1110 and bottom 1060, then the resulting dimensions would show 6224x4168 (width x height) for your data 😉 (I loaded a different image with different dimensions so my resulting dimensions are off... )
Mabula
