[argyllcms] Re: problem loading LUT-based icc profile to CRT
- From: David Heinrich <dh003i@xxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Wed, 9 Dec 2009 17:23:34 -0500
Ok, me and Troy Sobotka (mostly him) figured out the issue. Argyll's dispwin
was operating on the wrong display! I wasn't specifying -d2, and I needed
to. Running
sudo dispwin -r -d1
sudo dispwin -r -d2
resolved it. with -d2, I noticed the CRT lightening and darkening. Not so
with -d1.
Graeme, thank you for his wonderful tool and your thoughts on the matter.
On Wed, Dec 9, 2009 at 2:29 PM, David Heinrich <dh003i@xxxxxxxxx> wrote:
>
>
> On Wed, Dec 9, 2009 at 3:26 AM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
>
>> David Heinrich wrote:
>>
>>> I've made a LUT-based profile and am trying to load it (where are they
>>> loaded anyways, system software, gpu, monitor?).
>>>
>>
>> The 'vcgt' tag is loaded into the graphic card hardware to calibrate
>> the monitor. It's up to applications to load the profile to access
>> the monitor characterization information, so that they are
>> able to transform colors into the calibrated monitors colorspace.
>>
>> See <http://www.argyllcms.com/doc/calvschar.html>
>>
>>
>> When alternating between
>>> clearing profiles from the system and loading my LUT-based profile, I see
>>> a
>>> quick flicker on the screen (but not one of the audible ones where the
>>> CRT
>>> makes noise). However, I don't notice any change in my ~18% neutral gray
>>> desktop background.
>>>
>>
>> Maybe the monitor has a native characteristic very similar to
>> the calibration target ?
>>
>> Have you tried loading "strange.cal" from the argyll ref directory,
>> to get a more obvious visual indication that the calibration gets loaded ?
>>
>
> What do I do to do that?
>
>
>> I have a Sony GDM-F520 CRT monitor, 2048x1536. xrandr reports detected
>>> EDID
>>> modes, so I'm not sure why I'm getting these weird "Failed to get EDID
>>> for
>>> display" messages. (DVI-I_2/analog is my CRT, I'm not using the other one
>>> at
>>> the moment).
>>> *
>>> $ sudo /opt/Argyll/bin/dispwin -v -c; dispwin -v -E 9 -V
>>> colprof-sony-gdm-f520-3000-patches-12-6-2009.icc*
>>>
>>
>> Verify: 'colprof-sony-gdm-f520-3000-patches-12-6-2009.icc' is NOT loaded
>>> (discrepancy 12.2%)
>>>
>>
>> *$ sudo /opt/Argyll/bin/dispwin -v -E 9 -I
>>>
>>> colprof-sony-gdm-f520-3000-patches-12-6-2009.icc ; dispwin -v -E 9 -V
>>> colprof-sony-gdm-f520-3000-patches-12-6-2009.icc*
>>>
>>
>> Verify: 'colprof-sony-gdm-f520-3000-patches-12-6-2009.icc' IS loaded
>>> (discrepancy 0.0%)
>>>
>>
>> Seems like the calibration gets loaded as far as the software
>> is concerned.
>>
>
> Does that mean it is probably working? Any reason it wouldn't be if the
> software says it is?
>
>
>>
>> *$ xrandr*
>>>
>>
>> Try running xrandr --prop and see whether you can see the EDID property.
>> Is it called "EDID_DATA" or something else ?
>> If it's not there or not accessible because it's called something else,
>> then that's why the warnings about it.
>>
>
> Here's the result, I see no EDIT or EDID_DATA field.
>
> $ xrandr --prop
>
> Screen 0: minimum 320 x 200, current 2048 x 1536, maximum 3840 x 3936
> DVI-I_1/digital connected 1920x1200+0+0 (normal left inverted right x axis
> y axis) 480mm x 300mm
> _HDMI: 0 (0x00000000) range:
> (0,1)
> _Coherent: 0 (0x00000000) range:
> (0,1)
>
> _PanningArea:
>
> _OutputNumber: 1
> (0x00000001)
> ConnectorNumber: 1
> (0x00000001)
> ConnectorType:
> DVI-I
> SignalFormat:
> TMDS
> supported:
> TMDS
> 3840x2400 12.7
> +
> 1920x2400
> 20.1
>
> 1920x1200
> 40.9*
>
> 1600x1200
> 59.9
>
> 1280x1024 75.0
> 59.9
> 1024x768 84.9 75.1 70.1
> 60.0
> 800x600 84.7 72.2 75.0 60.3
> 56.2
> 640x480 84.4 75.0 72.8
> 60.0
> DVI-I_1/analog disconnected (normal left inverted right x axis y
> axis)
> _HDMI: 0 (0x00000000) range:
> (0,1)
> _Coherent: 0 (0x00000000) range:
> (0,1)
>
> _PanningArea:
>
> _OutputNumber: 2
> (0x00000002)
> ConnectorNumber: 1
> (0x00000001)
> ConnectorType:
> DVI-I
> SignalFormat:
> VGA
> supported:
> VGA
> DVI-I_2/digital disconnected (normal left inverted right x axis y
> axis)
> _HDMI: 0 (0x00000000) range:
> (0,1)
> _Coherent: 0 (0x00000000) range:
> (0,1)
>
> _PanningArea:
>
> _OutputNumber: 3
> (0x00000003)
> ConnectorNumber: 2
> (0x00000002)
> ConnectorType:
> DVI-I
> SignalFormat:
> TMDS
> supported:
> TMDS
> DVI-I_2/analog connected 2048x1536+0+0 (normal left inverted right x axis y
> axis) 0mm x 0mm
> _HDMI: 0 (0x00000000) range:
> (0,1)
> _Coherent: 0 (0x00000000) range:
> (0,1)
>
> _PanningArea:
>
> _OutputNumber: 4
> (0x00000004)
> ConnectorNumber: 2
> (0x00000002)
> ConnectorType:
> DVI-I
> SignalFormat:
> VGA
> supported:
> VGA
> 2048x1536_73
> 73.0*+
>
> 2048x1536
> 60.0
>
> 1920x1440 75.0 60.0
> 1856x1392 75.0 60.0
> 1792x1344 75.0 60.0
> 1600x1200 85.0 75.0 70.0 65.0 60.0
> 1680x1050 84.9 74.9 69.9 60.0
> 1600x1024 60.2
> 1400x1050 85.0 74.8 70.0 60.0
> 1280x1024 85.0 75.0 60.0
> 1440x900 59.9
> 1280x960 85.0 60.0
> 1360x768 59.8
> 1152x864 100.0 85.1 85.0 75.0 75.0 70.0
> 60.0
> 1024x768 85.0 75.0 70.1 60.0 43.5
> 832x624 74.6
> 800x600 85.1 72.2 75.0 60.3 56.2
> 640x480 85.0 72.8 75.0 59.9
> 720x400 85.0
> 640x400 85.1
> 640x350 85.1
>
>
>
>>
>> Have you tried V1.1.0 RC2, it has a couple of fixes in this area, and
>> will locate the EDID data from either the "EDID_DATA" or "EDID" output
>> property.
>> (
>> //www.freelists.org/post/argyllcms/ArgyllCMS-V110-RC2-is-now-available
>> )
>>
>
> Trying it now, will update on it.
>
>>
>> Graeme Gill.
>>
>>
>
>
> --
> Social sciences can never use experience to verify their statements --
> Ludwig von Mises
>
--
Social sciences can never use experience to verify their statements --
Ludwig von Mises
Other related posts:
