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
One thing has been annoying me for quite some time:
If one file fails to register, the whole process stops. Why?
Why can't the process just continue with the files that did register? You can always go back and re-register (start over) if you want to include that file.
Several times I have experienced that I start a process including several hundred files which I know will take hours, but when I get back to the PC the darn thing has stopped . This is not user friendly!
Display a message on the screen, but please, pretty please, let the process continue with the registered files.
Hi Heno,
Yes this is indeed the case and something Mabula will change, good point.
Hello,
I second what Heno has said. It's discouraging to set the computer to process overnight a large batch of files, and then discover in the morning it didn't go because a few files failed register.
I just had a multi session fail, which consisted of data of the same subject using the same equipment over 5 nights. Lights from each night's session were previously calibrated, saved as calibrated lights, and successfully registered and integrated within each session. When I then went to integrate all the calibrated lights from the 5 sessions into one master integration, 12 of the 600 or so calibrated lights failed to register. Now, the reason I had integrated the individual sessions was to make sure that I had good lights that would register (because I have had this problem before). So I was surprised that when going to a big multi session a few of the known 'good' calibrated lights failed to register under this circumstance.
But regardless of the reason these calibrated lights failed to register in a different integration, I just want the system to continue the integration process without the lights that failed to register. A warning message that a few light frames failed to register and therefore were not included in the integration is sufficient. Thank you!
P.S. I want to say that overall I am quite enjoying APP!
