2026-10-09 APP 2.0.0-beta48 has been released !
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.
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1
The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
I've just realised it is possible to process Calibration frames (like Darks) without associated Lights, so perhaps this is isolated to Flats/DarkFlats [I updated the topic to specifically target these]
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
Hi @itarchitectkev,
Let me check this, I will get back to you 😉
I've just realised it is possible to process Calibration frames (like Darks) without associated Lights, so perhaps this is isolated to Flats/DarkFlats [I updated the topic to specifically target these]
Off course, that should be possible and I do it all the time ;-). Simply load some darks, bias, flats and create some masters without loading lights, that should work without any issues.
Mabula
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
Hi @itarchitectkev,
I just tested this in 1.076 beta4 and no NullPointer is thrown. In which version is this happening and does it happen everytime you try this?
Creating master frames is irrelevant to lights being loaded or not. They will simply be created. If you assinged them incorrectly. Then you can always assign them correctly, by reloading those created masters. You don't need to recreate them ;-).
Mabula
