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.

[Solved] Dithering

4 Posts
2 Users
1 Reactions
4,321 Views
(@evolve)
White Dwarf
Joined: 7 years ago
Posts: 12
Topic starter  

Good Evening

I try to solve my Walking Pattern Noise

So I do dithering and I checked the Pictures it works. (each picture 5 pixels)

Do I have to set something in APP that this Noise goes away ? A Friend said maybe activate something like outlier (he doesn't have APP) . Because after Stacking I still can see Walking Pattern Noise.

CS Sebastian



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 
Posted by: @evolve

Good Evening

I try to solve my Walking Pattern Noise

So I do dithering and I checked the Pictures it works. (each picture 5 pixels)

Do I have to set something in APP that this Noise goes away ? A Friend said maybe activate something like outlier (he doesn't have APP) . Because after Stacking I still can see Walking Pattern Noise.

CS Sebastian

Hi Sebastian @evolve,

In which APP version is this? Have you tried in 1.077 or even 1.078 ?

If walking noise is still visibile, then it is caused usually by hot pixels or fixed patterns in your camera's dark current.

Are you using a Bad Pixel Map? If not, try calirbating with a Bad Pixel Map as well in 2) Calibrate.

In 6) Integrate, you want to use an outlier rejection filter to remove outliers, that should ged rid of remaining walking noise. If it is still present though, maybe the dithering steps were still to small?

Perhaps you can show a screenshot? How many images did you integrate?

Mabula



   
ReplyQuote
(@evolve)
White Dwarf
Joined: 7 years ago
Posts: 12
Topic starter  

Thanks for Helping me

I create a BPM and a Master dark Flat one of those reduce it much.

I tried also the outlier rejection by hand but I didn't see a different to automatic mode, so I guess the Program did it right



   
Mabula-Admin reacted
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 

Excellent Sebastian  @evolve, I think it is the addition of the Bad Pixel Map.

Walking noise is caused by hot pixels in your data and the BPM is there to get those corrected at the calibration frames already 😊 

Mabula



   
ReplyQuote
Share: