Datacolor User to User Support Group.

>>I've been using Spyder3 Elite to profile my HP 2065 LCD monitor. I last profiled this monitor in March 2010. Since then, profile checks have indicated that there is no need to re-profile. The agreement between monitor appearance and print appearance has not changed as far as I could tell.

If the checks didnt warn you about not being able to reach your target white luminance (brightness), then the only way the display could have dimmed in the mean time would be if you calibrated without a target white luminance in the first place. In older versions of Elite the default settings would not have included a brightness, newer versions do.  


>> Even so, perhaps foolishly, today I decided to re-profile the montor anyway.

Not foolish, it will force you to run the full process about every six months anyways, so you were about due. 

>>Ambeint lighting was Moderate, as it is every time I print or edit photos.

Acceptable, if a bit higher than ideal...

>>Using the monitor controls, I re-set the brightness and contrast of the monitor and then proceded to attempt to re-profile. I was surprised to see that the previously available screens for adjustment of brightness and contrast are not visible. I don't know how to access them again.

You would need to set them in Calibration Settings, of if you want something really exotic, in Advanced Settings. This may not come up if you already have a configuration chosen.  

>>To check the brightness another way, I used  Tools/Colorimeter to check the candelas of the screen. They were at 68 - very low. I readjusted the monitor controls to the settings they'd had just before I attempted the re-calibration. Candelas were now 88. I readjusted brightness to the maximum possible, and caldelas were then 100.

That display is marketed as offering 300c/m2, so if setting it to max brightness only gets you 100, that's not a good sign.  Still could calibrate at that brightness, but it would be too dim for use at Moderate lighting...

>>When I made that monitor calibration back in March, candelas were at 120, so something has gone very wrong. The monitor appearance itself does not seem to have changed in the past several months.

Well, if it can't hit 120 now, and CheckCAL was happy, you MSG have been configured for native luminance, not a targeted luminance, or you would have flunked.

>>Is this a matter for a support ticket, or can someone in the group steer me back on the right course?

See if any of this helps you. But the bottom line is that this display should be much brighter than that... Check your configurations!

C. David Tobie
Global Product Technology Manager
Digital Imaging and Home Theater
Datacolor inc. 
cdtobie@datacolor.com
www.datacolor.com

On Sep 13, 2010, at 12:27 PM, "bill_hansen20012001" <b2hansen@...> wrote:

> I've been using Spyder3 Elite to profile my HP 2065 LCD monitor. I last profiled this monitor in March 2010. Since then, profile checks have indicated that there is no need to re-profile. The agreement between monitor appearance and print appearance has not changed as far as I could tell. Even so, perhaps foolishly, today I decided to re-profile the montor anyway.
> 
> Ambeint lighting was Moderate, as it is every time I print or edit photos.
> 
> Using the monitor controls, I re-set the brightness and contrast of the monitor and then proceded to attempt to re-profile. I was surprised to see that the previously available screens for adjustment of brightness and contrast are not visible. I don't know how to access them again.
> 
> To check the brightness another way, I used  Tools/Colorimeter to check the candelas of the screen. They were at 68 - very low. I readjusted the monitor controls to the settings they'd had just before I attempted the re-calibration. Candelas were now 88. I readjusted brightness to the maximum possible, and caldelas were then 100.
> 
> When I made that monitor calibration back in March, candelas were at 120, so something has gone very wrong. The monitor appearance itself does not seem to have changed in the past several months.
> 
> Is this a matter for a support ticket, or can someone in the group steer me back on the right course?