Remove long distance haze

Impressive what can be recovered.

My try:


D200_20070802_2088.NEF.xmp (10.9 KB)

1 Like

I wanted to take a look at your edit, especially the red (not) showing up but your sidecar doesn’t load on my side. Everything except WB is turned off when I load your pp3

Can you re-upload it?

And before you ask: Yep, I’m on the latest development version (5.8-2750-g6ad419f18)

1 Like

@Jade_NL thanks for your request, for this edit i used dev-2711. In the meantime, i am quite sure, those reddish colouring depend of the weird RGB curves, i created.

D200_20070802_2088.NEF.pp3 (14,0 KB)

edit: i tried to load the sidefile in dev-2746 and it worked fine…

2nd edit: i was wrong… the haze removal tool shows a saturation of 100 % - i dont know why… instead of recognizing this, i used the rgb curves as a correction.

3rd edit: and the output profile was set to my monitor , not to sRGB…

so pls forget about my question above

@marter: :+1: This sidecar loads nicely.

Nice job on correcting the overlooked 100% saturation!

The red is baked into this version and is indeed colour management related.

Anyway; Nice edit!

1 Like

@Jade_NL thanks :slight_smile:

Maybe a bit lighter

1 Like

Indeed

Edit: right with RT neutral profile, left with some simple processing

2 Likes

I had a look at a map. Distance was more in the 5 km range…

another try…
the other version is way too dark for me …

Remove long distance haze_D200_20070802_2088_01.NEF.xmp (10.0 KB)

4 Likes

Keep up the good work. Love the goatees! :goat:
The challenge is getting rid of the colour cast.

Yes, but the hard part is knowing how to use the raw-black points module.
Rawpedia says nothing about haze: http://rawpedia.rawtherapee.com/Raw_Black_Points
But it seems to work very well in conjunction with the haze removal module.

But … How do you get those 239-530-477 values ​​in this image?

The same here:

Where do the values ​​57-224-219 come from?

Do you have to calculate it by eye?
It must be a very well kept secret :))
Regards!

Changing raw black points alters the white balance as a side effect; however, it is counter-intuitive, so I don’t use this technique very much.

Typically, dehaze algorithms estimate what is called airlight (the particles in the air filter light like a lens) and use that to correct the colour. More advanced algorithms do pre- and post-corrections; and machine learning compares colours against similar subjects.

The RawTherapee poor_man_dehaze branch logs them in console when opening a raw :wink:

1 Like

(Of course, @heckflosse is quite clever. I am waiting for it to reach maturity… :wink:)

Well that is very good and very useful! I’ll wait for it to merge with dev one day … or on 5.9 !!
Thank you.

1 Like

I was wondering this myself, thinking that @heckflosse’s solution was rather nice/clever but maybe not that practical.

Just merged that into my dev branch; That’s a nice one!

At its current info from the terminal state it is somewhat poor-mans indeed, but rather useful in some cases nonetheless! I’m sure you come up with something streamlined in due time :relaxed:

1 Like

dt 3.4.1

D200_20070802_2088.NEF.xmp (6.5 KB)

1 Like

RawTherapee
Thanks for the black points tip… :grinning:

D200_20070802_2088.NEF.jpg.out.pp3 (15.1 KB)

4 Likes

That also works in darktable btw, but there you have to enter the black levels in a different order (at least for Nikon D200 files) which makes it a bit harder…

In darktable for this file you have to use 530, 239, 477, 530

1 Like

@heckflosse

I wasn’t able to use the_poor_man :blush: and i found the black points looking at Art raw histogram. Values of green and blue was a bit different from yours. :slightly_smiling_face: