Datacolor User to User Support Group.

Sorry about leaving all of the quoted lines below but did not see a 
way to delete most without loosing the thread.

David, all I can say is that it appears the correct profiles that I 
built using the Spyder2 are being applied to the monitors and at the 
end of the boot sequence that is what I end up with.  I use the CRT 
as my soft proof monitor in Photoshop CS2 and it gives me the results 
I expect in that I am able to use the softproof to evaluate my images 
for printing using a profile for my paper/ink/printer that I built 
with PrintFix Pro.  This is what I want.  In PS, I have the color 
preferences set so that the RGB is Adobe RGB, not my monitor 
profile.  

My secondary monitor is an LCD with limited controls.  I can set 
brightness (to a limited degree) and the 3 colors, but not the 
contrast. Like most LCDs, it was way to vibrant, bringt and 
contrasty.  To tame the monitor down, I am using the video card 
controls to alter the bringtness and contrast in an effort to get it 
to be as close to the CRT as possible.  Between the adjustments and 
the Spyder2, I can get it to the point that it is close to the CRT 
which is fine as I use it for the tool, pallets, info window, etc.

When I check the properties for my monitors under Windows, they show 
that the profiles I built are the ones that are applied.  I can use 
the applet interactively to apply different profiles and when I apply 
the one I built, there is no change in the monitor so I am assuming 
it is the one that is applied.

If I use the ColorVision Profile Chooser, it open two windows, one 
for each monitor, and I am able to select a different profile for 
each.  When selected, the profile only impacts the monitor selected, 
not both.  The profiles listed are the ones built wityh the Spyder2.

I am always looking for better color management tips so if there is a 
better way, please make suggestions.

Rollin

--- In colorvision_group@yahoogroups.com, CDTobie@... wrote:
>
> 
> In a message dated 1/23/07 10:48:23 AM, rhill3@... writes:
> 
> 
> > David, I decided to try a test to see if I could confirm that each
> > monitor is indeed being loaded with a different profile 
> > 
> But thats the wrong question, and the reason so many people are 
deceived by 
> this issue. The OS does not load a profile, it just makes it 
available to 
> applications. On Windows it does not load videocard corrections 
either, unless a 
> utility makes that call. This utility should be making it, but does 
it flash it 
> uniquely, and successsfully, for each monitor?
> 
> 
> > and that it
> > is the one assigned to it using the WinColor applet.
> > 
> > After booting the machine, I used the applet to assign a profile 
to
> > the secondary monitor which caused the monitor to produce a very 
dark
> > image.  I set it as the default for the monitor. 
> > 
> That would be the video correction for one or the other monitor 
(assumedly 
> the correct one) being applied to that monitor. If this works 
right, it should 
> remain looking just like this thereafter...
> > 
> > I then rebooted the machine.  During the boot sequence, the
> > appearance of the monitors changed as follows:
> > 
> > 1. Shortly after the desktop appeared, both monitors changed to 
what
> > I am assuming is a no profile state.
> > 
> How do you assume that? We have to assign obviously wrong, and 
obviously 
> different, LUT data to both monitors to determine when one, the 
other, or none, is 
> being applied...
> > 
> > 2. Later, the appearance changed to what I know both monitors look
> > like with the profile for the primary monitor applied.
> > 
> No profile is being applied to the monitors, VLUT calibration data 
is being 
> applied.
> 
> >   I would guess
> > this is Win XP or the NVidia driver applying the same profile to 
both
> > monitors which is the expected behavior since I have a single 
video
> > card.
> > 
> Applying the same LUT data (as I would expect) to both monitors... 
wrong data 
> to at least one of them at that point.
> > 
> > 3. At the very end of the boot sequence, the secondary monitor
> > changes appearanceto what matches the dark profile I assinged to 
it
> > using the WinColor applet.
> > 
> So now different LUT data is being used for each. Thats half the 
battle.
> 
> >   The primary monitor does not change. 
> > This, to me says that the applet has loaded a different profile 
and
> > applied it to the one monitor but not to the other.
> > 
> But will applications like Photoshop actually get the different 
(and correct) 
> profiles assigned for both monitors as well. VLUT calibration data 
is still 
> only half the battle...
> 
> >   I have the
> > applet in my startup folder with the "/L" parameter so that it 
runs
> > with no input required.
> > 
> > I do not know what the applet is doing, but it does appear to be
> > applying separate profiles to the monitors.
> > 
> We'll assume its assigning the profiles for the monitors (for 
application 
> use) as well as utilizing the VLUT data from them. But you would 
have to prove 
> this by seeing that each is using a seperate profile in Photoshop 
or some other 
> application to be sure its all working.
> 
> >   In my case, I built the
> > profiles using the Spyder2 and gave each a unique name based on 
the
> > monitor type,  I have assigned these profiles as the default 
profile
> > for each monitor using the WinColor applet in interactive mode.
> > 
> > For the record, my video card is an NVidia Quadro FX 3400.  My
> > primary monitor is an IBM C220P CRT and the secondary is a Dell
> > 1905FP.
> > 
> > Is there something else you would like me to check to help answer 
the
> > question about whether or not the applet is applying the unique 
set
> > of corrections to each monitor?
> > 
> Short of sending you monitor profiles with clearly wrong profile 
> descriptions, and ones with clearly wrong LUT data, so you can 
confirm whats what, there 
> isn't much more you can check the way you're doing it. Sounds 
promising though; 
> let me know, off list, if you are interested in getting such 
profiles from 
> me...