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,
I am constantly running into this error message when trying to register my comet frames. APP is asking me to click the comet core, I do but it detects the wrong spot forcing me to click farther away to center on the core. This works most of the time but eventually I get this error and the registration fails forcing me to start over. Any help you can provide would be appreciated.Â
Â
Yes, some data shows this behavior and should be fixed in the upcoming 1.083 release.
Any word on this update or a beta release to fix this? It is extremely frustrating to go through 100 then error out on frame 101 when you have several hundred to process. Is there a trick or work around that I can try?
Thanks
Not a trick in this case no, the 1.083 release is very close to release, if that doesn't fix it please let us know and I'll make sure Mabula takes a good look as to why and hopefully fix it.
Have the same issue and I think it will be much easier if I can manually select the center pixel
I'm having the same issue (tried with Yes and NO answers) and haven't been able to get through this step yet. I agree it is very frustrating to click through most of the frames only to have the program fail when you're almost done...please fix ASAP or remove the capability until it is fixed. Thanks!Â
Just for clarification, this functionality is in a beta version of course, which means there can be issues. Mabula knows about it and will address them.
Yes I'm getting the exact same problme in 1.083- beta 2
Hi all,
This is all fixed in the upcoming release 😉 APP 1.083-beta3 is coming very soon now.. and the 1.083 stable release as well.
IMPROVED, Comet registration, the code to detect the comet nucleus has been improved much from the beta2 code. It has also been optimized in terms of memory usage so it works better and more efficiently now. Furthermore, you can now skip an image if visual comet detection seems to fail, in that case the detection is done based on the detection in the other frames combined with calculating the speed of the comet relative to the stars if the time shot metadata is being used. By default you will need to visually select the comet in the final frame to make all calculations more robust and reliable. In the 1.083-beta2 version, the comet detection would sometimes lead to an endless loop which will no longer occur as well so that has been solved. Once the comet has been detected properly in 3 frames, the comet speed is calculated which leads to better detection and prediction of the comet in the following frames as well.
