Here are two versions. One is using traditional white balance picked from the card; the other is with the new method (white balance set to camera reference, color calibration’s WB set from the card). I don’t see any difference (but I’m bad at colours); I was able to show that the two were different by doing a ‘difference’ merge in the Gimp and exaggerating the result):
The second pair is ‘as shot’; one using traditional WB, the other with WB=camera reference + color calibration set to ‘as shot in camera’. Since there was a slight shift in brightness, I slightly adjusted the exposure. There’s some shift (even I can see it in the sky), but there would be no point to the new method if it yielded the same result as the old, correct?
Something in what you write sounds suspicious to me: ‘The colour is ok when colour calibration is off. When I switch it on, the picture goes very blue.’
You can’t just switch colour calibration on and off (if you use it for CAT, not just as a channel mixer). In order for it to work correctly, the WB module must be set to ‘camera reference’. Sorry if I’m just stating the obvious, and you only omitted changing the WB setting for sake of brevity.
Thanks Yann for taking the time… much appreciated!
I cannot for the life of me get the same results as you. As in your first method :
First photo : with white balance module set to camera reference and I took white balance off card with the colour balance module. (Aargh !)
Second photo : Only the white balance module active with balance taken from card, looks like yours.
I am sending the screenshots, I am picking the balance with a small rectangle like in the screenshot I sent yesterday. What are you doing that I am not ??
As for the comment on the screen going blue, it was a question as to what the colour balance module was doing, not an attempt to get it right. It doesn’t really matter for now…
I had better luck with the white patch making all the numbers align. Your small grey patch is not evenly illuminated, there is a strong shadow on it and there is substantial color noise. I saw a lot of green on it as well. It could be a case of garbage in garbage out in this instance or even from how you select the area each time but as the area is not uniform then WB won’t make it perfectly line up IMO. The main part of the image is in a strong shadow with some mixed light as well so there will likely be more than one WB in this image. There are sections in the back have strong yellow cast from the sun. I think using targeted application of the color balance module and working on WB in areas in the shadows highlights and midtones will give you a good result… perhaps more so that trying to get WB from this card in this case…
Your first screenshot above shows a CCT of 4199K, a hue of 14.4 degrees and a chroma of 21.7%.
If I use color calibration’s picker on the grey card, I get 4384K (daylight). Switching to ‘custom’ illuminant, that’s 60 degrees at 17.8%.
Note that I’m on the master branch. Also, my setup applies profiled denoise in wavelet mode, for (edit: typo fixed) U0V0 only (at strength 5, Y0 all flat), and I used VNG for demosaic:
Not your setting but your wording Y0 i luminance correct?? Sorry I understand an my replay was maybe not clear. Your explanation refers to applying the denoise to Y0 when you are doing chroma denoise. You look to have modified the @rawfiner preset by bumping up the strength and reducing color denoise in the course wavelet areas at least that is what I see which I would not describe as applying the denoise to Y0…that is what I was trying to say…
Sorry i wan’t clear the first time and I think that is a great preset I just wanted to check in case I was not getting it… @nwinspeare as you can see with the noise not a very clean gray sample
I did notice a green tinge after the wb but as expected working through CB module on a sample from the highlights shadows and midtones removed it nicely…
FUJIFILM-X100V-2021-01-17-10h09min35s_01.raf.xmp (11.5 KB) Without color balance I do have a green tinge…On the buildings above the sign with CB off the blocks are 137,168,146 and with it on 145,149,149
Loading your original XMP, I read 28, 30, 34 (locked values in color picker). Picking with color balance I get 30, 30, 29. I’m wondering why you get might higher values, and so far away from grey.
Kofa, sorry about the exposure readings, I keep on resetting the history stack and adjusting the exposure… but I’m still getting a CCT of around 4400 K at best, with or without noise reduction. (I tried removing chroma noise early one, forgot to mention it. It doesn’t change much. I use the preset wavelets: chroma only. Darktable doesn’t have profiles for the x100v or x-pro3 yet.
We seem to be getting very different readings. I am on a Mac. Does it have anything to do with display profiles ?
I have another raw file, taken in better light with the same white balance issue between the legacy mode and the new color calibration, I’ll try to post it with a couple of screen shots.
white-balance2.raf (56.3 MB)
A new image with a lower ISO and the same problem.
First with the color calibration tool, exposure set at +1.5 and white balance taken from card (in center) The gray card reads (47,49,46)
@nwinspeare What do you have as your histogram profile…those numbers don’t match up with the image…no way your gray is 50-60…something is not right it is way brighter than that…just opening your image with no corrections at all no exposure or tone curves of any sort and the WB as you shot it… I get around 115-120 for your white card
I get the following numbers just pulling in your image…no exposure or anything…no filmic as shown above…
Camera WB as shot 4903 Gray card 114 116 112
Spot WB on whole image 4328 107 114 120
Spot WB on Grey card 4786 115 115 115
Color Calibration
Activated for the whole image 3688 113 121 127
Activated selecting gray card 4051 119 119 120
Others can try and share but your values loading into DT seem very low…
Adding around 1 ev give me the same trend with the gray now reading around 160…
I use export profile as my histogram profile and that determines your histogram and picker values …my export is usually sRGB…I think maybe you are on working profile which may be Rec2020 and this will give you lower values…
Perhaps someone can take a run at a better explanation. I want my histogram to match my exported file so I set it this way… There may be other or more correct uses…but I think this is you discrepancy when you are looking at C1
Ok, set histogram to export profile, soft proof profile to srGB, the other two are on system display profile. I now read (102,101,99) but when I copy the screen to affinity and get a colour picker, I read (134,135,133)
So then I discarded the history, and in darkroom switched off filmic and colour calibration.
With white balance module :
Camera WB as shot : 4903 grey card (102,101,99)
Spot WB on whole image : 4329 (95,99,107)
Spot WB on Grey card : 4596 (98,100,103)
With color calibration module on again , white balance set to camera reference:
Auto (just switched on) : 4047 (105,105,103)
AI detect from surfaces : 5002 (114,103, 87)
Spot WB on whole image selecting gray card 3875 (101,106,103)
Other question : the order of modules in the history stack is very different to yours…
History stack order means nothing. The left most tab in the modules group will give you the order that the modules are applied. This is the default if you set processing to none ie not legacy and not scene referred. I like to add what I want so I don’t commit to any preset. Also you dont need softproofing on thats just where you set the profiles. I may have had it selected in a screen shot after playing around with the settings. I selected a range on the gray card so we may get different values slightly…not sure. You can try the AI modes but AP has said mileage may vary with those. How are you spot WB with a range or single point?? You have sharpen on which might change the values slightly and the Affinity profiles are not a direct match they use some custom profiles so you would need to match up your icc profiles and even then I am not sure going between software like that you will get the same numbers. In the end what is more important is the channel balance that your arrive at not the numbers …if you add or subtract exposure you will bump the numbers up or down…Also unless you go in and turn it off Affinity adds a tone curve when you load a raw. Did you turn it off??
I think it should be shot closer as a larger image instead of a tiny patch in the screen and it should have even lighting no glare or shadows…for the best results anyway.
