I was trying out geeqie because of another thread I was reading, and I came across some old raws from a drive location I had paid no attention to. I started working on this one in dt 3.4.1. I have not finished it, but I became stumped when Filmic RGB turned it back to a very dark image. I discovered that (I think) that is because there are out-of-gamut blacks. So I tried to get them back with the Filmic black and white relative exposure controls. Am I on the right track? Or, is there some generally accepted methodology for dealing with this?
The reason you ran into this way-to-dark problem is because darktable isnât all that smart when applying auto scene referred settings. Especially in this case because it could be picked up easily and resolved by darktable while parsing this RAW.
The actual problem is this: You use scene-referred, which activates and sets filmic and exposure. This does not work correctly when you shoot manual and, for whatever reason, have adjusted the exposure compensation button on your camera. darktable blindly add/subtracts the found value (+3.3 in your case), which it shouldnât do when you use M(anual) mode because in that case is doesnât change any of the ISO, speed or aperture settings.
It is one of the reason why Iâve set my workflow to none and do it all manually. I always shoot in manual mode, dial-in my settings using the (live) histogram. I then use the exposure compensation button to change the lightmeter setting (which is the only thing the exposure meter changes in Manual mode) to the exact middle so I can have an easy indicator that I need to adjust my settings by 1/3 or 1/2 stop or redo the whole dial-in process if there is a larger difference.
I start my editing session by backing out of the pre-applied stuff, including highlights adjustment. Then, I do exposure, color calibration, and filmic. Then other modules as I finish the ways I want things to look. So, at least in my mind, I am bypassing most of that. Maybe Iâm fooling myself.
For this image, all I had before I started at White balance was Original, Orientation, Raw black/white point, Demosaic, Input color profile, Output Color Profile, and Display encoding.
I kinda stopped using darktable for my personal stuff but I do tend to start as bare-bones as possible, no matter the RAW editor I use. Those auto-applied âgoodiesâ come with their own caveats, I rather mess things up myself
I think it also depends on how many images you want to edit. If you have hundreds of shots from a wedding, an automatic start might come in handy .
However, in general want to see (and feel) the raw before I decide what to do with it. So I try to start with as few operations as possible (demosaic is okay though ).
First, a bit of terminology: Thereâs no gamut in âblackâ. Black is the absence of light energy and gamut is about the ability of rendition media to resolve colors of extreme energy, at the other end of the energy continuum, so to speak. What youâre probably concerned with are negative values, which are the product of manipulation.
The data right out of your image has no negative values; indeed, the minimum value of any channel is about 147. The interesting thing I found is in the NEF metadata, the MakerNote tag BlackLevel contains four values, all 600. If you subtract that from each pixel, you drive most of the meaningful data in the image below 0, given that the maximum value for this camera with itâs 12-bit sensor is 4095. Libraw delivers a more sensible value, 150, which contributes to a âmore colorimetricâ image.
Assuming negative values are clipped to 0 by black subtraction, I found a few subsequent operations that would drive values negative: some demosaic algorithms, lanczos resize, and convolution sharpen. The all affected only an insignificant number of pixels, my export conversion clips all such to 0 and the image looks fine.
Also, this image responded to a rather tame filmic curve. I canât comment about the darktable filmic; I started with a simple normalization of the linear data to 0.0-1.0, and I only had to boost the B param of rawproc filmic to 26.2 (from 16.2) to get this, in rawproc:
Iâm posting the 800x600 proof to demonstrated the value of rendition resizing in reducing noiseâŠ
This is a really good demonstration image for all of the raw-processing fundamentals; with your blessing Iâd like to use it in a demonstration videoâŠ
Thank you Glenn. While much of that is still over my head, that is the sorts of answers I was asking for. I am more trying to learn what was wrong, in general, and how to deal with it, in general, than how to edit this specific image.
I took the history all the way back to âoriginalâ and compressed the history stack. This gives that there are no out-of-gamut pixels, and a very dark image (expected).
But the pipeline on the right still shows several modules as active. The one lowest in the stack is âraw black/white pointâ. darkroom does not allow me to deactivate this module. And when I click on it, the out-of-gamut pixels are highlighted.
All four black levels are shown as 150 in the raw black/white point module. White is shown as 3880. So, I think you may be suggesting to change those 150s to something else. I will play with it and see what happens.
PS - If I change them all to 141, there are about three highlighted out-of-gamut pixels. If I change them to 140, there are none.
And here is my âfinalâ (heh heh) attempt based on the above post, with the raw black points all set to 140. I donât know why the numeric suffixes on the files differ, but the files were created at the same time.
There are a handful of modules (5) which cannot be disabled. Those are the bare minimum needed to go from a bucket of bits (the RAW file) to a very basic âviewableâ image.
.
).
