Why doesn’t Darktable’s histogram match my Canon 6D’s in-camera histogram?
Asked 4/24/2018
4 views
2 answers
0
When I import Canon 6D RAW files into Darktable 2.4.2, the histogram looks very different from the one shown on the camera. I also applied the Canon 6D base curve, but the image appears too bright. I even tried calibrating the base curve without success. Why doesn’t Darktable match the camera histogram, and what should I check?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
8y ago
2 Answers
4
First thing to do is to check the "mode" of your histogram. Darktable has three ways to visualise the histogram. One is the 'normal' one, which is linear in intensity, the second is logarithmic in intensity, and the third is a "waveform" display (I never figured out what the use of that one is). To see which mode is displayed, hover your mouse over the histogram. Four squares will appear: left to right display mode, red channel, green channel, and blue channel. Clicking on those squares cycles through the states.
So try clicking (perhaps a few times) on the left square until it shows a straight line (log mode will show a curve, waveform mode some kind of squiggles).
Then, there are a few basecurves for Canon provided. Perhaps one of the alternatives gives a better results? Nothing obliges you to use the camera basecurve. The manual even suggests not using that module at all, if you want to take full control through the "tonecurve" or "zone system" modules.
The basecurves are supplied as an easy way to get close to your camera's rendering of the raw files. Some, however, rise very fast, and can easily lead to clipping in the final image (on which the histogram is based). Try using the "cubic spline" to see the image without any curve applied.
Originally by user72870. Source · Licensed CC BY-SA 4.0
user72870
8y ago
0
Generated from our catalog & community — verify before relying on it.
This is normal in many cases. Your camera’s histogram is usually based on the embedded JPEG preview, not the untouched RAW data, so it reflects Canon’s own tone curve and processing. Darktable applies its own rendering, which can produce a different histogram and brightness.
A few things to check:
- Make sure Darktable’s histogram display mode is set the way you expect. It can show linear, logarithmic, or waveform views, and these look very different.
- In your screenshot/history, the base curve appears to have been applied twice. That would make the image look overly bright and change the histogram significantly.
- Darktable may already auto-apply a default base curve for your camera. If you add another one manually, you can effectively double the tone curve.
- Canon and Darktable tone curves simply won’t match exactly; that’s expected.
So the main fixes are: verify the histogram mode, check that base curve is not applied twice, and remember that the camera histogram and Darktable histogram are not expected to be identical for RAW files.
Recommended products
UniqueBot
AI8y ago
Your Answer
Related Questions
How can I manually access hidden base curve presets in darktable 2.4?
How can I make a darktable RAW edit match my camera’s out-of-camera JPEG color more closely?
Why do Darktable and Lightroom render the same RAW file differently by default?
Why won’t my Canon 6D connect to a Windows PC over USB?
Why does darktable not detect my Canon 1300D for tethered shooting when gphoto2 works?