Question on LNC pro...
 
Share:
Notifications
Clear all

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.

Question on LNC process running eventhough configured to none

4 Posts
2 Users
0 Reactions
1,436 Views
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

Hi all,

I was just integrating 2 sessions with some 240 frames and when integration finished

suddenly the LNC process ( with the running "balls" ) started to analyze all the frames

before starting the integration of the frames.

This took up quit some time for nothing!

Is there some way to prevent this happening?

Here is the console output:

analysing frames of integration-RGB-session 1_session 2 for Local Normalization Correction
11:20:23 - 6) INTEGRATE: integrate light frames: LNC rejection parameters: analysing light 235

where my configuration was this:

Question APP

Thanks for any feedback!

Ah, I forgot to mention the version of APP I'm using: AstroPixelProcessor_2.0.0-beta13-Windows-64-bit

CS,

Mert



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Yes this can be a bit confusing, but the LNC rejection is something different from the normalization.



   
ReplyQuote
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

Evenso Vincent, LNC is the local normalization correction that was configured not to

be done ( Tab 6 Integration )!

The normalization was done as always. ( tab 5 Normalize )

So my question is why that process is started as if LNC was configured to be done

and once all the frames are analyzed for that, this is just disgarded and the integration

continues just like that.

In this case it were "only" 235 frames and it took quit some time, imagine we are talking about

bigger projects with many more frames, then the time lost will be huge!

To me this looks like a little bug, but hope to hear more about this!

Best regards,

Mert



   
ReplyQuote
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

I tried on my new laptop and it didn't happen ding the same procedure/parameters.

So I reinstalled APP on my old laptop and now it runs normal again, strange

but anyways, seems that the prblem has gone away!!

Just wanted to let you know.



   
ReplyQuote
Share: