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.
Never had this issue before, but LNC seems to freeze.
Log:
15:55:06 - 6) INTEGRATE: integrate light frames: LNC: got center coordinates and area of frame 15 in integration composition
15:55:06 - 6) INTEGRATE: integrate light frames: wrote frame: 15 to file mapper
15:55:06 - 6) INTEGRATE: integrate light frames: LNC: starting Local Normalization Correction...
15:55:06 - 6) INTEGRATE: integrate light frames: LNC: Starting Local Normalization Corrections with 3 iterations...
15:55:06 - 6) INTEGRATE: integrate light frames: LNC: allow simultaneous read/analyse = true
15:55:06 - 6) INTEGRATE: integrate light frames: LNC: allow simultaneous write/apply = true
15:55:47 - 6) INTEGRATE: integrate light frames: LNC: iter 1 analysing light 15
15:55:47 - 6) INTEGRATE: integrate light frames: LNC: iter 1 performing LNC calculation...
Then it does not do anything and after 20+ minutes I cancel the work.
Could you please advice me how to proceed?
Â
Disable LNC works. Not sure why.
Thanks for reporting, can you tell me more about your system as well? I'll forward this to Mabula.
Hi @oscar-keet,
THe LNC algorithm has not been changed in quite a while, but we are working on a new and improved version already. I have never experienced LNC stalling though so this is new for me, especially when only 15 frames are loaded.
I think we can solve this quickest if I can see the data and test myself?
Can you upload it here:
https://upload.astropixelprocessor.com/
username: upload
password: upload
Â
Make a folder with your name and issue like : OscarKeet-LNC-issue
And let me know once uploaded 😉
Mabula
Â
Â
Thank you. The files are on their way, but it adds up to a total of almost 60GB, so it could take some time before everything is on your server.
To be honest, I've never had issues with LNC either, so I was somewhat suprised. I did another 'run' today and I got the same isse. I also added a log file in the map. Maybe it can help solving this.
My PC is an AMD Ryzen 5800X 8-core processor, 64GB of RAM. It runs on a fully updated version of Windows 10.
Kind regards.
Just for me, you finished the upload? Maybe 60GB wasn't required, if it would also happen on less files. 😉
@vincent-mod Yes, it's all there.
Hi @oscar-keet,
Thank you, I will test it within a couple of days and will let you know my findings 😉
Mabula
Hi Oscar @oscar-keet,
I have tested your data. There is a big data issue in your dataset and that is responsible for the subsequent issue in the LNC algorithm.
You first need to fix your data calibration. I have analysed your lights and calibration subs and the issue is very likely in your darks.
The lights, flats and flatdarks all seem fine and were shot with N.I.N.A. 2.1.0.9001
Ligths were shot with sensor gain 200 and offset 8.
Flats and flatdarks were shot with sensor gain 0 and offset 8.
The darks however were shot with different software, INDI, no indication of version here. The gain is not compatible with your lights, it is 125. The real culprit is the sensor offset of the darks, it is 30 as reported by INDI.
So the darks are very likely the issue. When the masterdark is sutracted from the lights you can clearly see the data is damaged.
When the darks are subtracted from the HA frames, well not much data is left even with the adaptive pedestal enabled...
So, the solution is very likely: shoot darks with NINA that are compatible with your lights, meaning, the darks must be shot with 120 exposure, 200 gain and offset 8 and -10 Celsius ideally.
Then very likely LNC will work as well. I think LNC stalls on having 0 sky background values due to the too large sensor offset in your darks.
I have added to our work on a new LNC algorithm that it should detect this and better handle the issue as well.
Mabula
@mabula-admin Thank you!
I've made these darks a while ago, when I was still using Astroberry.
I'll create some new ones and try again. Thanks alot.
Â
Yes. It was!
Sorry if I wasted your time with a totally beginners issue. I just started using NINA and did not update my darks. I created new darks and it all works fine now.
Â
Thank you!
Excellent !
