1 |
On Sunday 27 Sep 2015 09:58:43 Peter Humphrey wrote: |
2 |
> On Saturday 26 September 2015 16:11:04 Mick wrote: |
3 |
> > Thank you all for your answers. They guided me to do some reading in |
4 |
> > this field, which is quite a science all on its own! |
5 |
> |
6 |
> --->8 |
7 |
> |
8 |
> > Peter's description does not mention which application loads the .icc |
9 |
> > file that the hughski creates, but I'm guessing there must be something |
10 |
> > that does read it, if the monitor settings are indeed altered. |
11 |
> |
12 |
> As far as I remember, it's the colorhug's own program that sets the monitor |
13 |
> at the end of its calibration process. After that, the monitor has kept |
14 |
> those settings and hasn't needed any further tweaking. |
15 |
> |
16 |
> I do have the two .icc files in .local/share/icc: |
17 |
> |
18 |
> $ ls -l .local/share/icc |
19 |
> total 28K |
20 |
> -rw-r--r-- 1 prh prh 1.2K Sep 9 16:51 |
21 |
> edid-fbec4f9c1804ea718b6e1b585fc234ad.icc -rw-rw-r-- 1 prh prh 21K Sep 10 |
22 |
> 10:41 GCM - Samsung - SMS27A350H - unknown (2015-09-10) [04-58-44].icc |
23 |
> |
24 |
> /usr/bin/file shows them both as "ColorSync ICC Profile". I don't know why |
25 |
> there are two, nor why they have such different sizes. |
26 |
|
27 |
I'm guessing that the 'edid-fbec4f9c1804ea718b6e1b585fc234ad.icc' was |
28 |
extracted from your monitor's EEPROM chip through the i2c bus and saved on |
29 |
disk by the LiveCD you ran, but the 'GCM - Samsung - SMS27A350H - unknown |
30 |
(2015-09-10) [04-58-44].icc' was generated by the colorimeter during your |
31 |
calibration exercise. |
32 |
|
33 |
I'm also guessing that the smaller size of the first file is because your |
34 |
monitor's EDID is of an earlier version, e.g. EDID-v1.1 or some such, which |
35 |
used to only contain a 128-byte data structure. I seem to recall that very |
36 |
early EDID versions didn't even contain colospace and Gamma data, but may be |
37 |
wrong. |
38 |
|
39 |
These are the sizes : |
40 |
|
41 |
ls -n ~/.local/share/color/icc/devices/Display/ |
42 |
total 800 |
43 |
-rw-r--r-- 1 1001 1001 1944 Sep 18 18:16 ACI ASUS VS239 |
44 |
EALMTF200702_edid.icc |
45 |
-rw-r--r-- 1 1001 1001 2016 Sep 18 18:16 Dell Computer DELL ST2320L |
46 |
MP82K0712EJL_edid.icc |
47 |
-rw-r--r-- 1 1001 1001 20884 Sep 18 19:01 P2311H 2012-06-20 2.2 MQ-HQ |
48 |
3xCurve+MTX.icc |
49 |
-rw-r--r-- 1 1001 1001 783804 Sep 18 19:02 PA248 2015-04-18 S XYZLUT+MTX.icc |
50 |
|
51 |
The first two are from the monitors' EDID content, the latter are the profiles |
52 |
I downloaded from the Taxi DB. Some of these contributors' profiles were |
53 |
created with spyder or other expensive colorimeters, so I am surmising that |
54 |
they capture more data points and contain more information, than the |
55 |
manufacturers EDID which is primarily contains other than colorspace and Gamma |
56 |
data. |
57 |
|
58 |
|
59 |
> Maybe I'm mistaken and KDE is reading what it needs at startup from those |
60 |
> Files. I'll try moving them and see what happens. |
61 |
> |
62 |
> > With the monitors sorted as best as I could adjust them manually I loaded |
63 |
> > the icc files with Kolor-manager. I could not see any change in the |
64 |
> > colors displayed by the monitors. They are both wide gamut monitors, so |
65 |
> > perhaps the RGB changes were within the narrower RGB spectrum and that's |
66 |
> > why I did not notice a difference - not to mention that my eyes are not |
67 |
> > they used to be. :p |
68 |
> > |
69 |
> > Having done all this, I revisited ImageMagick. I ran identify -verbose |
70 |
> > and discovered that the original jpg image did not have an embedded icc |
71 |
> > profile. So I reran the command specifying a cmyk profile for the input |
72 |
> > file and an sRGB for the output file. The result is now satisfactory |
73 |
> > and comparable on all operating systems. |
74 |
> > |
75 |
> > I am still a bit unclear if on non-KDE dekstops xserver will pick up any |
76 |
> > icc files for the monitor from ~/.local/share/color/icc and load them at |
77 |
> > start up all on its own, or if any additional software is necessary to |
78 |
> > achieve this. |
79 |
> |
80 |
> Yes, I'm also unclear on this. |
81 |
|
82 |
-- |
83 |
Regards, |
84 |
Mick |