Please try to save this overexposed image in Darktable

Very nice contrast and colours, thanks. Punchy. I like it a lot!
Still a bit washed out floor, but I guess that’s the limit for DT 3.0.2, the way it handles extreme overexposure?

We could crop the front part and focus on the people and have totally usable photo here.

My try:


_V3A0302.CR2.xmp (8.3 KB)

4 Likes

Very nice editing too! A bit hdr-like. :slight_smile:

Thanks guys, I learned a lot from your changes!

The latest filmic rgb (v4; not available in 3.0.2, but in 3.1.0) has an excellent reconstruction option. This works in union with the highlight reconstruction module (and also exposure). It can do things that are not possible in the current stable versions.

The original does seem to have a hint of clouds (hard to be sure due to the clipping), but I have to admit that it is rather hard to get that back and it does result in a darker/stormy/sombre end result.

3.1.0 is the latest development version and not yet available for the general public. If you are willing and able you can build it yourself (build guide on GitHub). It is updated daily and not always as stable as you hope for (it is development…).

In August the new, stable dt 3.2.0 will arrive which holds all the goodies that are already available in 3.1.0.

The xmps created with a newer darktable are not compatible with older version (and might hang dt when trying to load them), hence the mentioning of the version(s) that I used if not the latest stable :slight_smile:

1 Like

I have darktable 3.1.0+2446~g7d3d982d4 (compiled from git development a day or so ago) and used filmic RGB 4.

First attempt was to let the recover highlights module work in LCR mode.


_V3A0302.CR2.xmp (13.0 KB)

After that, I made a pristine copy and turned off the recover highlights module, letting filmic do all the work on highlights.

I wanted to make the focus of the image the people, so I added a tone equalizer (to lighten the subjects and darken the top and bottom, more or less) and a duplicated exposure with a feathered, fuzzy, inverted circle mask over the area with the people (so that everything else becomes darker).

However, that affected the data filmic got, so its highlight handling let in too much semi-clipped data. Magenta invaded.

I then dialed back the highlight color, but it took away a little too much color in some of the non-sky (and sky reflection) color in the image. So I moved the highlights color back up and got a magenta cast in the sky (and reflection) again.

I then compensated for the magenta by “painting” a blueish color back using the colorize module with a parametic mask, to only affect the magenta color and then added two lasso masks to generally select the sky and the pool. Of course, then I feathered the mask.

Yes, painting the color on the sky is cheating a bit :wink: , but it’s done at the end of the pipeline and it it looks natural enough. I don’t know if the sky was completely grey, a touch blue, more blue, or some shade of magenta (due to a sunset) in real life. I’ve opted for a slight desaturated blue, which is most likely.


_V3A0302_01.CR2.xmp (12.2 KB)

I went back to the image a third time to create a simplified version where I don’t add any additional modules in the scene-referred mode (official mode in darktable > 3.1.x, which is filmic-powered), yet only have filmic handle the highlights (again), to show a mid-step, and got this:

_V3A0302_02.CR2.xmp (5.9 KB)

It’s a little different from where I started with the middle photo, as the parameters have changed. However, as it doesn’t have the tone equalizer sandwiched in-between exposure and filmic, it lets filmic handle the extremes better, and doesn’t need the compensation, like the one in the middle.

Perhaps reordering the modules might make sense for this photo, to let filmic handle the highlights better and still be able to adjust the tons of the image with the tone equalizer.

Everything’s a tradeoff, I suppose?

So here’s one last one, where I built on the previous simple version, letting filmic handle the highlights itself, but reordered the modules to stack tone equalizer on top of filmic, then added a second exposure on top of that (to slightly darken everything but the subjects):


_V3A0302_03.CR2.xmp (9.1 KB)

Edit: After seeing the image here, I’d probably further work on it, by making a mask for the equalizer to let the pool reflection shine through and then add another exposure module on top with a mask to slightly darken the chair highlights.

But, overall: This was a fun challenge and it was interesting to try out filmic 4’s highlight recovery.

1 Like

@maboleth
Now you got some results from DT users, do you mind if I post result from other SW as it is an interesting exercise? or is it too soon?

2 Likes

Another attempt trying manual highlight reconstruction using the channel mixer module.


_V3A0302.CR2.xmp (22.1 KB)

5 Likes

No, of course, go ahead. I’m mostly here to learn more about DT and how people fix/edit things means a lot!

Thanks a lot! You really tried so many ideas.

I think I like 3rd one best. It looks like a good tradeoff between nice contrast and resurrected whites.

1 Like

I had a little fun with this one. How about this:


Except for one, small step, this was all done with darktable…

Not entirely fair though, this being a composite of 2 images :grin: This is your image with part of a sky/clouds from one of my own shots and it was done using the watermark module.

The watermark module takes an svg as input and darktable does not export to svg so I had to use inkscape to convert to svg, which is the ‘small step’ that isn’t done with darktable.

2 Likes

Nice. :slight_smile: Even the reflection in the water looks like it was covered with the same type of clouds you added.

I’m so happy that DT 3.2 would offer much better tonal reconstruction of the overexposed floor tiles! Can’t wait for the final release. Rumored 1month from now.

3.2 is scheduled to be released August 10.

Experience learned that these planned dates aren’t written in stone though, it might be a bit later/earlier.

1 Like

My take with ART


a-_V3A0302.jpg.out.arp (13.4 KB)

Log tone mapping, highlight reconstruction/color propagation, local contrast, color correction of sky.

Replacing the sky as done by @Jade_NL is the solution when sky is completely white to save a photo.

1 Like

Thanks! Current (a)RT has the best highlight reconstruction of all! Floor tiles look totally nice.

Yeah, when sky is dead flat, you can do what Jade did with 2nd image or do some slight bluish cast as he also did on the first image. Anyway, very nice!

Sorry another non Darktable post. I found that Rawtherapee always had the best highlight reconstruction ever since I started using it in 2007. At that time it was far better than any commercial software.
In ART you can also apply the dehaze module specifically to the highlights and this emphasises any details in the highlights. It is good for bringing out textures in clouds.
On my phone now so don’t have examples.

1 Like

Totally agree. That’s why I wanted to see how DT guys process overexposed images, since I moved to DT due to speed reasons.
I still use RT for what is needed and I consider it superior to DT in RAW engine (color noise removal, highlights, capture sharpness, 2nd monitor usage for film strips etc.), but speed/responsiveness is really lacking (also lacks that very useful blend&fade feature for each module DT has).

However, what guys here showed me, future DT 3.2 will see big improvements in highlight reconstructions. Can’t wait to try it!

That’s funny, I find completely the opposite, RawTherapee and ART both run really speedily on my computer, but Darktable is very slow. ART seems to have the best of all worlds to me…

Here Luminar works better, in a very short time.

really … ??? Please compare with e.g.

and others!

Hermann-Josef

Well, new DT uses OpenGL a lot, so it should be faster than RT by default.

Still, what I was comparing the most were the files in file manager (lighttable). Switching back and forth, zooming in, previews, developing and going back to lighttable is super fast in DT. Unlike RT where the more files you want to develop the slower and slower the program gets.