2026-10-09 APP 2.0.0-beta48 has been released !
This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.
2026-10-03 APP 2.0.0-beta47 has been released !
This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂
And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.
Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.
RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.
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
Â
Â
