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 have tried with other programs and the result has the correct colors. The stars are wrong because I had to put the shims for the backfocus, but the colors are correct.
I have experienced the same problem. Here is an integration for M42 using duo narrow band filters. Here is also the image after loading it into the "remove light pollution" tool and the image after applying the " remove light pollution". Note that these images display fine in pixinsight. So definitely
something is wrong with the way APP is rendering/displaying these images
At first glance I didn't see real issues with your data, after integrating using the different master-darks and masterflat, this is what I got (using APP 1.083.2):
Normalization on or off doesn't produce weird colors either. I didn't use LNC or MBB.
I didn't select to use any narrow-band filter for this. What kind of filter did you use? I can check further what happens when I extract the channels. The result is at least the same when using the Ha-OIII color algorithm from tab 0.
I load the light, dark flat bias .. then as always I go to card 6 and change them something. I was unable to log in with my credentials to post the files online. I use an l-extreme
So that means you process first by extracting the narrowband data right? Not straight away loading in the data, integrating RGB and then the combineRGB tool? Because that's preferred, first extracting the narrowband data, (Halpha and OIII separately) making integrated Ha and OIII files, normalize those against each other and save the normalized frames and only then combining them in the combineRGB tool.
I think it's coincidence that it worked in the other objects, there the histogram also doesn't look correct to me. What exactly is the method you follow then, how do you use the combineRGB tool? As said, it's best, with narrowband filters like the one you use, to first extract the narrowband data. I'm trying that now with the data from afnaguib to show.
Sorry but it seems to me that we do not understand each other. My English has remained at school level. I read but to write correctly I use the translator. The method I use I wrote above. The HOO test was to show that I get the same results as both Airy disc and HOO in tab 0. Bye.
That is fine Paolo, I didn't know that. I think I may know the answer though, you're working in the Light Pollution correction tool probably and have the preview window set to "neutralize-BG", this can go wrong when you do both and can show this result. Mabula will force APP to switch off the neutralize-BG while in this tool. So, switch off neutralize-BG there and it should work.
4- For tab 6, I use adaptive rejection with local normalization rejection "ON". I also set local normalization correction with LNC degree set to "2nd degree LNC" and LNC iterations set to "3"
So the only major difference I see here is whether LNC is used or not.
Note: I am using the Optolong L-eXtreme duo narrow band filter, ASI2600MC
@vincent-mod In your reply to Paolo you mention that, if I use the Ha and OIII extraction integration option, I should normalize these integration against each other and then use these normalized integration in the RGB combine tool. What if I will use them with another RGB integration (for example a broadband integration of M42). Should I normalized the BB integration against the Ha and OIII integrations as well before using RGB combine tool as well?
@vincent-mod wrt to forcing the neutralize-BG to off when in the remove the light pollution tool, I want to point out that I tried that and still the same result, e.g. strange colors
@vincent-mod In your reply to Paolo you mention that, if I use the Ha and OIII extraction integration option, I should normalize these integration against each other and then use these normalized integration in the RGB combine tool. What if I will use them with another RGB integration (for example a broadband integration of M42). Should I normalized the BB integration against the Ha and OIII integrations as well before using RGB combine tool as well?
If you want to process narrownband with RGB, the best approach is to first split the channels of the RGB data to R, G and B mono data. These can then be loaded in again, together with any other mono data (like Ha and OIII) and integrated together. You'll then get integrated Ha, OIII, R, G and B results. These should then be ready for the RGBCombine tool. If you don't process that mono data together, but on their own first, then you load the integrated data as lights and go to the normalize tab to normalize them and then save them. Those can then also be used in the RGBCombine tool.
@vincent-mod wrt to forcing the neutralize-BG to off when in the remove the light pollution tool, I want to point out that I tried that and still the same result, e.g. strange colors
That is strange as I'm using your data for the above results. You are using 1.083.2 right? What happens if you do what I did, so just loading in the data, not changing anything, going to tab 6 and clicking on integrate?