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.
I have noticed that since the last update, APP does not save the files into the working folder I select. It saves the files into folders I had used on previous sessions.
Is this a known bug?
It should, unless you pick another directory when it asks to save the results?
@vincent-mod. it sends the files into a previous session directory not the one I specified when I opened the "now opened" session. I never had that problem until the last update in February.
Mmm, I'm forwarding this to Mabula, I don't think much changed in just the latest version here, but could be wrong..
@tempusfugitxxii, in the latest version we had a big update of the file save module. Normally, the results in 2), 4),5),6) were always placed in the Working Directory. Now you can adjust this with the Set Save Directory button.
We have not yet implemented that APP will remember the working directory of a previous session, so this can not be the case here. You must have set it to a different location with the Set Save Dir I assume?
Mabula
It is happening to me right now.  I did a session an hour ago. Closed APP and then came back for a second session for a different target.
The 1st session was no problem but when saving during the second session, APP sends the saved files to the previous directory that I had selected in session #1. It does not pick the directory I selected when starting session #2.
Â
Hi @tempusfugitxxii,
From that screenshot I can not tell what is happening. And what are you saving here while being in menu 4)Register? Are you saving a frame with the Save button below the histogram? That folder can always be adjusted by clicking on Directory and will show the latest path that you were I think, and not the Working Directory.
Mabula
What I am saying is: the folder in which the files will be saved with the save button under the histogram does not always correspond to the working directory. This is new with this release. Was that intended to be the case? If yes, I'll know better from now on.
Hi @tempusfugitxxii,
Indeed, that is new in this release with the new file saver which is much more flexible than before 😉
It look like you are saving registered frames with the save button below the histogram? It would be easier and better to do it with the Save Registered Frames option at the bottom of menu 4). That will always save in your Working Directory by default, unless you explicitely set the Save Directory with the set Save Directory button above the save registered frames button 😉
Mabula
Â
