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 Mabula,
Â
I was trying to process some O3 recording but i get every time the same "java" notification (see attacht files).
For these recoriding i was using the Zwo Asi 071mc-c.
This is wat i was doing:
First tab,Â
Set te bayer pattern to RGGB,
Check: Force CFA
Algorithm: Oxygen III
Then, Loaded about 20 files (6 files of 300 sec. and the rest of 600 sec)
Loaded only BPM and Master Bias.
Push then the calibrate, this is oke,
Push then the Analyse stars, this is also oke,
but when i try to register the files ik do get every time the Java notification.
Also the files wil not be registerd.
Â
Am i doing something wrong?
Â
Jan-Willem
Hi Jan-Willem,
Thank you for reporting this.
It's not a problem with the O3 debayer algorithm. It happens due to a problem in 3) star analysis. This problem has been solved in the upcoming version 1.056.
See here for details:
FIXED, registration, if star analysis only found very little stars in a frame (less than 12) a null pointer exception would be thrown in registration, due to a boolean that was not set in reporting back registration status internally. This is fixed, the null pointer exception/java error is gone. Was triggered by several users in version 1.055 due to the change in the detect above noise level kappa values and calculation of the dispersion of the data. Screenshot of the particular error that was triggered and a screenshot, in case of failed detection, showing that the user is warned now.
The attached screenhot shows the IB.a error, the same as you encounter.
The problem lies in the default detect above noise level: kappa value. In 1.056 this value will be set automatically to solve this inconvenience. For now, you will be able to solve this, by lowering the detect above noise level kappa value in 3) before starting star analysis. Make sure that enough stars are detected in star analysis before proceeding with registration. Enough would be to have at least 100 stars per frame detected.
Let me know if this solves it for now 😉
Kind regards,
Mabula
Hi Mabula,Â
Â
Thanx for the explanation. I dit not know this was the problem. I will try it your way.Â
Kind regards,
Jan-Willem
