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 am still within the 30-day trial window - that's how noob I am - but am very excited about what I've seen so far. I've run into a couple of quirks, but one that stands out is failing star analysis for frames that previously did not fail. UPDATE: This is for version 1.075. I just purchased and installed 1.077 but haven't done the stacks yet.
I shot M97 over several nights with my unmodded Nikon D5300 and stacked all the data. There were a few frames didn't load completely for some reason, maybe 3, and APP rejected these for failing star analysis. Okay, fine.
Night before last, I shot one night of M97 using my modded Nikon D5100, and I stacked the data. 1 frame failed star analysis - broken frame. I had already gone through every frame so wasn't sure what happened.
I decided to combine the two and added the D5100 frames to the D5300 frames as a new session and let it rip. It failed star analysis on perhaps 40+ frames.
I'm wondering why suddenly did so many frames fail star analysis? Is it because they were read over my network???
Hi Paul,
Thanks for buying APP! Did you get it to work with 1.077?
Hello Vincent!
No. 1.077 crashes without warning. Just vaporizes.
I went back to 1.075 and reran slightly smaller versions of the stacks I was previously working with, except I had copied everything to a fast SSD in the system to eliminate the network. 1.075 handled things fine - except the star analysis. I lose quite a number of frames due to star analysis failing. Of course, I am very new to this app, and I am pleased I was able to get a result at all. 😉
Thanks for replying!
Maybe try it again with the data on the fast SSD? It still shouldn't just vaporize. 🙂 1.077 does have a better star analysis algorithm so that might help. Not sure if it could be the network, but it might cause some issues, we never recommend using that as the working directory.
Hello Vincent,
1.077 crashes when using the fast SSD as well, so it's not a network glitch issue.
I am using 1.075 presently, and it has not crashed.
The star analysis failure is a bit annoying, but there is probably a logical reason for it. I know from DSS, the number of stars in my shots can be low, like 10-20. Using a long focal length (2032mm) f/10 doesn't always show tons of stars.
As a suggestion - when star analysis fails, have the "fail" popup contain the list of frames rather than having to scroll through the frame list at the bottom of the screen hunting. Sometimes the failed frames are clustered together, and sometimes not making them a bit harder to spot. Then give the user the option to "Continue without these frames? Yes/no."
Nice suggestion indeed, I'll pass it on. Crashes are beyond my diagnostic capabilities as Mabula actually codes it, so I've passed it along.
@khobar95 This happened to me yesterday after having the trail , all worked okay. Now bought and have registration issues
You mean the registration issue in the other post? That isn't a crash, but a data issue. Let's continue the discussion in that thread. 😉
