Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Thread

Color matching monitors -- target "white point"

Color matching monitors -- target "white point"

2007-05-18 by bbass408

I've read some posts where people have trouble color matching two 
monitors and they mention getting a "white point" setting from the 
calibration of one monitor and using that as a "starting point" for 
calibration of the second monitor. 
Could someone please explain this further.

Re: [colorvision_group] Color matching monitors -- target "white point"

2007-05-18 by CDTobie@aol.com


In a message dated 5/17/07 11:29:57 PM, bbass408@... writes:


I've read some posts where people have trouble color matching two
monitors and they mention getting a "white point" setting from the
calibration of one monitor and using that as a "starting point" for
calibration of the second monitor.
Could someone please explain this further.


There are two technical terms that get confused. Whitepoint and White Luminance. You need to match both. Whitepoint is the color of white. If you can match this with RGB gains controls, thats ideal, as its a hardware match,with no software cost. If not, we match your monitor's whitepoint to the target whitepoint for you, via the videocard corrections. That will get you two monitors that show the same color of white on screen. That value will be something like 6500k, or perhaps you'd use a custom value you feel better matching your paper white in your proofing light, such as 5800k.

Next is white luminance. This means the brightness of white (and of everything else, which all tags along) on the monitor. Again, you need to match this on two monitors for them to match. This means finding a white luminance both can hit (and thats appropriate for your ambient and proofing lighting) and targeting that for both monitors. So you need Spyder2PRO, which allows white and black luminance targets. Go to the Info window from the menu bar in Spyder2PRO, and check the native white luminance of both monitors. Use a value at least a bit lower than either native white, for headroom on the dimmer monitor (you don't want to set a target you can't hit again next month, when the monitor dims a bit), unless you are using a value thats notably lower than both, to match your ambient or proofing light brightness.

C. David Tobie
Product Technology Manager
ColorVision Business Unit
Datacolor Inc.
CDTobie@...
www.colorvision.com



**************************************
See what's free at http://www.aol.com.

Re: Color matching monitors -- target "white point"

2007-05-19 by bbass408

That was very informative.  Thank you.  

Is the process the same for Black luminance and does it matter as much 
as white luminance?  If one monitor can't hit the black luminance 
target, do you just plug in the target value that it can hit?

Re: [colorvision_group] Re: Color matching monitors -- target "white point"

2007-05-19 by CDTobie@aol.com


In a message dated 5/18/07 10:57:15 PM, bbass408@... writes:



Is the process the same for Black luminance and does it matter as much
as white luminance?


Inverse, but similar, you would choose the higher black luminance, and target that for both monitors; that is, if your monitors have a control that can adjust black luminance, most LCDs do not.

If one monitor can't hit the black luminance
target, do you just plug in the target value that it can hit?

If one monitor isn't bright enough, you lower your white luminance target until both can hit it, if one monitor isn't dark enough, you raise your black lumiance target until both can hit it. Again, that is if you have monitors with black luminance controls, such as CRTs or a few advanced LCDs. With most LCDs you are stuck with "native black luminance"... which tends to be fairly similar between monitors, once the white luminance is matched.

C. David Tobie
Product Technology Manager
ColorVision Business Division
DataColor Inc.
CDTobie@...
www.colorvision.com



**************************************
See what's free at http://www.aol.com.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.