I keep getting a “white balance module error” pop up in red when I adjust the settings in the color calibration module. Darktable 4.0.0 under Linux Mint, no opencl
Have you set this to modern?
WB-module should then automatically be set to D65
And this should not be changed, if you use CC for WB settings
Yes, I am set to modern.
Where is the D65 setting in WB? My module looks the same as yours.
I am now wondering if the error was occurring on images previously developed in an earlier version of Darktable, and hence the WB may have been altered from the default. I will pay more attention to this when I see the error again.
It’s the button I marked with red on my screenshot.
Then please show a screenshot of the error.
However please note my subsequent post above. I believe this is happening on older photos, and the white balance in them is set to something like “as shot”, instead of the new default you called “D65” (the popup help on which says is “set to the camera reference point, in most cases it should be D65” hence my confusion). This must be due to the images being previously edited in older versions of Darkroom.
There was an issue that causes that warning. I think it was a change in the adobe coefficients values or some rounding error.
What I did to fix it was change one image to camera reference, then use the copy and selective paste only the white balance module to all images.
Existing edits using the standard (legacy) WB should not be affected by auto-apply chromatic adaptation default being set to modern. If you still get this, there might be a bug – or you may have an auto-applied preset that turns on color calibration.
No I haven’t used color calibration before, so should be no presets being auto-applied. Funny thing happens when you try to fix this - when you go to WB and select the camera reference option, it gives a different error that WB has been applied twice. Then that seemed to go away. Strange. I think there may be something funny going on, but it looks like I just have to manually remember to go and change the WB setting on any old images that give the intial error that I got.
Can you post an XMP that only has old edits? (The image is not even needed.) Then we can see what happens if we apply it to an image, then open it with a current darktable version configured with auto-apply chromatic adaptation default = modern.
I opened this one and it gave the error
P1020999.RW2.xmp (8.2 KB)
and, after I sent this xmp, I tried changing the WB to camera referred, and this time, no problems, the error goes away without that bit about WB applied twice.
I do have my 4.0.0 version set this way now. I didn’t when I first created the image.
Yes, I understand that. If you can share a file, maybe we (the others) can also check, with different settings, on different machines. ‘Two heads are better than one.’ (in Hungarian: “Több szem többet lát” = ‘More eyes see more’)
Edit: sorry, I didn’t realise you already posted a file, and I thought you were responding to that, not to ‘current version of darktable’. What I meant with ‘a current darktable version’ is that if there’s a bug in 4.0.0, it may have been fixed in the development version, which quite a few of us run, so we could even test with that.
Please a file with only the old edits. This one already has cc enabled.
darktable:operation="channelmixerrgb"
darktable:enabled="1"
Try to find one that you have never opened with current DT version, also don’t open it before uploading here to prevent any changes to the xmp.
I confirm that this could happen on old edits since Adobe coefficients changes. Change that was really needed. This error appears on only some cameras, so many doesn’t have that. That doesn’t change image rendering, difference is really tiny. It’s only that default setting compatible with color calibration module is no more there and so appear this error. The only way to fix that is to select bulb icon in white balance to make that error disappear (then you could copy/paster only white balance module (with selective copy/paste options) on other affected images. But you could also ignore that error as there’s no visible difference on image.
More infos on that issue, how to correctly fix it and why we can’t do anything else:
2 Likes
Or (if you have selected “modern” chromatic adaptation defaults in the preferences) you can just click the “reset” button in the white balance module (which is what I do on the occasion that I see this warning). I only see it on some images because I quite often discard my history stack before I start working an image.
1 Like
Better and quicker way, never thought of that one!
Thanks. I can deal with it armed with this knowledge. Hopefully this area of Darktable will become more streamlined in later versions. I don’t want to sound negative, as I love and appreciate all the new developments in Darktable.
Great tips.
I personally have set my auto-apply chromatic adaptation defaults to legacy. If you did the same you may prefer the behaviour of DT with your past pictures. Then if you want to use the color calibration module for a new image you still have the option to set WB to camera reference and activate the color calibration module. More often than not I am happy with the WB created by the camera and therefore do not need to intervene using the color calibration module.