Daylight white balance values

[Beep6581]

Originally reported on Google Code with ID 1315

The daylight white balance value should be tailored to each ICC/DCP profile. Until such
time, I would like to assemble a list of these temperature/tint values and add them
to the manual. Please help complete this list (Oduis wink wink):

Documented in the white balance section of the manual:
https://docs.google.com/document/d/1DHLb_6xNQsEInxiuU8pz1-sWNinnj09bpBUA4_Vl8w8/edit#heading=h.tbejc8i25xz1

MAKE     MODEL     TEMP  TINT
-------  --------  ----  -----
Canon    EOS 400D  4862  1.03 
Canon    EOS 7D    5770  0.971
Canon    EOS D60   4723  1.237
Nikon    D300      5277  1.07
Nikon    D50       5321  1.18
Olympus  E-1       5118  1.154
Pentax   K10D      5420  1.094

Reported by entertheyoni on 2012-04-08 13:40:14

[Beep6581]

Please review this:
https://docs.google.com/document/d/1DHLb_6xNQsEInxiuU8pz1-sWNinnj09bpBUA4_Vl8w8/edit#heading=h.yib89jckz127

Reported by entertheyoni on 2012-04-08 14:40:03

[Beep6581]

"Daylight" is somewhat a broad definition. We would need to be specific in describing
 a particular kind of daylight when providing exact values for temperature & tint.

Reported by michaelezra000 on 2012-04-08 15:21:41

[Beep6581]

How about "Daylight at noon when the sun is at least 45° above the horizon"?

Is this paragraph correct?
"The daylight white balance temperature values used by your camera and commonly referred
to in literature and on the internet are averages. The precise temperature and tint
combination you should use for daylight photos is specific to the ICC or DCP input
profile auto-matched with your camera by RawTherapee."

Reported by entertheyoni on 2012-04-08 15:39:53

[Beep6581]

It seems to me that this is a pointless exercise.  Preset white balances are just ballpark
approximations; they will never achieve true white balance except by accident.  So
different cameras have different ballpark approximations; do we really want to spend
the effort to keep updating (and cluttering) the documentation/code with this?  I suspect
we have better ways to spend our time (Olli wink wink).

Reported by ejm.60657 on 2012-04-08 15:59:20

[Beep6581]

How is documenting them pointless but implementing them was not?

On the left is using the daylight white balance value from the list above, on the right
is using the "Daylight (Sunny)" preset.

http://i.imgur.com/1g7Rw.jpg

Reported by entertheyoni on 2012-04-08 16:54:43

[Beep6581]

My point illustrated -- the right hand image has a strong magenta cast.  The left hand
one looks a bit warm/green.

Perhaps I'm not up to date on all the changes going on with profiles -- do the new
input profiles change the values for various WB presets in addition to providing the
input profile, according to the individual camera?  If not, where in RT is it coded
that the WB presets change according to the camera model?  Or is this a 'feature' request?

Reported by ejm.60657 on 2012-04-08 17:31:37

[Beep6581]

That would be a feature request. As illustrated, the approximated daylight setting in
RT is visually far from what it should be for my camera. I remember the scene the way
it is on the left "5420 1.094" version, not the right "Daylight (sunny) 5300 1.000"
version.

Reported by entertheyoni on 2012-04-08 18:34:44

[Beep6581]

Isn't this what partial profiles are for?  It would seem to me more efficient, rather
than accumulating a long list of things for RT devs to maintain, to empower users to
create their own presets and store them.  We have that capability for whole profiles.
 One thing that we were thinking about a while ago was allowing a dialog where users
specify a partial profile, which when loaded alters only specified tool settings; I
don't think it ever got implemented, but its use case scenario is exactly the sort
of thing you are asking for here.  ACR has this capability, and it is sorely needed
in RT.

Reported by ejm.60657 on 2012-04-08 19:49:06