Home › Forums › Help and Support › Correction matrix not working properly
- This topic has 6 replies, 2 voices, and was last updated 3 years, 7 months ago by
Mark Appleton.
-
AuthorPosts
-
2022-12-25 at 9:59 #38169
I have an i1Pro2 and an i1 Display Pro, and I am trying to create a correction for the latter using the former as a reference. I follow the procedure, take my two sets of readings (with the i1Pro2 as the reference meter), and get the matrix shown below. However, when I measure the white point with the i1 Display Pro with the correction in force, the result is way off what the i1Pro2 sees (pics).
Curious, I used HCFR to generate a correction matrix and got something completely different, that corrected the meters to within 0.1 dE of each other on a simultaneous RGBW read. I tried editing an existing .ccmx in DispCAL’s directory to match it – the correction info page shows the same numbers – but it still gives measurements that are way off.
Does anybody have any idea what’s going on here? I got the i1 Display Pro for its superior speed and dark level performance, but if I can’t correct it with the i1Pro2, it’s kind of pointless!
Thanks.
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.2022-12-25 at 10:32 #38174I have also tried a spectral correction from the i1Pro2 – while it’s closer, it’s still not good enough.
2022-12-26 at 9:33 #38179Something else I noticed while profiling: the white point co-ordinates from the Pro 2 don’t match.
When I measure the whitepoint with the Pro 2 during a calibration, I get within 0.1 dE of D65 (first pic), but the white point while profiling the i1 Display Pro is way off (second pic); when the correction is applied to the i1 Display Pro, the white point does match the erroneous whitepoint of the Pro 2 (third pic).
Why is the Pro 2 getting the whitepoint wrong while correcting the Display Pro?!
Attachments:
You must be logged in to view attached files.2022-12-27 at 12:09 #38186Update – I have discovered something of a workaround, though I have no idea why it works: generate a .ti3 file from a WRGB patch measurement from each meter seperately, then use the correction menu to generate a matrix from those.
Second meter now measuring bang on D65 with the new matrix.
2022-12-27 at 12:25 #38187Looks like you are using CIE 2012 2 degree on one and default 1931 2 degree on the other.
2022-12-27 at 12:52 #38192Ah – just spotted that in the Pro 2 part of the menu… that would be a complete dingbat of a mistake – will check next time I start the application.
Would separate, manual .ti3 measures bypass this error? Would explain why it worked!
2022-12-27 at 13:10 #38195Looks like you are using CIE 2012 2 degree on one and default 1931 2 degree on the other.
Yup – colour me daft (pun intended). Just set the observer to 1931/2 on the Pro 2 and got exactly what I wanted.
Good catch, sir!
-
AuthorPosts