Message
Re: [colorvision_group] Re: Vista Color Management
2007-04-19 by CDTobie@aol.com
In a message dated 4/19/07 12:35:30 PM, rw3st@... writes:
Sorry - what I actually meant was what settings should I be setting in
Vista, both before and after calibrating.
I want to calibrate my monitor - so before calibrating do I go into
Vista Color Management and set it to 'Use my settings' and then remove
any existing profiles?
After calibrating my monitor I noticed that Colorvision software starts
up automatically with Vista and loads the profile. This is what I do
not understand - is Vista Color Management also loading the new profile
as well?
What I am specifically trying to avoid is Vista using a profile as well
as Colorvision using a profile (if that is even possible).
This is a cooperative venture. Windows (including Vista) is in charge of the housekeeping chore of assigning profiles to monitors and remembering them. The monitor calibration software automatically, and invisibly, makes this request of Windows, and the profile is assigned, you don't need to do anything about this unless Windows fails to set this successfully... see previous post about details of that. The other half of your monitor color management is video card corrections (called VLUTs) that need to get loaded to the videocard. Windows (Vista included) does not automatically do that, so our startup utility does. So there is no danger of "the profile being loaded twice". There is no danger of the video corrections being loaded twice either. Since they are the same VLUTs, even if you did load them again manually, it would just overwrite correct data with the same data. Its when another application loads the wrong LUTs that you get in trouble. So avoid any software that does that. Use only one monitor calibration tool at a time.
C. David Tobie
Product Technology Manager
ColorVision Business Unit
Datacolor Inc.
CDTobie@...
www.colorvision.com
**************************************
See what's free at http://www.aol.com.
Attachments
- No local attachments were found for this message.