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.
[Solved] 1.076 Beta 3 - Integrate Slider 100%, Says 0 of 72 frames will be stacked
That is an interesting one, I'll forward it to Mabula. I guess it's either a bug or something in your settings. Thanks for letting us know! One question; why are you saving the calibrated frames in between, does it work when you just skip that and go for integration straight away? Does it work when you save your frames at the normalization step instead of the calibration step?
I save the calibrated frames because I am imaging over multiple nights and my workflow is to calibrate and save the calibrated frames each morning, since that requires loading the session-specific calibration frames. Then when I've collected all the data I load the calibrated frames and do the remaining steps.
I reverted to the previous release so I could get things working, so at the moment I am not able to test it with saving the normalized frames.
I will check if I can duplicate your issue, is there any change that you can upload either the calibrated frames or some lights with the masters? Then I can duplicate the problem quickly and fix it 😉
Thanks for uploading your data, it is different data than on which you post the problem and I am not able to duplicate the issue I am afraid.
You uploaded lights with filter B and they process fine, also on the calibrated saved frames, also when forced with a filter H as shown in your screenshot:
Maybe it will help if you upload the data (SH2-240 H filter) on which you get the issue? Or do you get it on this dataset as well, NGC_1333 B filter ?
It will also be very helpfull if you can show exactly the output in the console panel after normalization finishes and integration would need to start, thus where it stops in your case 😉
It's still uploading - actually there are errors with the upload so not sure what happened.
I was going to give you instructions after the upload finished.
With this data set, it integrated the L frames but didn't integrate the R, G or B's. (it said 17 of 41 integrated even though I had the slider set to 100%).
I tried the data set with H frames yesterday but using pre-built Master Flats and it integrated all 41 frames, so I decided to use this data set that showed the problem. I don't know if all the steps are needed, but the problem has occurred when I follow this flow.
1) Load master dark, dark flat and BPM
2) Load flats, create flat masters
3) Load lights, save calibrated frames
4) Integrate
The problem did not happen when I just loaded calibration masters, lights, and then integrated.
I'll try to finish the upload of the data set that failed today (LRGB) and later today I will re-try the H only data set including building flat masters and see if that fails.
Good news, I was studying my code and I have already located the issue now, it will occur if you use filter assignments/names of only 1 letter and if you have more than 1 filter assignment in APP's memory. I can duplicate the issue now:
For instance, if you have an R and B filter assignment, things will not work well. I am fixing this now to make this 100% reliable 😉
Thanks for bringing this to my attention 😉 Rowland.
