- This topic has 7 replies, 3 voices, and was last updated 1 month, 2 weeks ago by
.
-
Posts
-
Hello, I have two 1display pro colorimeters. I’ve been using one of them regularly for several years. I put the other colorimeter away in a drawer a few years ago because its USB cable had broken.
Yesterday, a friend of mine repaired the colorimeter with the broken cable. The idea is to have a spare colorimeter.
To check if the colorimeter was repaired correctly, I used Displaycal to generate a measurement report based on a calibration I had already performed with the colorimeter I usually use.
The measurement report was not successful; it indicated a deviation of 3 AE at the white point, I expected some differences, but not this noticeable. Obviously, if I run a measurement report with the same colorimeter I used for the calibration, the result is Ok.
So, to test it, I created a new target in Color Navigator 7 on a different slot using the same calibration parameters I’d used with my usual colorimeter, and I calibrated my monitor with the repaired colorimeter.
I noticed that with the new calibration performed using the repaired colorimeter, visually the monitor appears very green compared to the calibration created with the colorimeter I usually use. This effects colors, in color management application too.
With Displaycal I ran a measurement report on this profile, and numerically, this report is ok.So now I have two colorimeters of the same model that, when calibrating the same monitor with the same parameters, visually show a significant difference in the white point, but numerically, both are valid.
How is this possible? Which of the two colorimeters can I trust?
I am attaching three measurement reports: one with the calibration performed using the colorimeter I usually use but measured with the repaired colorimeter, and the other two with calibrations performed using each colorimeter.
I apologize for my English; I’m using an online translator.
The measurement report was not successful; it indicated a deviation of 3 AE at the white point, I expected some differences, but not this noticeable. Obviously, if I run a measurement report with the same colorimeter I used for the calibration, the result is Ok.
3dE is near the max inter instrument variation after CCSS+firmware spectral data. Look for Stuart Pointon measurements in “lift gamma gain”
So, to test it, I created a new target in Color Navigator 7 on a different slot using the same calibration parameters I’d used with my usual colorimeter, and I calibrated my monitor with the repaired colorimeter.
CN7 is using by default a matrix nonportable correction between i1d3.
CN7 has no WLED-PFS support by default, it uses GB-LED if configured to use EDR(“no compensation”)
It seems that there were some initial batchs of CS2420 with GB-LED but latter changed to WLED PFSI noticed that with the new calibration performed using the repaired colorimeter, visually the monitor appears very green compared to the calibration created with the colorimeter I usually use. This effects colors, in color management application too.
With Displaycal I ran a measurement report on this profile, and numerically, this report is ok.So now I have two colorimeters of the same model that, when calibrating the same monitor with the same parameters, visually show a significant difference in the white point, but numerically, both are valid.
How is this possible?
I do not know the extent of the damage on the repaired one, or if filters were damaged in the repair process.
Even if there was no damage there is an statistical variation in the accuracy of actual spectral response on the filters and the firmware spectral sensivity data.
Also overall correction depends on the accuracy of CCSS vs display SPD. Checking if your CS2420 is GB-LED or WLED PFS may help. Also using “no compensation” + EDR replacement )if needed, for WLED PFS variant, you can use CS2731 EDR)
Which of the two colorimeters can I trust?
non repaired seems the safe choice. Making a comparison vs 3nm high res readings of an i1Pro will help too.
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.I’m pretty sure my CS2420 has a GB-LED panel. Because, a while back, I tried the modified EDR, and after calibration, the white point was completely off, so I switched back to the default EDR.
In CN7, I always use “No compensation” in the Compensation method, because this way the white point looks very similar to my second monitor, a BenQ PD2500Q, which I calibrate with Displaycal.
If I set CN7 to “Color management”(Default settings), my Eizo seems to shift toward magenta compared to the BenQ.Regarding the colorimeter repair, to clean out any dust that had accumulated over time, I completely disassembled the colorimeter, including the part where the main lens and three small colored lenses are located, and cleaned everything with compressed air. Under the main lens there is a small plastic disc, which is supposed to diffuse the light. While cleaning, this small piece of plastic had popped out of its seat, and I had to put it back in.
Maybe I didn’t reinsert it correctly?
Afterward, I reassembled this part of the colorimeter.
Then my friend soldered the five wires of the USB cable to the connector on the board.Is there a risk that the colorimeter was damaged during these operations?
Another question I have is: if the colorimeter had been damaged during the repair, would it have been able to perform a calibration that is numerically correct in the Displaycal measurement report?
Because, after calibration, the DisplayCal measurement report appears to be numerically correct. Even though, visually, the monitor looks very green.In addition, there is also the fact that, if I use the repaired colorimeter to generate a measurement report for the profile created with the other colorimeter —the one I usually use— there is a deviation of 3 DE. Based on what you wrote, the deviation is too high.
Is there a risk that the colorimeter was damaged during these operations?
IDNK what you did.
Another question I have is: if the colorimeter had been damaged during the repair, would it have been able to perform a calibration that is numerically correct in the Displaycal measurement report?
Yes. Like a “shrinking ruler”, if you measure with a ruler and after a few years it becomes shorter by itself when you measure you’ll see an error.
But if you measure right now with the shortened rule (calibration) and do again after a few minutes (verification), they will measure the same but both measurements will be wrong (with an error) and the only way to know that there is an error is a reference device that it is known to be accurate or if the error is visually obvious (like a ruler -25% shorter, white point in our example)Because, after calibration, the DisplayCal measurement report appears to be numerically correct. Even though, visually, the monitor looks very green.
That is white point error.
Get a reference device (good advise before any reparing attempt, to make comparisons), measure (@3nm if Xrite’s), compare.
If it is off because the repair as long as error is stable in time can be corrected by a custom ccmx.
It could be possible to use the other i1d3 to generate a ccmx (no spectral data, just 4 WRGB 255 measurements) but remember to measure with no CCSS with the faulty one.Also this implies that you won’t be able to use the repaired one with ColorNavigator since they do not allow custom 3×3 XYZ to XYZ correction matrices (like CCMX). You may ask Eizo for that feature, several people asked, the more you press the higher the chances to get that into CN.
Based on what you wrote, the deviation is too high.
It’s close to the max inter instrument error for i1d3, so it’s expected, but in the low probable zone.
Anyway if the same display using “no compensation” in CN7 had no such green tint when measured with the old one years ago, and after repairment it does… it’s the repair.
i1d3 devices seems to age pretty well (mine is almost 14 yo) without drifting.Thanks, Vincent, for your help!
Yes. Like a “shrinking ruler”, if you measure with a ruler and after a few years it becomes shorter by itself when you measure you’ll see an error.
But if you measure right now with the shortened rule (calibration) and do again after a few minutes (verification), they will measure the same but both measurements will be wrong (with an error) and the only way to know that there is an error is a reference device that it is known to be accurate or if the error is visually obvious (like a ruler -25% shorter, white point in our example)Your example has helped me understand the situation better.
Anyway if the same display using “no compensation” in CN7 had no such green tint when measured with the old one years ago, and after repairment it does… it’s the repair.
Unfortunately, I don’t remember if that colorimeter showed a different white point before it was repaired. It’s been sitting in a drawer for several years.
If it is off because the repair as long as error is stable in time can be corrected by a custom ccmx.
It could be possible to use the other i1d3 to generate a ccmx (no spectral data, just 4 WRGB 255 measurements) but remember to measure with no CCSS with the faulty one.That sounds like a good compromise: this way, I could still use it with DisplayCal to calibrate another monitor that I use at my other home.
Get a reference device (good advise before any reparing attempt, to make comparisons), measure (@3nm if Xrite’s), compare.
It would be great to have a spectrophotometer like the i1 Pro, But it’s beyond my budget.
https://www.argyllcms.com/doc/ccxxmake.html
If ArgyllCMS does not allow you to use the i1d3+ccss (the good one) as reference, try to measure the 4 patch set on MS paint (non color managed) then write the TI3 file manually.
Another way is to port the 3×3 matrix from Calman. Compute 3×3 matrix using calman (manually enter measured coords if two i1d3 devices are rejected, maybe it works on “demo” version without measurement), copy them back to CCMX file (you can use other person CCMX as template)
So sad for the cleaning of the id3. Cleaning with compressed air not good for optics. I decided to not even clean mine after I dropped it. The factory software made me open and close the lens so many times instead of just leaving on the screen. A qtip but I worry about the cotton sticking. something with a microfiber cloth and alcohol might be ok on the eye one device. Do not use alcohol on Oled and maybe not good on a LCD. Distilled water works fine. And only when necessary.
