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.
Hi Mabula,
Would you considder adding the posibility to setup some selection criteria on the light frames to be used in the process?
I mean not only asigning a quality score that lateron assigns a percentage to the frame to be used in the integration.
IMHO it would be beneficial for the final integration to be able to reject frames that do not comply with the setup criteria ( like FWHMmax, ...etc. ) and these frames will not be taken into account for the integration.
This without doing that by hand as is already possible using the framelist, but automagically.
Just an idea?
Kind regards,
Lammertus de Vries
Hi Lammertus,
I have notified Mabula of your request.Â
Wouter
Hi Lammertus @lammertus,
Indeed, this is on our ToDo list so we will make it possible.
Currently, the APP quality score determines which frames will be integrated using the % slider at the top op 6)Integrate.
We will make it possible, that you can choose which metric to use for the % slider ;-), so then you can opt to stack the best 85% frames in terms of FWHM size, or roundness or shape (size*roundness) for example.
Mabula
@wvreeven Thanks Wouter, much apreciated!
