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.