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.
Looking for help with error message when calibrating
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
Regarding your last post, I may be wrong but my understanding is that a Master Dark used for Scaling must be created with Dark frames and Bias frames, not using a Master Bias file????
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
TY to all who considered this.
Hi Kevin @kevinkalikimaka, that is great. Thank you very much for your feedback. I did implement a fix for this error and it should not happen again with 2.0.0-beta38 or later 😉
@jhart that is not correct, to have scaling working on the masterDark, the MasterBias must be present. The MasterBias is subtracted form the MasterDark and then a noise analysis on the subtracted MasterDark determines the scaling factor(s).
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
