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.
Those errors are weird and should be fixed. I have never seen this in all my testing to be honest. Is this happening with this dataset each time? Or did these problems only happen once?
If it happens each time, we need to see the data so we can fix it properly, please upload the data here then:
I have fixed the issue in FindBestRegistrationModel. I will work now on the other bug in FrameDataCalibration. Can you possible upload your data so I can solve this properly?
Fixed ArrayIndexOutOfBoundsException in FindBestRegistrationModel
As reported here https://www.astropixelprocessor.com/community/main-forum/arrayindexoutofboundsexception-in-findbestregistrationmodel-while-registering/#post-34227 an ArrayIndexOutOfBoundsException could be thrown when registering in the FindBestRegistrationModel module. The issue will be caused when dynamic distortion correction is enabled. When disabled all works as expected. The issue would manifest if APP tries to calculate distortion correction on data that really does not need it for already perfect registration. The issue is now solved and prevented by simply disabling distortion correction completely in the 2-view registration phase on data that has very little movement in the stars between the images. The user can simply leave distortion correction enabled, internally, APP will disable it for the specific registration task.
Thank you dear Mabula. That’s good News. Please tell me whats kind of info do you need me to upload? I have been experience this with any of my integrations. Didn’t happened with older versión. I changed with the 40 and 39 versión and happened similar. But I know you will fix it
This post was modified 6 months ago by hector Duran
Please make a folder with your name and issue like: Hector-CalibrationError
and upload the dataset into that folder. Then please let me know once you have completed the upload. I will make sure the issue will be properly fixed then.
I already located the error to the Bias calibration. Do you load many bias frames to make a masterbias, or do you load perhaps multiple masterbias frames? Please share as much detail as you can, so I can repeat the error on solve it with 100% certainty.
