Eizo CS2740 calibration questions

[JohnD]

Yeah, I know that wasn’t a particularly scientific test I did – more an anecdotal one. I don’t unfortunately have access to the JETI anymore.

I do, however, have a ccmx I made for each monitor and I also have a set of verification readings I took on the factory calibrated native gamut profile using the JETI, so the best I can do is compare the JETI readings I saved against the i1d3 CCSS and the CCMX corrected readings – see attached.

I added a column on the CCSS and CCMX readings that show the deltaE with the JETI readings, colour coded for red/green to show which of the two has a lower deltaE with respect to the JETI.

The CCSS seems a little more accurate on the greys and the CCMX a little more accurate on the colours, but both are well with in acceptable tolerances. The CCSS isn’t actually nearly as bad as I thought initially.

The big difference, and seemingly the only significant departure, is on the whitepoint and luminance. The CCMX is spot on but the CCSS corrected readings are way off.  The CCSS under-reads the luminance by 7cdm/2.

I get a good result using color navigator by using an EDR created from my CCSS files, specifying a target whitepoint of 6750K (which is what the CCSS correction reads a whitepoint I know to be 6500K from the JETI) and adjusting the luminance target by -7 to take into account the luminance under-read.

If I then verify that calibration with Displaycal using the CCMX correction and the i1d3, it’s spot on (except of course for the profile whitepoint not matching the measured whitepoint and the profile luminance not matching the measured luminance).  It’s perfectly usable and way better than the result I was getting using the CG319X EDR.

Attachments:

You must be logged in to view attached files.

Calibrite Display Pro HL on Amazon  
Disclosure: As an Amazon Associate I earn from qualifying purchases.

[Vincent]

That i1d3 seems fine. A NIST certified i1Pro2 using Xrite SDK (not Argyll high res mode) will have bigger error on a WLED PFS

[JohnD]

A NIST certified i1Pro2 using Xrite SDK (not Argyll high res mode) will have bigger error on a WLED PFS

Not that I didn’t believe you, but I was curious to see how much worse, so I of course tried.

Even using Argyll hi res mode, my i1Pro2 has a 3.73 dE (!) on the whitepoint to the JETI’s reading. Luminance reads correctly.

Average dE with the JETI readings of 0.13 in the greys and 0.29 in colours.  Slightly more accurate on the greys than the ccss/ccmx corrected i1d3, less accurate on the colours than both

[Vincent]

There is a thread on LGG about “CCSS corrected vs reference device”  = error between filters and frimware data about the filters with 3 sample i1d3 measuring one of those narrow spikes WLED PFS. If I remember it properly on of the i1d3 had 3dE on whitepoint with generic HP Z24x G2 CCSS, WLED PFS adobeRGB green, P3 red, (and white point should be the most noticeable error), that’s why I said that CCSS corrected your i1d3 is working perfectly and on spec.
The thread was about an CS2731 or a CG319X. Stuart shared its modified EDRs for CN on one of these threads. You can do the same with your CCSS with CCSS2EDR app. Latest version was a fork by aron7wol on AVS Forum.

Regarding i1Pro2, these narrow spike backlights and laser projectors are its weakest point.

Edit but for most of them that i1Pro2 error is moved towards yellow in a ~45 degree displacement so it is usually on daylight curve if you aim for D65 so it is not very noticeable, i1Pro2 just see it warmer. I’ll try to find one reading for a WLED PFS, I had stored one.

• This reply was modified 2 years, 8 months ago by Vincent.

[Vincent]

CS2731 + i1d3 + Stuart Pointon EDR (1nm) + ColorNavigator7. Whitepoint after calibration was on spot (measured by i1d3 CCSS corrected), 10xx:1 contrast

Then my saved file says

i1Pro 3nm
13:10:07,790 Black level = 0.1093 cd/m^2
13:10:07,790 50% level = 27.06 cd/m^2
13:10:07,790 White level = 124.37 cd/m^2
13:10:07,790 Aprox. gamma = 2.20
13:10:07,790 Contrast ratio = 1138:1
13:10:07,790 White chromaticity coordinates 0.3120, 0.3284
13:10:07,790 White Correlated Color Temperature = 6546K, DE 2K to locus = 4.7
13:10:07,790 White Correlated Daylight Temperature = 6548K, DE 2K to locus = 0.0
13:10:07,790 White Visual Color Temperature = 6376K, DE 2K to locus = 4.5
13:10:07,790 White Visual Daylight Temperature = 6548K, DE 2K to locus = 0.0

13:13:24,169 Black level = 0.1110 cd/m^2
13:13:24,169 50% level = 27.11 cd/m^2
13:13:24,169 White level = 124.40 cd/m^2
13:13:24,169 Aprox. gamma = 2.20
13:13:24,170 Contrast ratio = 1121:1
13:13:24,170 White chromaticity coordinates 0.3120, 0.3284
13:13:24,170 White Correlated Color Temperature = 6545K, DE 2K to locus = 4.6
13:13:24,170 White Correlated Daylight Temperature = 6547K, DE 2K to locus = 0.0
13:13:24,170 White Visual Color Temperature = 6376K, DE 2K to locus = 4.5
13:13:24,170 White Visual Daylight Temperature = 6548K, DE 2K to locus = 0.0

i1Pro 10nm
13:12:01,876 Black level = 0.1139 cd/m^2
13:12:01,876 50% level = 27.12 cd/m^2
13:12:01,876 White level = 124.57 cd/m^2
13:12:01,876 Aprox. gamma = 2.20
13:12:01,876 Contrast ratio = 1094:1
13:12:01,876 White chromaticity coordinates 0.3136, 0.3296
13:12:01,876 White Correlated Color Temperature = 6451K, DE 2K to locus = 4.4
13:12:01,877 White Correlated Daylight Temperature = 6453K, DE 2K to locus = 0.3
13:12:01,877 White Visual Color Temperature = 6297K, DE 2K to locus = 4.2
13:12:01,877 White Visual Daylight Temperature = 6465K, DE 2K to locus = 0.3

10nm had an xy 45 degree error (warm-cool) but not color tint (no error vs daylight curve). It also has an Y mismatch vs 120+-2 by i1d3, I do not find HTML report right now, CN7 target was 120cdm2

Where was located the error in your i1pro2, warm-cool axis or color tint (green-magenta) axis?

So if you have a max 1.7dE vs true reference using CCSS it’s OK.
A K10A would be faster of course, but your i1d3 seems to have very good match in filter behavior vs filter data in firmware so it is able to use CCSS without issue (distributed corrections without your own spectrophotometers) and the klein does not (maybe newer versions?). Stuart i1d3 samples showed higher error with  CCSS.

• This reply was modified 2 years, 8 months ago by Vincent.
• This reply was modified 2 years, 8 months ago by Vincent.

K10-A on Amazon  
Disclosure: As an Amazon Associate I earn from qualifying purchases.

[Vincent]

BTW: It had lower error than I remembered

[JohnD]

You can do the same with your CCSS with CCSS2EDR app

Sure, I have one already, just didn’t post it here as it’s not an allowed upload filetype.  Anyone who wants it can download it here: http://www.kz3.uk/downloads/RG_Phosphor_Family_25Jul12_CS2740.edr

As I mentioned in a previous message, I get a great result by calibrating for 6750K and taking -7 cdm/2 off my desired luminance. Then I end up with 6500K and whatever target luminance I’ve set + 7cmd/2. That may be specific to my i1d3, so mileage may vary.

Replace the file in C:\ProgramData\EIZO\Sensor\i1DisplayProEDR with this one, removing the _CS2740 part of the filename.

I used all 20 sets of readings from both monitors to create this EDR (a total of 80 readings), so it’s probably fairly robust given that it comes from two monitors and there are multiple readings for each monitor.

Where was located the error in your i1pro2, warm-cool axis or color tint (green-magenta) axis?

I think the screenshot I uploaded to this message should answer your question. Note that you can’t see the plot marker for the JETI as the CCMX one is directly on top of it, with exactly the same coordinates

Attachments:

You must be logged in to view attached files.

[JohnD]

Anyone who wants it can download it here:

Made a typo on that link, but just noticed I can upload zip files, so attached to this message as a zip

Attachments:

You must be logged in to view attached files.

[Vincent]

Thanks for sharing the EDR since a lot of users may not know how to run python apps like CCSS2EDR

[Author]

Posts