Not sure why the CC module seems to have a bias toward warm color balance. In the example below, the first image is with default camera WB and it is already pretty close to neutral WB (according the the color picker values). The second image is after CC after sampling the grey patches and as you can see it is too warm. Am I missing something?
Note: The color checker was illuminated with daylight LED.
Is white balance set to camera reference in the second screenshot? Which camera?
I had something like this with my Canon 5D mk. II, but I havenāt really had to deal with that since I started using custom WB coefficients.
LEDs are notorious for their poor color rendition.
I have never noted it to be warm for most cameras in fact I think the opposite so I think you are right likely not on camera reference orā¦ there is a sticky setting in the spot colorā¦ @dtrtuser Make sure you are at L=50 and C and H =0 in the spot color sectionā¦
I think it has something to do with the way the color picker works. When I set the color calibration to default or deactivate it the white balance is ok. Then I activate the color picker and get strange colors or white balance errors. This time it is a blue cast, sometimes it is green.
What settings are on your sliders in the spot colorā¦if they ever got manually changed they are not corrected with a module resetā¦they are stickyā¦just to be sure check that they are 50 0 and 0
If I remember correctly, some cameras (Sony and Olympus, I think) do not play well with color calibration, because their D65 values in the camera profile/matrix are wrong.
Could you perhaps share the shot of the ColorChecker, as well as your XMP?
Yes, WB is set to Camera Reference.
Did you check the spot color settingsā¦ also what camera??
Bingo! Spot mode values were out of whack. All good now with 50/0/0. I donāt know why it was messed up as I never touched these parameters.
Thank you all!!!
Itās a weird implementation that this setting is sticky. Most others are cleared by a module reset. And as you also use the same picker for this if you ever accidentally have the setting on measure then that value is stored and every time you use the picker as you normally would it correctsā¦So the overlap of function in the module and with the picker and sticky setting can be a real gotchaā¦ glad it got sortedā¦I suspect he same for the other example in this threadā¦ happy editing
Yes, my issue is solved. The values in the āspot color mappingā arenāt being reset, even after a restart of darktable.
Since I donāt use the calibration module for white balancing it is not a big issue for me.
This sticky-ness of the values is a featured designed by Mr. AP. I allows you to use the same white balance values across several images. You open image-1 and take a āmeasurementā, Then close image-1, hence the need for sticky-ness, and then open image-2 and apply the ācorrectionā values from image-1 to image-2. This gives you a consistent white balance to multiple images. It makes more sense after you play around with it.
Makes sense. Yet shouldnāt it be reset to 50/0/0 when resetting the module?
The issue has bitten enough people that i think it might be useful to have a possibility to warn people when they choose to reset the module so you can reset the spot values as well or at least warn them that custom values are set and not resetā¦ if we warn about double wb but not this then why bother there either ā¦
I still think the solution to this is to have a separate colour picker for the spot mapping section, with the current picker always set to grey. Alternatively, reset it to grey when the spot mapping section is collapsed?
