[argyllcms] Re: Capture video card gamma LUT to ICC profile
- From: Benjamin Shadwick <benshadwick@xxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Fri, 3 Feb 2012 00:01:03 -0800
Thanks, I seem to have figured it out:
"dispwin -s lutfile.cal" dumps the current video card LUT to a .cal file
"fakeread -k lutfile.cal baseprofile.icm outputfile" creates the
outputfile.ti3 file using info from the cal and icm files.
"colprof outputfile" converts the outputfile.ti3 file to outputfile.icm.
The .icm file that I used as a base specific to my monitor that was already
being used by Windows, which contained no vcgt tag. After running the above
tools, I got an output .icm file that was much larger (~134KB instead of
~1KB) that contains a vcgt tag.
I set this new .icm as the default profile for my monitor in Windows 7's
Color Management applet, and it uploaded the LUT to the video card. I was
able to verify using a calibration tool that reads the video card LUT that
the ramp loaded by Windows from my .icm file is visually identical to the
original source data, which is exactly what I was hoping for.
This is good because it means that I now hopefully no longer have to run
Monitor Configuration Wizard to load and enforce my custom LUT. I did
notice that Windows 7 isn't any better than MCW at preventing games from
resetting the LUT, but I have other ways around that (
http://colorclutch.sourceforge.net/ among other things).
Thanks again to both of you for the help!
On Thu, Feb 2, 2012 at 11:41 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
> Benjamin Shadwick wrote:
> > I have successfully followed your first step to dump the current LUT to a
> > .cal file, but I'm not sure how to invoke dispread and colprof to do what
> > you describe. Specifically, dispread wants more parameters than just -k
> > filename.cal. Can you provide more details?
>
> dispread reads the display values using an instrument.
> See <http://www.argyllcms.com/doc/Scenarios.html#PM3>
>
> > Nikolay:
> >
> > I don't understand your instructions for using fakeread on the output of
> > targen. Fakeread seems to want 2 files in addition to the .cal file
> > specified for the -k parameter.
>
> You need to go though a similar proceedure to profiling
> a display: Create a set of test values (.ti1) file
> than used fakeread instead of dispread.
>
> Look at the documentation for each utility to get further
> information on the required parameters.
>
> Graeme Gill.
>
Other related posts:
