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.
This is a common problem for me and no doubt others.Â
Scenario - I have 5 sessions of data covering RGB or SHO.Â
Say 25 Ha, 25 OIII but only 10 SII.Â
I want to use Average integration for Ha and OII but Median for SII.
But I cant because the script forces me to choose one integration method for all frames.Â
So what do I do?
Can we have a facility to allow the optimal Integration Method to be used for each stack please.Â
UPDATE. Just done some testing to compare Median (No rejection) vs Average (Adaptive Rejection (Kappa 6-Low/4-High) and a bit surprised by the results for SII with only 10 frames.
In both cases the Average integration stacks were better quality - although differences were slight. I also noticed the rejection maps for Median showed noticeably more rejected data. Guess it could be data dependent but based on this I will now consider using Average integration for >= 10 frames where previously I would have wanted >=20 frames.