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.
Should I wait for integration to finish or it's already "done" after this exception?
Hi Maxim @mseningmail-com,
I have never seen this exception earlier. The LNC algorithm in beta4 is identical to 1.083 stable, so it is very likely that the LNC calculation can not complete due to some problem.
For beta5 probably and definitely 2.0.0 stable, a new LNC algorithm is being developed which must be better, faster and use less RAM. It will be LNC 2.0 🙂 I am working in this at the moment.
So for now I would suggest you tro try LNC 2nd degree and let me know if that does complete on your data. Maybe if it also fails, it will be good if you share your data so I can test it for LNC 2.0 as well 😉
I think the error prevents the stack from completing unfortunately... I will also fix that going forward.
Mabula
Hi Maxim @mseningmail-com ,Â
After the Java exception there is no point in waiting. If I am not mistaken, You'll need to quit and restart APP again.
LNC works for me up to 6th degree (I did not yet try more, though).
But LNC is highly depending on CPU single core speed as well as  SSD & bus speeds and RAM size.
Depending on Your computer it might be more or less. 2nd degree should work though and already provide nice results using 3 iterations.
Hi @Mabula-Admin
looking forward to LNC 2.0! - once this works on multi-core code it might scale by a factor of 3 or more...Â
Â
Thanks. Looking forward to the new version!
I can only add that this happened with 2 sessions of NB data from same optical train, when I chose "Integrate - per session and all", and to apply L4 LNC with 3 iterations on individual session stacks and final stack. And reproduced it again on 2-session stack where images were from two different optical trains. All same settings except for registration (dynamic distortion I unchecked "same optics" and checked "flip descriptors X/Y" and increased scale stop to 15. Both cases drizzle 2.0. IDK if that helps anyhow.
Hi Mabula, glad to hear you were working on LNC 2.0. Is it possible to process very large stacks, say over 1000 frames and more, with the new version? With large stacks I always get the message Can,t get Sample Size and LNC was not applied.
With best regards.
Another exception in 4th degree LNC processing 2-session stack. Different this time:
