Monitor profiles disappearing from Windows XP display settings

This seems to have settled down now, after doing everything I can to disable the the second "monitor" (the TV-out)
I’ve opened and closed Photoshop many times, and have entered the display colour management
settings many times as well, and the problem just hasn’t occurred again.

I’ve been taught how to check the monitor profile which Photoshop is actually using, too, so if/when
I do enable the TV out again, at least I’ll be able to check. (just look in the RGB settings in the
color preferences)

Greg.

"Greg" wrote in message

Hi,
On Windows XP, I’m finding that quite often when I go into the Color Management settings for my display,
my display profiles have disappeared off the list. Typically, I then

simply

exit out of the settings, and re-enter,
and voila – they’re back! I’m pretty sure now that when they are not

there,

that Photoshop then reverts to
the system default, which is sRGB. Very annoying, and risky!
If it makes any difference, my video card is a GeForce4 MX 440-SE, and in addition to the standard VGA output, it has a TV output. The

problem

still exists, even after I yank
the cable which runs to my TV, which prevents the card from detecting the second "monitor".

Anyone have any idea what’s going on?

I’m using Photoshop CS at the moment, but have had the same problem with

V7.

Greg.

Greg wrote:

I’ve been taught how to check the monitor profile which Photoshop is actually using, too, so if/when I do enable the TV out again, at least I’ll be able to check. (just look in the RGB settings in the color preferences)

The information inside Photoshop seems to depend on Adobe Gamma in the control panel. If I load say Adobe RGB(1998) in Adobe Gamma and changes the description to ‘Test’ and saves the profile under the name ‘Test’ when I close Adobe Gamma, the Monitor RGB-setting inside Photoshop’s color settings changes to ‘Monitor RGB – Test’ even if OptiCAL startup loads my custom made monitor profile (VP201s) into the LUT of the graphic card at startup.
That means that the information inside Photoshop is wrong. It’s not using the ‘Test’ profile. It’s using the profile loaded by the gamma loader (OptiCAL startup in my case).

—
Regards
Madsen.

Thomas,
Why are you even using Adobe Gamma at all, when you are using OptiCAL? The two are simply not compatible at all.

When you run the OptiCAL startup, how does it know which monitor profile to obtain the LUT from? You do know that Photoshop simply has no knowledge of which LUT has been loaded into the graphics card, right? If you have forced
a load of a LUT from a different profile to the one which Photoshop is actually
using, Photoshop isn’t going to detect this. The LUT isn’t strictly speaking part of the profile at all – it’s *calibration* data. The LUT, in combination with
the monitor’s brightness, contrast, and colour temperature controls, calibrate
the monitor, and the monitor profile *defines* the characteristics of the monitor
in that calibration state, and *only* that calibration state. Photoshop has to
assume that the monitor has been calibrated to the correct state, such that the monitor profile it is using represents reality. It doesn’t do any checks. (to the
best of my knowledge)

Greg.

"Thomas Madsen" wrote in message

Greg wrote:

I’ve been taught how to check the monitor profile which Photoshop is actually using, too, so if/when I do enable the TV out again, at least I’ll be able to check. (just look in the RGB settings in the color preferences)

The information inside Photoshop seems to depend on Adobe Gamma in the control panel. If I load say Adobe RGB(1998) in Adobe Gamma and changes the description to ‘Test’ and saves the profile under the name ‘Test’ when I close Adobe Gamma, the Monitor RGB-setting inside Photoshop’s color settings changes to ‘Monitor RGB – Test’ even if OptiCAL startup loads my custom made monitor profile (VP201s) into the LUT of the graphic card at startup.
That means that the information inside Photoshop is wrong. It’s not using the ‘Test’ profile. It’s using the profile loaded by the gamma loader (OptiCAL startup in my case).

—
Regards
Madsen.

Greg wrote:

Why are you even using Adobe Gamma at all, when you are using OptiCAL? The two are simply not compatible at all.

I know and I’m not using Adobe Gamma. I’m using OptiCAL startup and Adobe Gamma Loader is removed from the startup folder.

When you run the OptiCAL startup, how does it know which monitor profile to obtain the LUT from?

When I make the profile with OptiCAL I can choose if the profile should be the default monitor profile and if I do that the result is that OptiCAL startup uses that profile at startup. I don’t know where that information is saved. Maybe in the registry.

You do know that Photoshop simply has no knowledge of which LUT has been loaded into the graphics card, right?

Yes I do. The profile you see inside Photoshops color setting (Monitor RGB – name-of-the-profile) is picked from Adobe Gamma, as far as I can see, and therefore doesn’t necessarily reflect the current monitor profile in use. That’s what I’m trying to say. 🙂

—
Regards
Madsen.

"Thomas Madsen" wrote in message

Yes I do. The profile you see inside Photoshops color setting (Monitor RGB – name-of-the-profile) is picked from Adobe Gamma, as far as I can see, and therefore doesn’t necessarily reflect the current monitor profile in use. That’s what I’m trying to say. 🙂

This doesn’t make any sense. Do you observe this behaviour even after doing the following:
1. Ensure that Adobe Gamma is not starting automatically
2. Check your system default monitor profile in the advanced display
settings (should be your *original* OptiCAL profile, as created by OptiCAL, and not edited with Adobe Gamma, of course. I realise you used Adobe RGB though, for the Adobe Gamma test,
and not your OptiCAL profile)
3. Reboot
4. Double check your system default monitor profile
5. Open Photoshop and check the monitor profile in use

If it’s still wrong, perhaps you have a similar issue to me, regarding multiple monitors? 🙂

Greg.

Greg wrote:

This doesn’t make any sense.

Maybe. 🙂

I’ve just tried the 5 steps you described.

I first went to Adobe Gamma in the Control Panel where I loaded the Adobe RGB(1998) profile and changed the settings completely, so that everything on the desktop was dark blue and utterly ugly. I then changed the description to ‘Totally Wacky Profile’ and saved the profile under the same name (Totally Wacky Profile) when I closed Adobe Gamma. Then I restarted the computer and OptiCAL Startup loaded the normal VP201s profile into the LUT. Everything was back to normal with a neutral gray desktop. Photoshop was behaving normally too so it’s not the Totally Wacky Profile I’m using after the restart. It’s my normal VP201s profile because that’s the profile that OptiCAL startup loads when Windows starts. It knows that the VP201s profile is the default monitor profile and therefore loads it. (As I wrote earlier, I don’t know where it get that information from though).

If I open Adobe Gamma in the Control Panel now, the profile with the name ‘Totally Wacky Profile’ is loaded and when I go into the color settings of Photoshop I see ‘Monitor RGB – Totally Wacky Profile’.

In Control Panel > Display > Settings > Advanced > Color Management, the ‘Totally Wacky Profile’ is the only profile listed in there and therefore the default profile according to Windows, but that’s obviously not true. The VP201s profile is the current profile in use. If the ‘Totally Wacky Profile’ was loaded into the LUT, everything would be blue and utterly ugly right now but it’s not.

—
Regards
Madsen.

"Thomas Madsen" wrote in message

Greg wrote:

This doesn’t make any sense.

Maybe. 🙂

I’ve just tried the 5 steps you described.

In Control Panel > Display > Settings > Advanced > Color Management, the ‘Totally Wacky Profile’ is the only profile listed in there and therefore the default profile according to Windows, but that’s obviously not true. The VP201s profile is the current profile in use. If the ‘Totally Wacky Profile’ was loaded into the LUT, everything would be blue and utterly ugly right now but it’s not.

I think the Adobe Gamma profile *is* the one in use. However, Adobe Gamma did not successfully load the LUT from the Adobe Gamma profile. I’ve noticed a similar thing on my system. For example, I had an Eye One Display profile as my system default, but I disabled the Eye One calibration loader from
starting, and enabled Adobe Gamma Loader instead. When I rebooted the system,
Adobe Gamma loaded the LUT from the Eye One monitor profile. (yes, despite the fact that Adobe Gamma didn’t create the profile – it still worked). However,
I then reset the LUT using a seperate utility, and then manually re-reran the Adobe
Gamma Loader. This didn’t work – the Adobe Gamma Loader failed to load the LUT
from the same monitor profile which it did successfully load from at system startup. For
some reason, it seems that the Adobe Gamma Loader (and probably the Adobe Gamma applet),
sometimes fail to load the LUT. But that is a seperate issue to which monitor profile
Photoshop is actually using. (I agree that the situation you describe is invalid though –
the LUT doesn’t correspond to the profile in use, which is plain wrong)

When I do everything normally, it all seems to work fine. 🙂

Greg.

Greg wrote:

(I agree that the situation you describe is invalid though – the LUT doesn’t correspond to the profile in use, which is plain wrong)

If I put Adobe Gamma Loader in my startup folder and restart the computer, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_ loader.png>

If I use OptiCAL startup instead, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png> OptiCAL loads the VP201s profile but neither WinXP nor Photoshop shows me that. According to them, the wacky profile is the one in use. Photoshop gets the information from Adobe Gamma, as far as I can see.

When I do everything normally, it all seems to work fine. 🙂

Same here. Normally, I let OptiCAL startup do the gamma loading and when I use OptiCAL to calibrate and profile the monitor, OptiCAL automatically makes sure that this is what happens:
<http://home18.inet.tele.dk/madsen/winxp/monitor/normal.png> but if it fails to change the default profile inside Control Panel > Display > Settings > Advanced > Color Management (and I have seen that happened sometimes), the profile inside Adobe Gamma won’t change either, and then you’ll get the wrong information both from Windows and Photoshop: < http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png>.

—
Regards
Madsen.

Thomas,
I always make sure the monitor profile in the Windows control panel settings is the one I want.
I never rely on anything else to set that for me. Other than my issue with multiple
monitors, everything is working fine the first time the system boots. After the system has booted, if I stuff around with things, I double check that everything
has taken effect. One tool I use to help with this is Powerstrip.

Greg.

"Thomas Madsen" wrote in message

Greg wrote:

(I agree that the situation you describe is invalid though – the LUT doesn’t correspond to the profile in use, which is plain wrong)

If I put Adobe Gamma Loader in my startup folder and restart the computer, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_ loader.png>
If I use OptiCAL startup instead, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png> OptiCAL loads the VP201s profile but neither WinXP nor Photoshop shows me that. According to them, the wacky profile is the one in use. Photoshop gets the information from Adobe Gamma, as far as I can see.

When I do everything normally, it all seems to work fine. 🙂

Same here. Normally, I let OptiCAL startup do the gamma loading and when I use OptiCAL to calibrate and profile the monitor, OptiCAL automatically makes sure that this is what happens:
<http://home18.inet.tele.dk/madsen/winxp/monitor/normal.png> but if it fails to change the default profile inside Control Panel > Display > Settings > Advanced > Color Management (and I have seen that happened sometimes), the profile inside Adobe Gamma won’t change either, and then you’ll get the wrong information both from Windows and Photoshop: < http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png>.
—
Regards
Madsen.

Greg wrote:

I always make sure the monitor profile in the Windows control panel settings is the one I want.

Me2.

I never rely on anything else to set that for me. Other than my issue with multiple monitors, everything is working fine the first time the system boots.

It also works fine here if I only use one monitor.
(I’m unable to have fairly accurate colors on both my two monitors at the same time too, but that’s another story).

One tool I use to help with this is Powerstrip.

I used to force my old ATI graphic card to run in 1920 x 1200 @ 85Hz with Powerstrip, but I don’t have the ATI card anymore, so I’m not using Powerstrip anymore either.

Is Powerstrip the separate utility you use to reset the LUT, or how do you do that?

—
Regards
Madsen.

"Greg" wrote in message

Thomas,
I always make sure the monitor profile in the Windows control panel

settings

is the one I want.
I never rely on anything else to set that for me. Other than my issue with multiple
monitors, everything is working fine the first time the system boots. After the system has booted, if I stuff around with things, I double check that everything
has taken effect. One tool I use to help with this is Powerstrip.

It also gets dumped in the registry. This might explain why the wrong profile was read when both the gamma loader and optical loader were active.

—–= Posted via Newsfeeds.Com, Uncensored Usenet News =—– http://www.newsfeeds.com – The #1 Newsgroup Service in the World! —–== Over 100,000 Newsgroups – 19 Different Servers! =—–

"Thomas Madsen" wrote in message

Is Powerstrip the separate utility you use to reset the LUT, or how do you do that?

Yes, that’s right. I like Powerstrip, because it can unobtrusively display the current
LUT data, too.

Greg.

Thomas,
There’s something about your screen grabs which I don’t understand at all. Why are they different
colours? I thought the LUT data was loaded into the graphics card, and only affected the video signals
sent to the monitor. But from your screen grabs, it appears that the graphics driver itself is using the
LUT data, which comes as a huge surprise to me.

They *are* screen grabs, right? (they look too good to be photos)

Greg.

"Thomas Madsen" wrote in message

Greg wrote:

(I agree that the situation you describe is invalid though – the LUT doesn’t correspond to the profile in use, which is plain wrong)

If I put Adobe Gamma Loader in my startup folder and restart the computer, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_ loader.png>
If I use OptiCAL startup instead, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png> OptiCAL loads the VP201s profile but neither WinXP nor Photoshop shows me that. According to them, the wacky profile is the one in use. Photoshop gets the information from Adobe Gamma, as far as I can see.

When I do everything normally, it all seems to work fine. 🙂

Same here. Normally, I let OptiCAL startup do the gamma loading and when I use OptiCAL to calibrate and profile the monitor, OptiCAL automatically makes sure that this is what happens:
<http://home18.inet.tele.dk/madsen/winxp/monitor/normal.png> but if it fails to change the default profile inside Control Panel > Display > Settings > Advanced > Color Management (and I have seen that happened sometimes), the profile inside Adobe Gamma won’t change either, and then you’ll get the wrong information both from Windows and Photoshop: < http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png>.
—
Regards
Madsen.

"Thomas Madsen" wrote in message

If I put Adobe Gamma Loader in my startup folder and restart the computer, this is what I get:
< ://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_load er.png>

What was the default monitor profile in the Windows control panel before you rebooted?
I assume it was the Totally Wacky Profile, right? (as is shown in the Windows Control Panel)
I don’t think the Adobe Gamma Loader changes the system monitor profile. All it
does is load the gamma correction table from whatever happens to be the system
default monitor profile, at the time it’s run.

If I use OptiCAL startup instead, this is what I get:
< http://home18.inet.tele.dk/madsen/winxp/monitor/optical_star tup.png> OptiCAL loads the VP201s profile but neither WinXP nor Photoshop shows me that. According to them, the wacky profile is the one in use. Photoshop gets the information from Adobe Gamma, as far as I can see.

OptiCAL probably doesn’t "load" the VP201s profile. I suspect it’s simply failing to
load the gamma
correction table from the system default monitor profile. The reason it is failing may be
because the OptiCAL loader detects that the profile is not an OptiCAL profile, so it
plays it safe, and simply ignores the profile altogether. This is how my Eye One calibration
loader behaves – it simply will not load the gamma correction table from an Adobe Gamma
profile. I suspect your OptiCAL calibration loader works like my Eye One loader – it simply
attempts to load the gamma table from the Windows default. To really prove it, create a
*different* wacky profile with OptiCAL – one that is the opposite to the Adobe Gamma
version. Leave the Adobe Gamma profile as the system default, configure the OptiCAL
loader to start automatically – I bet it will *not* load the OptiCAL gamma table.

I do not think Photoshop gets it’s profile information from Adobe Gamma at all. It uses
whatever profile is the current Windows default. I still don’t see any evidence to
the contrary. The issue of which gamma table is loaded is entirely outside the scope
of Photoshop.

Greg.

Thomas,
Also, I suggest you assess the results of calibration loaders *before* opening Adobe Gamma. Adobe Gamma
can modify the LUT as soon as it’s run, which may cause extra confusion. 🙂 I’ve just realised that
your screen grabs were done with Adobe Gamma actually open. I have an uneasy feeling about that.
If you want to load a LUT from the system default monitor profile, use either your OptiCAL calibration
loader, or the Adobe Gamma *Loader*. Actually, I find that the Adobe Gamma Loader can load the
LUT from my Eye One Display profiles as well.

Greg.

Thomas,
I can’t reproduce the different coloured screen grabs. When I create a profile with a wacky LUT,
the appearance of the desktop changes a lot, but screen grabs don’t change at all.

Do you have some special way of doing a screen grab, which somehow captures the data after it
has been through the LUT of the graphics card??????? (external video capture device???)

Otherwise, perhaps your graphics card doesn’t actually have a hardware LUT at all, and the calibration
loaders are able to instruct the driver to do the gamma correction instead?

Perplexed…….

Greg.

Here’s a summary of what I think everything does:

Photoshop: Uses the Windows system default monitor profile, as configured in Control Panel | Display | Settings | Advanced | Color Management. *Assumes* that corresponding LUT from this profile has been loaded by a calibration loader.

Adobe Gamma: Upon *saving* a monitor profile, it sets the Windows system default profile to be that profile, and loads the LUT from that same profile into the graphics card. (I am unsure exactly how Adobe Gamma behaves when it is initially opened, but I don’t think this is
particularly important. It does seem to reliably reset the LUT to what it was before, if an exit without a save is done)

Adobe Gamma Loader: Attempts to load the LUT from the current Windows system default monitor profile. Seems to also work for profiles which have not been created by Adobe Gamma.

OptiCAL profiler: (tentative) Upon completion of creating a monitor profile, sets the Windows system default monitor profile to be that profile, and loads the LUT from that profile into the graphics card.

OptiCAL calibration loader: (tentative) Attempts to load the LUT from the current Windows system default monitor profile. *Only* works for profiles which have been created by OptiCAL (and probably PhotoCAL?)

Greg.

Greg wrote:

Photoshop: Uses the Windows system default monitor profile, as configured in Control Panel | Display | Settings | Advanced | Color Management. *Assumes* that corresponding LUT from this profile has been loaded by a calibration loader.

After further testing, I can see that you’re right Greg. I’ve tried to load a different profile in Adobe Gamma than the one listed under Control Panel > Display > Settings > Advanced > Color Management (Adobe Gamma doesn’t change the default system profile before you save with Adobe Gamma). With VP201s as the Windows system default monitor profile, and a different profile loaded in Adobe Gamma, Photoshop says: ‘Monitor RGB – VP201s’ so Photoshop doesn’t pick the information from Adobe Gamma, as I wrote earlier. It picks it from Control Panel > Display > Settings > Advanced > Color Management.

Adobe Gamma: Upon *saving* a monitor profile, it sets the Windows system default profile to be that profile, and loads the LUT from that same profile into the graphics card.

Yep. And if you change the profile inside Control Panel > Display > Settings > Advanced > Color Management, the profile inside Adobe Gamma changes to the same profile automatically.

Adobe Gamma Loader: Attempts to load the LUT from the current Windows system default monitor profile. Seems to also work for profiles which have not been created by Adobe Gamma.

It doesn’t seem that Adobe Gamma Loader is able to load the profile made with OptiCAL here. If VP201s (the profile made with OptiCAL) is the default profile inside Control Panel > Display > Settings > Advanced > Color Management and I change OptiCAL Startup with Adobe Gamma Loader in the startup folder, Adobe Gamma loader doesn’t change the behaviour of the display when Windows restarts like OptiCAL Startup does with the same profile. If I open Adobe Gamma in the Control Panel, nothing happens either.
I’ve read somewhere that it’s the ‘vcgt’ tag in the profile that changes the behaviour of the display when you load a profile with such a tag. Maybe Adobe Gamma can’t recognize the ‘vcgt’ tag made by OptiCAL but I don’t know.

I can’t change the behaviour of the monitor with Adobe Gamma when the OptiCAL profile is loaded either because both ‘Phosphors’, ‘Hardware’, and ‘Adjusted’ under ‘White Point’ is set to ‘Custom’, but if I set the ‘Adjusted’ setting to something else than ‘Custom’, the behaviour of the display changes. In order to keep that change, I have to save the profile with Adobe Gamma but then it’s not an OptiCAL profile anymore.

OptiCAL profiler: (tentative) Upon completion of creating a monitor profile, sets the Windows system default monitor profile to be that profile, and loads the LUT from that profile into the graphics card.

Yes (if I choose that the profile made with OptiCAL should be the default one, that is).

OptiCAL calibration loader: (tentative) Attempts to load the LUT from the current Windows system default monitor profile. *Only* works for profiles which have been created by OptiCAL (and probably PhotoCAL?)

From my point of view, OptiCAL Startup doesn’t try to load the current system default monitor profile. Well maybe it does, but fails if the profile isn’t created by OptiCAL as you say, but it loads the VP201s profile even if the profile under Control Panel > Display > Settings > Advanced > Color Management is a different one made with Adobe Gamma for instance.

And now to the "mystery" of the wacky profile screenshot. 🙂 < http://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_ loader.png> I was just trying to illustrate how my monitor looked when the Adobe Gamma Loader was loading the wacky monitor profile. I couldn’t capture the strange colors because when I changed back to the profile I normally use (the VP201s profile), the strange colors of the screenshot was gone too, so I used Hue/ Saturation to change the colors just to illustrate the strange colors of the monitor with the wacky profile loaded.

I can see now that I’ve got it all wrong in the first place. I’m sorry about that and thanks for your patience.

—
Regards
Madsen.

"Thomas Madsen" wrote in message

Adobe Gamma: Upon *saving* a monitor profile, it sets the Windows system default profile to be that profile, and loads the LUT from that same profile into the graphics card.

Yep. And if you change the profile inside Control Panel > Display > Settings > Advanced > Color Management, the profile inside Adobe Gamma changes to the same profile automatically.

I don’t think it always does this. 🙂 (I saw a case where it seemed to start with a
profile which was not the system default)

Adobe Gamma Loader: Attempts to load the LUT from the current Windows system default monitor profile. Seems to also work for profiles which have not been created by Adobe Gamma.

It doesn’t seem that Adobe Gamma Loader is able to load the profile made with OptiCAL here. If VP201s (the profile made with OptiCAL) is the default profile inside Control Panel > Display > Settings > Advanced > Color Management and I change OptiCAL Startup with Adobe Gamma Loader in the startup folder, Adobe Gamma loader doesn’t change the behaviour of the display when Windows restarts like OptiCAL Startup does with the same profile.

Ah, ok. Obviously my Eye One Display profiles are compatible with Adobe Gamma,
but your profiles aren’t.

If I open Adobe
Gamma in the Control Panel, nothing happens either.
I’ve read somewhere that it’s the ‘vcgt’ tag in the profile that changes the behaviour of the display when you load a profile with such a tag. Maybe Adobe Gamma can’t recognize the ‘vcgt’ tag made by OptiCAL but I don’t know.

Yes, something like that. (the vcgt tag is definitely the tag which contains the
gamma correction tables)

OptiCAL calibration loader: (tentative) Attempts to load the LUT from the current Windows system default monitor profile. *Only* works for profiles which have been created by OptiCAL (and probably PhotoCAL?)

From my point of view, OptiCAL Startup doesn’t try to load the current system default monitor profile. Well maybe it does, but fails if the profile isn’t created by OptiCAL as you say, but it loads the VP201s profile even if the profile under Control Panel > Display > Settings > Advanced > Color Management is a different one made with Adobe Gamma for instance.

What do you mean "loads the profile"? Do you mean "loads the gamma LUT"? Are you absolutely sure about that behaviour?

And now to the "mystery" of the wacky profile screenshot. 🙂 < http://home18.inet.tele.dk/madsen/winxp/monitor/adobe_gamma_ loader.png> I was just trying to illustrate how my monitor looked when the Adobe Gamma Loader was loading the wacky monitor profile. I couldn’t capture the strange colors because when I changed back to the profile I normally use (the VP201s profile), the strange colors of the screenshot was gone too, so I used Hue/ Saturation to change the colors just to illustrate the strange colors of the monitor with the wacky profile loaded.

Arrrghhhhh!!!!!!!!!!!!!!!!!!!!!!! 🙂 I was tearing my hair out on this one. 🙂
(you would not have captured the slightest difference, regardless. The screen grab
captures the data *before* it’s sent to the graphics card, thus the screen grab won’t
change at all, regardless of what data you load into the LUT. The gamma correction is
applied in hardware, on the graphics card itself. Naturally, the screen grab would change
for colour managed applications, if the profile proper was different))

Glad we got to the bottom of all this. ;^)

Greg.

Greg wrote:

What do you mean "loads the profile"? Do you mean "loads the gamma LUT"?

I mean that the behaviour of the monitor changes in the same second that the OptiCAL logo appears on the screen and I can see that it’s the VP201s profile it loads. That profile is easy for me to recognize.

—
Regards
Madsen.

"Thomas Madsen" wrote in message

Greg wrote:

What do you mean "loads the profile"? Do you mean "loads the gamma LUT"?

I mean that the behaviour of the monitor changes in the same second that the OptiCAL logo appears on the screen and I can see that it’s the VP201s profile it loads. That profile is easy for me to recognize.

Oh, well that’s badness!! 🙂 I take back what I said about the OptiCAL calibration loader loading the Windows default monitor profile then. It appears that
you need to *manually* ensure that the Windows default monitor profile is the same profile
which the OptiCAL calibration loader gets it’s LUT data from, *if* you didn’t
get the OptiCAL profiler to do that for you, at the time you ran the profiler.

Greg.

Greg wrote:

It appears that you need to *manually* ensure that the Windows default monitor profile is the same profile which the OptiCAL calibration loader gets it’s LUT data from, *if* you didn’t get the OptiCAL profiler to do that for you, at the time you ran the profiler.

Exactly. Normally the OptiCAL profiler makes sure that it happens, but if it fails, it can be quite confusing when Photoshop shows you one thing (because it looks at the profile inside Control Panel > Display > Settings > Advanced > Color Management) and the monitor shows you something else, because OptiCAL Startup loads another profile than the one inside Control Panel > Display > Settings > Advanced > Color Management.

—
Regards
Madsen.

Greg,

I posted a message in another thread that you are participating in. Here is a copy of my text.

Greg,

Long time. You and I chatted some time ago about something similar.

I just replaced a Matrox G550 with a P650. The P650 comes with a program called Coloreal that can be used to calibrate (via eyeball) a dual monitor config. Any, I too am having a bit of a difficult time understanding the relationship between AdobeGamma, the AdobeGamma Loader, XP and Coloreal. Here is my situation.

I created a profile with Coloreal which has one monitor very bright and the other very dark (for test purposes); lets refer to this monitor setup as "DL" for short. I delete the Coloreal profile from Properties-Settings-Advanced-Color Management. I reboot and the DL appearance returns. I can I add and profile I want via
Properties-Settings-Advanced-Color Management and reboot and I still get the DL appearance. I suspect the LUT value the make up DL are being saved in the Registry. I gather you investigated this and found that to be true, yes?

If I run (by hand) the AdobeGamma Loader "AGL" it will change the monitor appearance based on the Default monitor profile. I think this makes sense. However when I reboot (again), I’m back to DL. I gather that running AGL does not update the Registry. Note anything about the Registry is pure conjecture on my part. What ar your thoughts?

As a related question, I gather that XP does nothing with the info in Properties-Settings-Advanced-Color Management, other than to keep in there for any piece of software that cares? Is this consistent with you understanding?

I also notice, that I can change the default profile in
Properties-Settings-Advanced-Color Management run AGL then change the default profile to something else and rerun AGL but this time nothing visibly changes. Almost like it will only do something the first time. Very strange.

I’d be interested in you experience with regard to any of this.

Jerry

"ozonepark" wrote in message

Long time. You and I chatted some time ago about something similar.

Hi – yes – I remember you. 🙂

Note anything
about the Registry is pure conjecture on my part. What ar your thoughts?

Well, Flycaster says that something monitor related gets put into the registry, and
I’ve seen it too. (somewhere under an Adobe related registry key I think) I have
no idea how Coloreal behaves though. The behaviour you observe seems to match OptiCAL. I don’t have either OptiCAL or Coloreal – I have the Eye One Display, and it seems to always load (or attempt to load) the LUT from the Windows default
monitor profile. Nice and simple – I like that behaviour. 🙂 (I’d prefer it to issue a warning
if it detects that the profile is not an Eye One profile, though)

As a related question, I gather that XP does nothing with the info in Properties-Settings-Advanced-Color Management, other than to keep in there for any piece of software that cares? Is this consistent with you understanding?

Yes – that matches my understanding.

I also notice, that I can change the default profile in
Properties-Settings-Advanced-Color Management run AGL then change the default profile to something else and rerun AGL but this time nothing visibly changes. Almost like it will only do something the first time. Very strange.

Strange perhaps, but it doesn’t really matter much, because when we invoke Adobe Gamma, we normally want to create a new profile, and the first step is to load the starting profile, if the profile it happened to open initially isn’t the
one we want to use as the starting point.

I’d be interested in you experience with regard to any of this.

Perhaps all this works much more consistently and intuitively on a Mac? 🙂

Greg.

"Greg" wrote in message
[snip]

Well, Flycaster says that something monitor related gets put into the registry, and
I’ve seen it too. (somewhere under an Adobe related registry key I think)

[snip]

Do a regedit Find on your profile, and it’ll take you right to it. Colorcal used to advise deleting the value when re-profiling, but I dunno what it does, or if it’s even relevant. Seems to me, though, that you’d want it to be the same value (ie, profile) as it is in the control panel. But, registry stuff is voodoo to me…

—–= Posted via Newsfeeds.Com, Uncensored Usenet News =—– http://www.newsfeeds.com – The #1 Newsgroup Service in the World! —–== Over 100,000 Newsgroups – 19 Different Servers! =—–