How is it possible? How can the White Balance be so different?
When I set in my camera Canon 5DS the WB to 5500 K. Then I see in PL 5292 K en tint - 9.
In Capture One it is 5374 K and tint 7,4.
When I set Daylight in PL I see 5200 K and tint 0. In CO it is 5102 K and tint 6,8.
When I set in my camera Canon 5DIII the WB to 5500 K. Then I see in PL 5126 K en tint -14.
In Capture One it is 4995 K and tint - 4,4.
When I set Daylight in PL I see 5200 K and tint 0. In CO it is 4768 K and tint - 4,7.
Colour temperature values differs from software to software.
Can we do anything about it? Should we do anything about it? Should we even care?
From a technical point of view, answers would be 3 x yes, from a point of view of usability, art and getting the result we want, the answer is 3 x no (imo). While it can be interesting to know how manufacturers get the values they get, itâs of minor concern for daily use. Iâve stopped worrying about such things, it saves me a lot of headaches.
@Joanna posted a while ago an image of a gray card with a preset wb. When that image was opened in Pl the histogram did show 3 peaks next to each other and a different wb as was set. Changing that wb to the value of the preset did show a histogram where these 3 peaks did overlap, as it should.
Thank you, Platypus for your answer. You are right, headache, but I asked myself why is the White Balance âDaylightâ of Capture One, so it looks, camera related and of PL not. That is not rational.
You mention 5200 Kelvin as DxOâs Standard, but as if to me Iâve seen 5400 Kelvin as their starting point
â or is that something else?
(Only asking as normally I donât care / have set my cam to Auto WB â except for sunset and such.)
@Pieloe
I am not sure I understand well what is said there.
So my question is :
Does DxO camera tests done when creating camera profiles take care of those kind of specificities (different white balance interpretation between brands and models) and tries to faithfully follow specific camera color interpretation nor not ?
An other way to ask this would be :
Is DxO trying to provide camera profiles that respects as much as possible camera native colors when cracking - doing reverse engeenering on - Raw code (those colors the constructor choosed for itâs camera - for instance what is called nikon specific colors by some nikon users).
Or do they apply some rules that fits they software and their way to see how colors have to behave without trying to respect the âcharacterâ of the cameras ?
You did shoot a grey card with a preset color temperature based on you color temperature meter. And was upset that pl didnât take the values of your preset.
I checked a picture of a grey card that I have. It seems that it is camera dependent, some profiles are not properly calibrated.
For example, I took a picture of a grey card with a Nikon D750, white balanced with the internal colormeter. When I load the picture into Photolab using the as shot white balance, the histogram looks fine, all color peaks align. Also manual white balance using the color picker delivers similar results (it would be nice if it was possible to choose a radius greater than 50 pixels to average a greater area):
This is with the Photolab profile for the D750. When I use my own calibrated DCP profile, the results are similar.
However, when I pick a different profile of other cameras, there are shifts in the histogram peaks, which in my opinion should not happen. It only happened to a few profiles though, most prominent with the profile for the âCanon 1DMK3, 1DsMK3â: