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.
just downloaded the latest version of APP, and hoped it would solve my mosaic problem of a picture of the milky way. But sadly it has not. Any solutions for that Error?
I tried the mosaic mode of APP 1.079 as well. I started with over 200 raw images in an attempt to create a mosaic in one go. However, registering all images takes forever, as is to be expected. So I took the 4 integrated panels that I created with 1.078 and created a mosaic of that which worked wonderfully well.
Yes I just replied to your other post. I got that error also in 1.078 but using the settings that I posted in my comment I do not get the error in 1.077 nor in 1.079. Let's discuss that in your post.
I had the same and many other error or fail notices and pictures when doing a complex mosaic. And I'm serious. this is someones coding idea of fun when the program glitches. Needless to say I don't find it that funny after hours of work.
I see that you're on 1.078. Many bugs have been fixed in 1.079, unfortunately that is the nature of software sometimes. It's very unfortunate ofcourse, but we can investigate (that's why we're here) and fix this.
just downloaded the latest version of APP, and hoped it would solve my mosaic problem of a picture of the milky way. But sadly it has not. Any solutions for that Error?
You don't want to load the individual mosaic frames, that is very inefficient and much less robust.
You need to make mosaic panels first and register those as a mosaic 😉
Â
I don't know how the panels are arranged and how much overlap they have, but usually, to be able to register a mosaic successfully, you need to increase the star detection number to 2000-2500 from 500 in 3) Analyse stars.
In my case after studying carefully the tutorial, I managed to integrate successfully but only a limited number of panels.
My Integration worked for a max of about 16 panels. Is there is a limit to the total number of panels in mosaic mode?
I have a total of 45 panels in my project (a 50mm lens spanning a large span of the Milky Way). I found it impossible to have them all integrate no matter the settings. I keep getting NEP errors even with 0.1 size integration and a 64GB RAM machine (50GB allocated to APP).
I will try with another data set as I suspect a lot of my panels to have too much redundant data (50%+).
I told you that I'd tried everything. What you are seeing here is an attempt where I loaded all of the stacking data and then only selected the Lights for each panel. I also tried this in a an earlier version of the programme. Analyse Stars: I used 500 stars to make the stacks and 2000+ when making the panels into a mosaic as is your guidance. I've been through the tutorial you cited several times move by move (given that its not that relevant in places as its an older version) and Sara's video on YouTube. Its a good tutorial, It just won't work for my data or me or both.
In my case after studying carefully the tutorial, I managed to integrate successfully but only a limited number of panels.
My Integration worked for a max of about 16 panels. Is there is a limit to the total number of panels in mosaic mode?
I have a total of 45 panels in my project (a 50mm lens spanning a large span of the Milky Way). I found it impossible to have them all integrate no matter the settings. I keep getting NEP errors even with 0.1 size integration and a 64GB RAM machine (50GB allocated to APP).
I will try with another data set as I suspect a lot of my panels to have too much redundant data (50%+).
Is there is a limit to the total number of panels in mosaic mode? No, there is not.
Â
If you have so many panels with 50mm length, you need to be aware that your field of view will be huge in terms of degrees.
If the field of view is larger than 120 degrees, which is most likely the case for your mosaic, you need to use
the calibrated projective registration model
and use a different projection method than the default rectilinear projection. This is an example of an 180 degree mosaic where you need to use a different projection method.
If registration if the mosaic was good, then with a different projection, the problem that you face should be solved 😉
So register your panels as a mosaic with the calibrated registration model and set the projection to equirectangular or mercator :
Then the integration of the field of view should work properly. If you leave the projection at rectilinear, the field of view will start to blows up to infinity if the field of view is larger than 120 degrees... 😉
 Kind regards, Mabula
This post was modified 7 years ago 3 times by Mabula-Admin
