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!
I have a narrowband dataset taken with a DSLR and a L-Extreme filter. I usually integrate Ha & Oiii separately so I can then compose them back with StarTools.
I've done best 90%, 80% and 60% integrations for both emission lines. Then, cleared all loaded data from APP and re-loaded those integrations as light frames and ran "Normalize" so that they get analyzed.
What I found is that the best quality score depend on the emission line:
* For Ha: 90% best subs
* For Oiii: 60% best subs
I did this analysis because I want to get a good balance between SNR & FWHM and I think the quality score is a good relative measure of that.
So, here's my question: Would it make sense that I pick different % integrations based on the best quality scores of each emission line to get the best composite possible?
Â
Thanks in advance,
Lucas
If that would make sense totally depends on your data, it sounds like you tested this already and that's the best way to judge that I think. I personally would always go for 90-100% depending on what I know the quality of the night has been, when your setup is behaving well and the nights were good enough, that always seems to work nicely. If you have data from nights with a full moon or lots of troubles, then I would probably make separate integrations.
