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 tried to do a comet registration but APP continuously gives me an error like this popup window, eventhough when I raise the amount of stars, and do all what is suggested it still fails. When clicking image by image on the comet nucleus, then Skip view to continue, finally the error message pops up. Anything I do wrong, any instructions on how to use this?
I'm using the Beta 7 version, works nice and a lot faster then before but I encountered this problem. Trying to process with DSS I had no problem, APP does more or less the same, first registers on the stars and then registers each frame on the comet nucleus ( you have to indicate by hand every frame sadly enough ).
I thought that indicating the first frame of th sequence and the last one would suffice for APP to extract the comet's position in each frame.
If you need a couple of frames please tell me so that I can create a folder and upload there. I have 45 frames of 10 seconds each so please indicate how many of them you need.
There was a problem with the capture program, so I had to reinitiate it and then the camera was uncontrolled, likely the sensor got cooled too fast and showed some dark spots, likely ice.
Yes it can do that automatically, but that also depends a lot on if APP is able to detect the nucleus properly and it sounds like it can't in your data. This can be due to the data. You can upload the frames to our server so I can have a look (please allow for a few days):
Ok, I just created that folder and uploaded 15 frames.
I would highly apreciate if there is some help on how to use this comet registration automatically since when you image a fast moving comet, you need a lot of short exposure frames and indicating manually where the comet nucleus is takes a lot of time!
Maybe in my case there is some problem since the comet is close by a star.
Hope to hear from you when you had time to check my data!
No problem, being very close to a star may also throw it off. But it's always nice to have more data to test our algorithm on and improve it for sure. I'll let you know what I see later.
So I could register the data you uploaded fine, but the comet needs manual confirmation indeed. It may be due to the low signal on it, but Mabula is going to inspect both registration and see if we can improve the comet detection algoritm as well with your data (that will take longer).
