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.
Very excited to try the new beta on my large Ha-O3 integration of the Veil with FLI KL4040 camera. Running it now but could not select the Local Normailzation Correction box. Does this depend on other settings?
Wayne
Hi,
On my installation if the filter drop-down box is set to 'no rejection' then the select normalisation rejection check-box is inoperable.Â
If any other option in the filter rejection drop-down is selected then the check-box becomes operable.
Probably an element of redundancy here because if 'no rejection' is an option what is the value of the check-box?
Mike
As you can see there is now a new weights option, which is set to "Auto". This will take care of these settings automatically on the basis of your data. If you still want to adjust it yourself (I would first test the auto setting), you can change the weights to e.g. median.
@vincent-mod
Got it - thanks!
wayne
Hi @whixson & @mestutters & @vincent-mod,
If the integration mode is set to automatic it will control:
- average or median integration
- choose equal or quality weights (equal is preferred choice with little frames to stack for noise/Signal to Noise characteristic reasons)
- enable/disable outlier rejection
- choose the outlier rejection settings if enabled
- enable/disable local normalization rejection when outlier rejection is enabled.
So when you set the integration mode to either average/median: you can control the outlier rejection settings yourself including local normalization correction.
And off course, if you set it to no rejection, the local normalization rejection selectbox is turned off naturally as an option, because if you would be able to turn it on, it would do nothing. That selectbox only applies when an outlier rejection filter is used...
Probably an element of redundancy here because if 'no rejection' is an option what is the value of the check-box?
Exactly 😉
Hope this clarifies the new automatic integration setting.
Mabula
It does yes, apart from the things you can still select.
Thanks! So choosing automatic integration kind of manages everything else?Â
wayne
Hi Wayne @whixson, indeed 😉
I have implemented this, because it should greatly improve usability of APP for many users, especially in the multi-channel/session modes where you will have integrations of different sizes and which would warrent different settings like median/average and the outlier rejection settings.
Mabula
Thanks Vincent, Mabula!
Sounds like a great addition. Simplified and probably makes better decisions than I would.Â
wayne
