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.
Hello and happy new year!
I'm actually using the trial-Version of APP 1.082 on a WIN10-PC and try to get used to it.
When re-editing some older data which I had formerly processed with Siril, I got this error-message:
Encountered error in module:
ImageNormalizer
Error message:
java.lang.ArrayIndexOutOfBoundsException: 3
Cause:
3
n.a(Unknown Source)
n.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
The lights are RAWs from Canon 6D, I also loaded the master dark and master flat processed by Siril as FITS-Files, since I could not find the original RAWs at the moment. After loading the files I went directly to Integrate.
I hope this is enough information for you to be able to help me with this problem. Some older posts with similar questions in this forum always ended after the first answer which was a request for more detailled information 🙁
Hi Kurt @kukro,
Happy 2022!!!
Can you please first try with our latest 1.083 beta 4 release? Download links are at the top of the forum.
Your bug could be related to using master frames from a different program, especially since it concerns Bayer (Color) data. Different application deal differently with this. Is there a way to remake the masters? Otherwise we might have to inject the Bayer pattern into your Siril masters as a solution.
If the 1.083 beta 4 gives the same error, then I will be happy to look at your data and fix it.
Mabula
Thanks for the quick reply. I shall try the beta and then come back to you.
Kurt
We actually are on 1.083 the full version already. 🙂 Also to be found in the link on top of the forum.
We actually are on 1.083 the full version already. 🙂 Also to be found in the link on top of the forum.
Yeah, found that out too, thanks.
I also found the (my) error: within the directory of the light raws (which I had marked all to load into APP), there was one image which I had processed with LR and exported as TIFF, since it contained a meteorite trail. After removing this file from the file list, everything worked out fine.
Thanks for your help,
Kurt
We actually are on 1.083 the full version already. 🙂 Also to be found in the link on top of the forum.
Yeah, found that out too, thanks.
I also found the (my) error: within the directory of the light raws (which I had marked all to load into APP), there was one image which I had processed with LR and exported as TIFF, since it contained a meteorite trail. After removing this file from the file list, everything worked out fine.
Thanks for your help,
Kurt
Thank you Kurt 😉
Happy to hear that you found the cause of the issue. I think it is because you mixed data that still needed debayering and a Tiff that was already debayered, right?
Issues like this should be caught properly and dealt with in 1.084 on which we will start working tomorrow !
