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,
when starting star analysis after loading and calibrating my 50 L F DF + MB + MD frames APP doesnt perform a star analysis but restarts calibration. (I am also repeatedly asked where to save my Master frames)
Some days ago, with a similar stack, APP ran without problems.
Any ideas?
Thanks, Peter
@peter-s Hi Peter, very strange indeed. What OS are you on? Did you try rebooting the PC/laptop? Is your data on the internal HD or an external one? If external, is it an SSD?
Hi Wouter,
W10 64bit, Pi7, 64 GB RAM, L + F + DF + MB + MD loaded from int. HDD, working directory is int. SSD; I did a reboot and several trials - no change.
Now it runs after unchecking "auto detect Masters & Integrations" - that was always checked.
Peter
Hello,
when starting star analysis after loading and calibrating my 50 L F DF + MB + MD frames APP doesnt perform a star analysis but restarts calibration. (I am also repeatedly asked where to save my Master frames)
Some days ago, with a similar stack, APP ran without problems.
Any ideas?
Thanks, Peter
Dear Peter,
If you load the single flats and darkflats, APP will again try to make Master calibration frames (MasterFlat and MasterDarkFlat) If you already have created the MasterFlat, you only need to load the masters and then APP will start directly with 3) Analyse stars.
I think that should explain it? Or is there something else happening you think?
Mabula
Â
Dear Mabula,
yes, I know. I started from beginning and couldnt proceed with the next step = star analysis; when clicking on "analyse stars" APP restarted calibration of all frames until I unchecked "auto detect Masters & Integrations".
Peter
Hi Peter @peter-s,
Not sure though what exactly happened. The "auto detect Masters & Integrations" will detect Masters and Light frame Integrations no matter with which button you load them. So if you load a MasterDark with the Lights button, it will still be loaded as a MasterDark. So by disabling "auto detect Masters & Integrations" and still having loaded single calibration frames, I guess APP would still start with trying to create calibration frames, because that always is the first step before anything else.
Do you want me to check you data to see what exactly happenend or is all okay now?
Mabula
Hi Mabula,
....I think leaving the Light frames checked lead to that behaviour, even if that never happened before.
Thanks!
Peter
