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 am getting the following exception with registering pre-integrated panels for a mosaic (calibrated projective, scale stop 12, flip descriptors in x/y, use dynamic distortion correction, NOT same camera and options.
What APP version are you using?
I'm seeing the same thing and am running on OSX v10.15.5 (Catalina
Encountered error in module:
OverlapBetweenTwoImageObjectsCreatorWorker
Error message:
java.lang.ArrayIndexOutOfBoundsException
Cause:
null
no trace
Then I upgraded to 1.080 from 1.077.3 which continuously crashed and was deeply unreliable. I then upgraded that to 1.082 and while it didn't crash, I was getting these errors as wel I circled back to v1.077.3 and am now getting these errors there.
I've attached a screen shot of the error and the registration panel. Previously, these setting worked really well with no issues. I can't process any of mosaic data at this point.
Is there any news on this issue or will it be fixed in a new version?
Well it doesn’t have to be a bug, it might be a data issue as well that sometimes triggers such an error. For that I would need the data to have a closer look.
@vincent-mod I don't understand how subs can make it this far (with loading, detecting stars etc) then it be a data issue. I'm using the exact same camera, optics, acquisition software I have for a long time now. This is new to the recent version of APP as well as the constant crashing.
Yes, well I'm not saying it's not a bug either, it's something I see a lot when there is something with the data. In your case you're right it usually crashes earlier in the workflow. Would you be able to share the data to our server to check this?
I think I found out the reason it was not working for me.
I tried extracting Ha/oIII from my one shot colour images by changing the settings in Step (0) away from Adaptive Airy Disk to "Ha-OIII extract Ha" and extract oIII. I thought this'd be a cool way to improve the overall image. This seemed to work OK to get the ha/oiii only images (and I could combine them as well) BUT I was then unable to figure out the specific process on how then integrate that back into my main image.
- Stacking/processing all the Ha/oIII into one image worked without errors
- Stacking/processing all the colour images worked without errors
I found the issue consistently presented itself when I was trying things like
- Trying to in "(1) LOAD" and using "multi-channel/filters" and load the main colour and the previously seperated Ha/oIII subs tagged against Ha and OIII respectively. It generated this error at normalisation even though they loaded and passed analyse stars etc.
- Trying to use the RGB combine the tool in (9)
- Take three already stacked/calibrated images and then simply try to combine them another stacking run
I've put some screen shots below showing the types of subs I was using to try to do this so you can see the exact error messages and how I had APP configured at the time.
Does this help?
PS While I'm at it, this error could entirely be because I don't know the process on how to take previously extracted Ha/oIII data and put it back into the main colour image. Is there a link to where this has been done before.
I think the error happens because you're trying to normalizing mono data with RGB data. That doesn't work as one is 1-channel and the other 3-channel, we have to make this easier for sure. What does work is if you first split the RGB into separate channels (tab 2, on the bottom). Then all the data is 1-channel and you can go through the entire process with those.
