- This topic has 11 replies, 2 voices, and was last updated 2 years, 10 months ago by
.
-
Posts
-
I got a PD2700U as second monitor yesterday, and decided to calibrate both my screens since I needed to calibrate the new monitor anyways. I’ve got an Eizo CG248-4K which I use with a BlackMagic Ultrastudio Monitor 3G. I’ve calibrated that following this video from Eizo. Did the verification through Resolve, results look great.
Then I calibrated the PD2700U, with the settings I’ve attached below. I’m not 100% sure if these are right, so if this is the problem, please correct me where I was wrong! After saving the 3D LUT, I went to Resolve and set this .cube file in the Color Management tab as ‘Color viewer lookup table’. Started a new verification through Resolve to check if the values were good, and these also looked great.
After doing all of this and being reassured by the measurement reports that the calibrations went well, visually the screens don’t match. The PD2700U looks a bit darker and more purple than the CG248-4K.
I’m not sure what to do now; I guess I should trust the CG248-4K, but since both reports state the monitors are calibrated correctly I don’t know which monitor to trust.
Could someone help me with this? Also, let’s say I should trust the CG248-4K, what’s the best way to try and match the PD2700U to the CG248-4K?
Thanks in advance for reading and helping! 🙂
Assuming that those CCSS are correct, it may be your visual system not matching CIE 1931 2 degree when you see different SPDs.
Choose the whiter one as reference, whatever it is, then visual match th other and for that 2nd one make LUT3D relative colorimetric (an alt take is to use as source profile Rec709 with tha WP coordinates of the visually matched white)
Also the grey range in the Eizo LUT3D is unusually high, its very unlikely that thi is present on monitor, so you may have done something wrong.
A last tip… if you are going to make a LUT3D and use only it through that LUT3D in Resolve, it is pointless to force the PD far away from native gamma. Let the LUT3D do it.Hi Vincent,
Thank you so much for your reply!
I’m quite new to DisplayCAL, so could you maybe explain how I’d go about to do the visual matching and making a LUT3D relative colorimetric? Would I do the visual matching with the on-screen controls? Also, visually the PD2700U looks a bit too purple and the Eizo looks a bit too green; I was hoping that the I1 DisplayPro could give me a technical analysis which one is closer to the white point, but is the only way of knowing this by trusting your eyes?
About the grey range on the Eizo, could this be because in the 3D LUT panel in DisplayCAL I selected the “TV 16-235” in and output encoding, as shown in the video? I just saw another tutorial for two different Eizo screens, where they used the full 0-255 range.
In your last tip, what exactly do you mean with “pushing it far away from native gamma”? I can select multiple gamma’s with the on-screen controls, and for the calibration I used the ‘Gamma 2.4’ setting.
Sorry if these are stupid questions, but I’m feeling overloaded by all the information online.
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Hi Vincent,
Thank you so much for your reply!
I’m quite new to DisplayCAL, so could you maybe explain how I’d go about to do the visual matching and making a LUT3D relative colorimetric? Would I do the visual matching with the on-screen controls?
Let’s say, as a wroking hypothesis that CG and PD are right, i1d3 colorimeter is right, CG looks white and you want to correct the mismatch IN YOUR EYES for PD.
-Set numerical match to D65 in OSD, like you did, cancel calibration.
-in calibration tab, whitepoint choose chromaticiy coordinates, then visual whitepoint editor (1st icon). It will open a popup, manually tweak that windo control till you get a match. When you get a match, measure. THen DisplayCAL will calibrate to that white.-when making LUT3D choose relatibe colorimetric as rendering intent, to preserve the visuall matched white in LUT3D for teh Benq PD.
Al alternative option is to bake an alternative Rec709 profile with that alt whitepoint and use abs colorimetric, but it may be easier for you to just use rel colorimetric.That’a all
Also, visually the PD2700U looks a bit too purple and the Eizo looks a bit too green; I was hoping that the I1 DisplayPro could give me a technical analysis which one is closer to the white point, but is the only way of knowing this by trusting your eyes?
Is CG248 a WLED PFS? Check Spectral power distribution plot, (i) icon.
ColorNavigator7 does not have colorimeter corrections fro WLED PFS and i1d3 colorimeter, it is using:
-built in colorimeter
-or generic matrix for a ganwric i1d3 and CG248
-or GB-LED EDR for i1d3 (no compensation)
You can use Stuart Pointon CS2731 corrected EDR to patch COlor Navigator, several threads about thisAnyway, when you made LUT3D for Eizo that LUT3D has a color correction from whatever your i1d3 measured in displaycal with custom 3nm CCSS and D65 (rec 709). Taht WP correction may suffer from whetever rounding errors present in Resolve LUT3D.
You can use post calibration fine tune of whitepoint in Color Navigator, Read teh manual, os close to DIsplayCAl’s. If you choose a visually matched wgite in Color Navgator, then to preserve that visually matched white in LUT3D you’ll have to chose rel colorimetric too.
About the grey range on the Eizo, could this be because in the 3D LUT panel in DisplayCAL I selected the “TV 16-235” in and output encoding, as shown in the video? I just saw another tutorial for two different Eizo screens, where they used the full 0-255 range.
IDNK what you did. It’s easier to test grey range from Color navgiator with no LUT3D applied: plugged to common GPU in your PC or through resolve. Test both.
In your last tip, what exactly do you mean with “pushing it far away from native gamma”? I can select multiple gamma’s with the on-screen controls, and for the calibration I used the ‘Gamma 2.4’ setting.
Is that OSD setting close to 2.4 target ? Measure it.
Let’s say, as a wroking hypothesis that CG and PD are right, i1d3 colorimeter is right, CG looks white and you want to correct the mismatch IN YOUR EYES for PD.
-Set numerical match to D65 in OSD, like you did, cancel calibration.
-in calibration tab, whitepoint choose chromaticiy coordinates, then visual whitepoint editor (1st icon). It will open a popup, manually tweak that windo control till you get a match. When you get a match, measure. THen DisplayCAL will calibrate to that white.-when making LUT3D choose relatibe colorimetric as rendering intent, to preserve the visuall matched white in LUT3D for teh Benq PD.
Al alternative option is to bake an alternative Rec709 profile with that alt whitepoint and use abs colorimetric, but it may be easier for you to just use rel colorimetric.Thanks! I’ll try those steps after making sure the Eizo is calibrated correctly.
Is CG248 a WLED PFS?
On Display Specifications I found that it uses a LG LM238WR2-SLC1 panel, which is a GB-r LED (WLED) display.
Check Spectral power distribution plot, (i) icon.
I can’t find the Spectral power distribution plot in this screen, I also found another thread on here where you explain to someone it can also be created in the ArgyllCMS folder with: ‘specplot.exe PATH_to_CCSS’
You can use Stuart Pointon CS2731 corrected EDR to patch COlor Navigator, several threads about this
I googled this and looked through the forums but can’t seem to find these, could you maybe link those?
You can use post calibration fine tune of whitepoint in Color Navigator, Read teh manual, os close to DIsplayCAl’s. If you choose a visually matched wgite in Color Navgator, then to preserve that visually matched white in LUT3D you’ll have to chose rel colorimetric too.
I’m very sorry but I’m losing you here; So from what you’ve said before, the problem might be that Colornavigator doesn’t use the custom 3nm CCSS that I’ve used in DisplayCAL, but since I apply the whole DisplayCAL calibration through Resolve, which is my end goal, why does ColorNavigator come back in here again?
It’s easier to test grey range from Color navgiator with no LUT3D applied: plugged to common GPU in your PC or through resolve. Test both.
and;
Is that OSD setting close to 2.4 target ? Measure it.
So sorry, but could you explain which settings I should select in DisplayCAL to do these correctly? Do I disable everything from DisplayCAL and in ColorNavigator?
Also, I might’ve made a mistake by not letting the Eizo calibrate and therefore not having the changes I made prior to doing DisplayCAL’s calibration being applied. I followed every step again from this video, but now also made sure the changes I made before doing anything in DisplayCAL were applied. Also I changed the ‘TV 16-235’ in the 3DLUT tab back to ‘Full 0-255’ since in the comments below he mentions the only display that needs to put ‘TV 16-235’ there is specifically the CG247X display. I’ve uploaded the measurement report in the attachments.
I’m very sorry for not understanding what you’re saying. I really want to start to understand more about the whole calibration thing but I feel like there’s so much stuff throw at me and I can’t keep up, and even when the measurement reports seem great I’m still not where I want to be.
You are mixing things I wrote for teh Benq PD with the CG…
Anyway…
LCD GB-r-LED IPS (Eizo CG248 (i1 Pro 2)) <Eizo CG248 (i1 Pro 2).ccss>
Plot it and see if it looks like GB-LED or like a WLED PFS (3nm or 10nm, since it looks like a community one)
Regarding CG calibration,
why does ColorNavigator come back in here again?
I wrote it earlier:
Anyway, when you made LUT3D for Eizo that LUT3D has a color correction from whatever your i1d3 measured in displaycal with custom 3nm CCSS and D65 (rec 709). Taht WP correction may suffer from whetever rounding errors present in Resolve LUT3D.
So the goal is to minimize white point correction in LUT3D for the reference display.
Also visual white point editor / matching is not related only to your i1d3 accucary using a proper EDR/CCSS but to your visual system not matching CIE 1931 2 degree
I plotted the one I used and made a screenshot which I put in the attachments below.
I also plotted two other corrections that I found online for the same display and they are quite different (see attachment, left one being the one I used for my calibration). How do I choose the right one?
To be sure that I’m understanding what you’re saying; Because the Eizo calibrated its white point using Colornavigator before doing the DisplayCAL calibration, I should minimize DisplayCAL’s white point correction by selecting the correct 3nm CCSS, otherwise it will apply these “misreadings” to the correction?
You were right, it was a GB-LED (CG248 was older than I thought!).
Choose “no compensation” in Color Navigatior preferences (regarding colorieter correction) and it will use GB-LED EDR (RG phosphor) for i1d3 colorimeter. Do not patch Color Navigator with CS2731 correction.Thanks for that, I changed it to ‘no compensation’ in CN now!
After doing that I started a new calibration, and tried out the community EDR versus the ‘standard’ DisplayCAL GB-r-LED / RG-Phosphor LED family EDR. When doing the whitepoint measurement I got the following results (see attachments). I also added a screenshot of both plots, the 3.3nm community EDR and the ‘standard’ DisplayCAL 1nm plot.
So it seems the whitepoint changes less using the ‘standard’ DisplayCAL EDR, should I opt for that one instead of the community one, even though it is not specifically made for this display?
Did two calibrations now, one with the GB-r-LED / RG-Phosphor LED family EDR and one with the community EDR. The measurement report of DisplayCAL’s GB-r-LED / RG-Phosphor LED family EDR calibration comes out a tiny bit better, although I can’t see any visual differences switching between the two calibrations in ColorNavigator.
Do these measurement reports seem correct?
Thanks for that, I changed it to ‘no compensation’ in CN now!
After doing that I started a new calibration, and tried out the community EDR versus the ‘standard’ DisplayCAL GB-r-LED / RG-Phosphor LED family EDR. When doing the whitepoint measurement I got the following results (see attachments). I also added a screenshot of both plots, the 3.3nm community EDR and the ‘standard’ DisplayCAL 1nm plot.
So it seems the whitepoint changes less using the ‘standard’ DisplayCAL EDR, should I opt for that one instead of the community one, even though it is not specifically made for this display?
They’re the same
Did two calibrations now, one with the GB-r-LED / RG-Phosphor LED family EDR and one with the community EDR. The measurement report of DisplayCAL’s GB-r-LED / RG-Phosphor LED family EDR calibration comes out a tiny bit better, although I can’t see any visual differences switching between the two calibrations in ColorNavigator.
Do these measurement reports seem correct?
Grey range is low as expected for a Coloredge. Both samples. IDNK what you did in previous Resolve calibration ( #138574) but now seems better. Anyway… you did not check Color Navigator results without LUT3D to find which step was adding it.
