1 |
On Sunday 27 Sep 2015 11:50:54 Peter Humphrey wrote: |
2 |
> On Sunday 27 September 2015 10:47:51 Mick wrote: |
3 |
> > On Sunday 27 Sep 2015 09:58:43 Peter Humphrey wrote: |
4 |
> > > I do have the two .icc files in .local/share/icc: |
5 |
> > > |
6 |
> > > $ ls -l .local/share/icc |
7 |
> > > total 28K |
8 |
> > > -rw-r--r-- 1 prh prh 1.2K Sep 9 16:51 |
9 |
> > > edid-fbec4f9c1804ea718b6e1b585fc234ad.icc -rw-rw-r-- 1 prh prh 21K Sep |
10 |
> > > 10 10:41 GCM - Samsung - SMS27A350H - unknown (2015-09-10) |
11 |
> > > [04-58-44].icc |
12 |
> > > |
13 |
> > > /usr/bin/file shows them both as "ColorSync ICC Profile". I don't know |
14 |
> > > why there are two, nor why they have such different sizes. |
15 |
> > |
16 |
> > I'm guessing that the 'edid-fbec4f9c1804ea718b6e1b585fc234ad.icc' was |
17 |
> > extracted from your monitor's EEPROM chip through the i2c bus and saved |
18 |
> > on disk by the LiveCD you ran, but the 'GCM - Samsung - SMS27A350H - |
19 |
> > unknown (2015-09-10) [04-58-44].icc' was generated by the colorimeter |
20 |
> > during your calibration exercise. |
21 |
> > |
22 |
> > I'm also guessing that the smaller size of the first file is because your |
23 |
> > monitor's EDID is of an earlier version, e.g. EDID-v1.1 or some such, |
24 |
> > which used to only contain a 128-byte data structure. I seem to recall |
25 |
> > that very early EDID versions didn't even contain colospace and Gamma |
26 |
> > data, but may be wrong. |
27 |
> |
28 |
> I've just visited the Taxi site you mentioned to see what's there for my |
29 |
> monitor. Nothing! So I tried uploading my ColorHug data. The page asked for |
30 |
> a metadata file and a profile data file, from which I supposed that my |
31 |
> smaller file is metadata about the content of the larger one. But when I |
32 |
> tried to upload the two files on that assumption I got a server error. |
33 |
> Same when I tried them the other way round. |
34 |
> |
35 |
> Looking at the larger file with less, I find eight lines of binary data at |
36 |
> the head followed by 400-odd lines of legible textual data. Interesting |
37 |
> stuff, though of course I don't know what to do with it myself. |
38 |
> |
39 |
> > These are [Mick's] 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 |
50 |
> |
51 |
> XYZLUT+MTX.icc |
52 |
> |
53 |
> > The first two are from the monitors' EDID content, the latter are the |
54 |
> > profiles I downloaded from the Taxi DB. Some of these contributors' |
55 |
> > profiles were created with spyder or other expensive colorimeters, so I |
56 |
> > am surmising that they capture more data points and contain more |
57 |
> > information, than the manufacturers EDID which is primarily contains |
58 |
> > other than colorspace and Gamma data. |
59 |
> |
60 |
> Lucky you! As I said, my monitor hasn't made it into the database yet. And |
61 |
> it seems I can't contribute to it either. |
62 |
|
63 |
|
64 |
Contributing is more involved than simply downloading a profile. I think you |
65 |
have to use the TaxiDB API: |
66 |
|
67 |
http://sourceforge.net/p/openicc/taxi/ci/master/tree/docs/api_doc.txt |
68 |
|
69 |
I you are interested then you can contact the OpenICC project to ask for |
70 |
details: |
71 |
|
72 |
http://www.freedesktop.org/wiki/OpenIcc/ |
73 |
|
74 |
-- |
75 |
Regards, |
76 |
Mick |