Datacolor User to User Support Group.

-- 
Nathan Gutman

With CRT displays, there were controls for both contrast and  
brightness, and the most effective way to avoid clipping at either end  
while doing a visual, not measured calibration, was to adjust until  
the four squares were visible.

For LCDs this is seldom an issue. First, on less expensive displays  
there may be clipping at all settings. And with the types of controls  
on many LCDs, clipping may not occur at any setting. Besides, most  
LCDs have no control to adjust the blacks, and whites on them are so  
bright that luminance is not set to just below clipping, it's ideally  
set way down from full brightness, through a targeted white luminance  
value. Targeted white and black luminance values are measured with the  
Spyder, not set visually.

To put of much more simply: if you don't like making visual  
adjustments, select measured, not visual mode. Then your setting will  
not come from the four visual squares, but from Spyder measurements  
you take later in the calibration process.

C. D. Tobie
Global Product Technology Mngr.
Digital Imaging & Home Theater
Datacolor.com
CDTobie@...

On Feb 13, 2009, at 8:24 PM, Nathan Gutman <nzgutman@...>  
wrote:

> I am still learning... learning...
> Spyder hardware is supposed to eliminate the visual judgment needed  
> when using calibration software such as Adobe Gamma or QuickGamma.
> But when using Spyder I am asked to visually inspect four white  
> squares and four black squares and adjust monitor brightness and  
> contrast accordingly.
> Isn't this predicated on the visual acuity of the observer?
> Can someone please explain?
> Thanks,
> -- 
> Nathan Gutman
>
>
>

Projectors are totally different animals.  Black luminance for  
projection is not set by the projector, but by the ambient light.  
White is set by the projector, in a properly darkened room, so  
effectively that a pink or green wall will appear white when projected  
upon.

You can use Spyder3TV to set the hardware controls on your projector,  
but the number of such controls is limited when hooked to a computer,  
and even more limited when in digital mode.

The approach Spyder3Elite takes is to leave the hardware setting alone  
(ideally at defaults), let the room and the eye define those factors,  
and simply profile the result, with or without VLUT gray balancing.  
With seems best for LCD projectors, without for Texas Instruments  
projectors.

C. D. Tobie
Global Product Technology Mngr.
Digital Imaging & Home Theater
Datacolor.com
CDTobie@...

On Feb 14, 2009, at 9:30 AM, Nathan Gutman <nzgutman@...>  
wrote:

> Thanks, can you also amplify how does this apply to calibrating a  
> projector?
> Nathan
>
> Cdtobie wrote:
>>
>> With CRT displays, there were controls for both contrast and  
>> brightness, and the most effective way to avoid clipping at either  
>> end while doing a visual, not measured calibration, was to adjust  
>> until the four squares were visible.
>>
>> For LCDs this is seldom an issue. First, on less expensive displays  
>> there may be clipping at all settings. And with the types of  
>> controls on many LCDs, clipping may not occur at any setting.  
>> Besides, most LCDs have no control to adjust the blacks, and whites  
>> on them are so bright that luminance is not set to just below  
>> clipping, it's ideally set way down from full brightness, through a  
>> targeted white luminance value. Targeted white and black luminance  
>> values are measured with the Spyder, not set visually.
>>
>> To put of much more simply: if you don't like making visual  
>> adjustments, select measured, not visual mode. Then your setting  
>> will not come from the four visual squares, but from Spyder  
>> measurements you take later in the calibration process.
>>
>> C. D. Tobie
>> Global Product Technology Mngr.
>> Digital Imaging & Home Theater
>> Datacolor.com
>> CDTobie@...
>>
>> On Feb 13, 2009, at 8:24 PM, Nathan Gutman <nzgutman@...>  
>> wrote:
>>
>>> I am still learning... learning...
>>> Spyder hardware is supposed to eliminate the visual judgment  
>>> needed when using calibration software such as Adobe Gamma or  
>>> QuickGamma.
>>> But when using Spyder I am asked to visually inspect four white  
>>> squares and four black squares and adjust monitor brightness and  
>>> contrast accordingly.
>>> Isn't this predicated on the visual acuity of the observer?
>>> Can someone please explain?
>>> Thanks,
>>> -- 
>>> Nathan Gutman
>> =
>
> -- 
> Nathan Gutman
>
>
>

I recently recalibrated and profiled the monitors on two different systems
and got some error messages that I do not know the reason for or what they
mean.

 

In case one, with a dual monitor display Vista system using LCD monitor and
a CRT monitor, when I finished creating each of the profiles and it was time
to save them, I got the following error message:

 

Save Profile Using ICM. Delete Failed

Profile Support. cpp299

5(0X5)

 

However, when I check out the display using the Spyder 3 Pro software's
program for comparing pre and post profile displays, it appears as if the
monitors are using a color profile, which I assume is the Spyder3 generated
one.

 

In case two, things get a little more complicated. I am using on a XP system
a Matrox G450 dual heading video card with a single Viewsonic VA1912WB LCD
monitor on a VGA analog connection.  It has a maximum possible resolution
less that that which the monitor says is optimium and wants; so I installed
a software program (Powerstrip) which allows me to set the monitor
resolution to 1440X900, which is the resolution that the monitor expects as
optimum.  The video card accepts this and functions at that resolution when
the Powerstrip application is used.  However, after I calibrated and
profiled the monitor with the Spyder 3 hardware and software and saved that
profile, I get an error message that pops up periodically which says:

 

Display Info RB_Get Screen Index - Did not Find

Monitor 0,0,1376,768

 

 

 

I have no idea what this means, why I am getting it, or how to correct it.
The only thing that I can think of is that Powerstrip is interfering with
Spyder finding the monitor or video card LUT so as to apply the profile.
Could this be the case in this instance and is there a work around apart
from getting a new video card that supports the higher resolution natively?

Nowhere do you note what calibration product you are using. I would  
not be to concerned aboutva one time message about not being able to  
delete things, if the resulting profile is okay. As for running a  
third party utility for display resolution, yes that could be an  
issue. There is no knowing just how that interacts with the video  
driver and VLUT application.

C. D. Tobie
Global Product Technology Mngr.
Digital Imaging & Home Theater
Datacolor.com
CDTobie@...

On Mar 15, 2009, at 4:28 PM, "LAURIE SOLOMON" <laurie@...>  
wrote:

> I recently recalibrated and profiled the monitors on two different  
> systems and got some error messages that I do not know the reason  
> for or what they mean.
>
>
>
> In case one, with a dual monitor display Vista system using LCD  
> monitor and a CRT monitor, when I finished creating each of the  
> profiles and it was time to save them, I got the following error  
> message:
>
>
>
> Save Profile Using ICM. Delete Failed
>
> Profile Support. cpp299
>
> 5(0X5)
>
>
>
> However, when I check out the display using the Spyder 3 Pro softwar 
> e’s program for comparing pre and post profile displays, it appears  
> as if the monitors are using a color profile, which I assume is the  
> Spyder3 generated one.
>
>
>
> In case two, things get a little more complicated. I am using on a  
> XP system a Matrox G450 dual heading video card with a single  
> Viewsonic VA1912WB LCD monitor on a VGA analog connection.  It has a  
> maximum possible resolution less that that which the monitor says is  
> optimium and wants; so I installed a software program (Powerstrip)  
> which allows me to set the monitor resolution to 1440X900, which is  
> the resolution that the monitor expects as optimum.  The video card  
> accepts this and functions at that resolution when the Powerstrip  
> application is used.  However, after I calibrated and profiled the  
> monitor with the Spyder 3 hardware and software and saved that  
> profile, I get an error message that pops up periodically which says:
>
>
>
> Display Info RB_Get Screen Index – Did not Find
>
> Monitor 0,0,1376,768
>
>
>
>
>
>
>
> I have no idea what this means, why I am getting it, or how to  
> correct it.  The only thing that I can think of is that Powerstrip  
> is interfering with Spyder finding the monitor or video card LUT so  
> as to apply the profile.   Could this be the case in this instance  
> and is there a work around apart from getting a new video card that  
> supports the higher resolution natively?
>
>
>
>

Thanks!  I am using the Spyder3 Elite.  I am sorry that I did not get
this and reposted my message.  Apparently my messages from the list and
Yahoo in general are being b ounced - even the re-activation notices.  I
have only saw this message and the fact that  messages have been
bouncing because I went to the Yahoo Web site  for the group to check
and see what is happening.


--- In colorvision_group@yahoogroups.com, Cdtobie <CDTobie@...> wrote:
>
> Nowhere do you note what calibration product you are using. I would
> not be to concerned aboutva one time message about not being able to
> delete things, if the resulting profile is okay. As for running a
> third party utility for display resolution, yes that could be an
> issue. There is no knowing just how that interacts with the video
> driver and VLUT application.
>
> C. D. Tobie
> Global Product Technology Mngr.
> Digital Imaging & Home Theater
> Datacolor.com
> CDTobie@...
>
> On Mar 15, 2009, at 4:28 PM, "LAURIE SOLOMON" laurie@...
> wrote:
>
> > I recently recalibrated and profiled the monitors on two different
> > systems and got some error messages that I do not know the reason
> > for or what they mean.
> >
> >
> >
> > In case one, with a dual monitor display Vista system using LCD
> > monitor and a CRT monitor, when I finished creating each of the
> > profiles and it was time to save them, I got the following error
> > message:
> >
> >
> >
> > Save Profile Using ICM. Delete Failed
> >
> > Profile Support. cpp299
> >
> > 5(0X5)
> >
> >
> >
> > However, when I check out the display using the Spyder 3 Pro softwar
> > e’s program for comparing pre and post profile displays, it
appears
> > as if the monitors are using a color profile, which I assume is the
> > Spyder3 generated one.
> >
> >
> >
> > In case two, things get a little more complicated. I am using on a
> > XP system a Matrox G450 dual heading video card with a single
> > Viewsonic VA1912WB LCD monitor on a VGA analog connection. It has a
> > maximum possible resolution less that that which the monitor says is
> > optimium and wants; so I installed a software program (Powerstrip)
> > which allows me to set the monitor resolution to 1440X900, which is
> > the resolution that the monitor expects as optimum. The video card
> > accepts this and functions at that resolution when the Powerstrip
> > application is used. However, after I calibrated and profiled the
> > monitor with the Spyder 3 hardware and software and saved that
> > profile, I get an error message that pops up periodically which
says:

> >
> >
> >
> > Display Info RB_Get Screen Index â€" Did not Find
> >
> > Monitor 0,0,1376,768
> >
> >
> >
> >
> >
> >
> >
> > I have no idea what this means, why I am getting it, or how to
> > correct it. The only thing that I can think of is that Powerstrip
> > is interfering with Spyder finding the monitor or video card LUT so
> > as to apply the profile. Could this be the case in this instance
> > and is there a work around apart from getting a new video card that
> > supports the higher resolution natively?
> >
> >
> >
> >
>