Datacolor User to User Support Group.

Hi, David,

I am currently using Spyder3Pro. It does not allow me to formulate my own target definitions.

I have target definitions I have formulated with OptiCAL. Should these be usable under Spyder3Pro?

In particular I am intersted in an sRGB target.

I note, when using OptiCAL, that the provided "sRGB" target definition said that its white point was 6500K (by which I assume was meant the blackbody chromaticity with that color temperature). The prescribed white point for sRGB is D65, which is a little different from that.

I loaded the "sRGB" target provided with the package, then selected D65 as the white point, and saved the result. Now I have used that target with Spyder3Pro.

Can I expect it to have done the right thing with that target definition?

Thanks.

Best regards,

Doug

Il giorno May 27, 2009, alle ore 7:46 AM, Doug Kerr ha scritto:

> I am currently using Spyder3Pro. It does not allow me to formulate  
> my own target definitions.

Right, it has a limited number of predefined target values, the most  
common ones.
>
> I have target definitions I have formulated with OptiCAL. Should  
> these be usable under Spyder3Pro?

No, not really...
>
> In particular I am intersted in an sRGB target.

But sRGB is the most common standard of all: Gamma 2.2, Whitepoint  
6500; Spyder3Pro not only will do that one, it defaults to it. There  
is no way to build a true "sRGB" target, and targets do not define a  
display's primary saturations. But the profile defines them, and a  
color managed application uses those definitions to show color  
saturation correctly.
>
> I note, when using OptiCAL, that the provided "sRGB" target  
> definition said that its white point was 6500K (by which I assume  
> was meant the blackbody chromaticity with that color temperature).  
> The prescribed white point for sRGB is D65, which is a little  
> different from that.

We have actually changed our whitepoint definition in terms of the  
x,y, values since OptiCAL, so they are probably already what you want.  
But let me stress that anyone who cares about the miniscule difference  
between varying definitions of 6500 should be using Spyder3Elite, not  
Pro...
>
> I loaded the "sRGB" target provided with the package, then selected  
> D65 as the white point, and saved the result. Now I have used that  
> target with Spyder3Pro.

Possible but not really appropriate...
>
> Can I expect it to have done the right thing with that target  
> definition?

Maybe, but, you are mixing and matching things not intended to be put  
together... you really need to do the Pro>Elite upgrade.

C. David Tobie
Global Product Technology Manager
Digital Imaging & Home Theater
CDTobie@...

Hi, David,

--- In colorvision_group@yahoogroups.com, C D Tobie <CDTobie@...> wrote:

> But sRGB is the most common standard of all: Gamma 2.2 . . .

Well, not really, quite.

> . . . Whitepoint 6500 . . .

Well, not really, quite.

> . . .Spyder3Pro not only will do that one, it defaults to it. There 
> is no way to build a true "sRGB" target, and targets do not define > a display's primary saturations. But the profile defines them, and > a color managed application uses those definitions to show color  
> saturation correctly.

I understand.

> We have actually changed our whitepoint definition in terms of the  
> x,y, values since OptiCAL, so they are probably already what you want.

Good.
  
> But let me stress that anyone who cares about the miniscule difference  
> between varying definitions of 6500 should be using Spyder3Elite, not Pro...
Yes, and I am not really concerned over those small differences. It was just really an "intellectual" matter for me.

> ... you really need to do the Pro>Elite upgrade.

Indeed, as soon as the stock market goes up a little! Right now, my curiosity isn't worth the $99.00!

Thanks for your insights.

Best regards,

Doug