Re: Ooops - D65 != D65 ???
Re: Ooops - D65 != D65 ???
- Subject: Re: Ooops - D65 != D65 ???
- From: email@hidden
- Date: Wed, 20 Jun 2007 09:27:48 EDT
In a message dated 6/20/07 12:18:44 AM, email@hidden writes:
> But two questions, David. You wrote:
>
> > Spyder2PRO's info window will tell you your monitor's native [...]
> > whitepoints
>
> Where does the software get that info from?
>
>From measuring the native and calibrated whitepoints...
>
> I ask because when I first opened the Info window, it told me that
> the "uncalibrated" (= native) whitepoint of my display is 0.314 -
> 0.342. At that time, I had not yet used Spyder2Pro to create a
> profile with a "native whitepoint" setting (I did use it to create
> profiles with a D65 setting).
>
Not choosing Native as a taget value does not keep the software from reading
the native value... it just means that there will be a different value
targetted.
> After I created a profile with a
> "native whitepoint" setting, the Info panel reported the
> "uncalibrated" (= native) whitepoint of my display is 0.311 - 0.338.
>
Typically you make hardware adjustments in the process of calibrating a
monitor, those effect the native whitepoint; native means what the hardware is
putting out, change the monitor controls, and what the hardware is putting out
changes.
>
> So at first I thought the Spyder software gets this info from the
> hardware (Apple's System Profiler, whatever) as it "knew" it
> immediately, but in this case a measurement couldn't change that. So
> can you tell me where Spyder gets this info from?
>
>From reading white on screen, in an uncalibrated state, meaning without LUT
adjustments.
>
> > including xy and Kelvin
>
> When I enter 6500 Kelvin in the "user-defined whitepoint" [translated
> from the German GUI] dialog panel, the panel displays an xy of
> 0.314 / 0.324. Robin Myers said at the beginning of this thread that
> D65 is defined as 0.3127 / 0.329, which is also what Eye-One Match
> reports for 6500 Kelvin in its corresponding dialog panel. Now where
> does that inconsistency come from?
>
> You are targetting 6500Kelvin; no reason that should be an exact match to D65
(as was covered earlier in this thread). Older versions of our software used
to offer both D65 and 6500K. This was though to be confusing to many users
(lots of tech support calls asking which to use and why). Since one can't really
calibrate to D65 (only to little x, little y values from it; a monitor does
not emit a D50 or D65 spectrum)) the choice was to eliminate the D target
values, and leave the K target values. I hope to adjust this further in the next
version by offering the D values (by whatever title), since they are the only
consistant set, and would be more what users would expect for the type of
crosstesting you are doing. Typing in xy target values will get the desired result,
however.
C. David Tobie
Product Technology Manager
ColorVision Business Unit
Datacolor Inc.
email@hidden
www.colorvision.com
**************************************
See what's free at http://www.aol.com.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden