[argyllcms] Loading CAL file with dispwin

Hi everyone,

Going through the final steps of calibrating and profiling a display using
Argyll and I am not clear on what dispwin does.

First, I dispcal my monitor. Got a *.cal file.
Second, I generated an RGB *.ti1 testchart file.
Third, I dispread my monitor using the *.ti1 file while applying the *.cal.
Fourth, I created an ICC profile using profile and the *.ti3 file.
Fifth, this is in Windows, I installed the profile in the appropriate
directory. Then selected as the default under Display Properties > Advanced.

Question. And I realize this will vary with OS but, say under Windows,
selecting a given profile to make it the default is probably not enough to
download the VCGT tag into the video LUT -- because nothing changed on my
monitor when I did so (unlike on MacOSX).

So, I believe I have two choices at that point, since the VCGT *is* included
in the resultant profile, as far as I can see. So the information is there
for Windows to use. The choices are : to reboot, to have Windows download
the VCGT at load time into the video LUT *or*, better, I thinkik, to use
dispwin. That's what I tried. I used :

> dispwin -v myCalibration.cal

I believe that the above *did* the job because I could tell my screen
changed appearance right after hitting Enter. So now, if I launch Photoshop,
not only my new Argyll monitor profile should appear in its place (Color
Settings > MonitorRGB) but the videoLUT should also be correctly loaded with
myCalibration.cal, right?

Somehow, I remain skeptical. So I launched dispwin with the -V parameter and
got the following :

> C:\Users\Roger\Argyll>dispwin -v -V
> About to open dispwin object on the display
> Setting White
> Setting 75% Grey
> Setting 50% Grey
> Setting 25% Grey
> Setting 12.5% Grey
> Setting Black
> Setting Red
> Setting Green
> Setting Blue
> Setting Cyan
> Setting Magenta
> Setting Yellow
> Darkening screen
> Lightening screen
> Restoring screen
> Normal beep
> Good beep
> Bad double beep
> About to destroy dispwin object

That's not really a confirmation of anything. What kind of output am I
supposed to get? Could be a bug in my installation (like that -x parameter
in spotread).

I tried :

>dispwin -v -VmyCalibration.cal

And

>dispwin -v -V"myCalibration.cal"

With the same results.

Any thoughts?
  
Roger Breton

Other related posts: