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,
I am slowly working through a mosaic project & last night managed to capture a 2nd session of data for the target.
Running two sessions data through APP was a breeze but I did stumble upon a weird naming convention issue.
On the first integration of my data I chose:
Multi-Session Options > Integrate per session & all
this produced:
Integration 1 Session 1
Integration 2 Session 2
Integration 3 Session 1 & Session 2
very obvious and nothing wrong there.
Now I was not happy with the output of Integration 3 and made some changes in the Integration tab before running the Integration again.
This time I just chose:
Multi-Session Options > Integrate all
this now produced a frame name:
Integration 4 Session 2
Initially I thought that I had made an error but looking more closely, the associated filename for this Integration does in fact include the text 'session_1_session_2' and when loaded in the viewer it is both sessions combined.
Possibly the 4th Integration should have also name the frame 'Session 1 & Session 2' or even just 'All Sessions'
Don't get me wrong, the software itself worked like a dream, very simple, this is just more of an aesthetic point really.
Regards..,
Kirk
Hi Kirk @1cm69,
Thank you for sharing this. Can you please indicate on which APP version this occured? I know that this was a bug/or resembles a similar one in an older version.
The frame name should have been Session 1 & Session 2 to indicate both sessions were integrated.
Kind regards,
Mabula
Hi Mabula,
v 1.070
regards..,
Kirk
Hi Kirk,
Thanks, will check this particular issue before the next release 😉
Mabula
Hi Mabula and Kirk,
I thought I would tack my observations onto your post, Kirk. No need to start another topic.
Background: My camera is not cooled and does not have an integrated temperature sensor. In order to temperature-match my darks against lights I designed an Arduino-based, high-precision ambient temperature logger. At the end of a session I use the log to segregate my lights and darks into subfolders having names like 'temp_19.5F' and 'temp_20.0F'.
To make this work in APP, I create custom session names like 'temp_19.5F' and 'temp_20.0F'. It appears as if APP has a problem handling '.' (period). The final integrated stack looks correct but the file names are misleading (see attachment).
I am using APP 1.071
Thanks,
Brian
Hi Mabula,
I've chosen an abbreviated naming convention that APP handles and I like better:
examples "19F5" for 19.0 Fahrenheit, "20F0" for 20.0 Fahrenheit
works well and easier on the eyes.
Thanks,
Brian
