Calibration Issues with BenQ EW3270U and AOC 24G4X Monitors

[Antonio Ramos]

Hi everyone,

I’ve followed Florian Höch’s step-by-step instructions on the 3D LUT creation workflow for Resolve (GUI) to calibrate my monitors for Rec. 709 gamma 2.4. I’m using a SpyderX Elite and the LCD PFS Phosphor WLED, RGB LED preset, as both of my monitors are W-LED with large gamut coverage. Here are the details of my setup:

Monitors:

Monitor 1: BenQ EW3270U (Contrast: 3908.1:1 after calibration)
Monitor 2: AOC 24G4X (Contrast: 1101:1 after calibration)
Both calibration reports are attached for reference. And also a visual representation of my issue.

Issue: Perceptually, monitor 1 (BenQ EW3270U) looks way too washed out compared to monitor 2 (AOC 24G4X). Despite having a higher contrast ratio, the colors, especially blues and whites, on monitor 2 seem much more magenta than on monitor 1. Surprisingly, the Delta E on monitor 2 is better than on monitor 1, but I don’t believe this is the main issue.

The significant difference I noticed in the reports is in the black target levels. Could this be causing the problem? Should I trust the higher contrast ratio of monitor 1 and consider it more accurate, or should I try to match the black target levels to those of monitor 2, which looks more contrasty?

Here are the black target level details from the reports:

Monitor 1 (BenQ EW3270U):

Media black point

Illuminant-relative XYZ 0.0412 0.0504 0.0626 (xy 0.2673 0.3267)

Illuminant-relative CCT 9480K

ΔE 2000 to daylight locus 20.22

ΔE 2000 to blackbody locus 21.31

Monitor 2 (AOC 24G4X):

Media black point

Illuminant-relative XYZ 0.0870 0.0916 0.0992 (xy 0.3132 0.3297)

Illuminant-relative CCT 6472K

ΔE 2000 to daylight locus 0.06

ΔE 2000 to blackbody locus 4.70

I would appreciate any insights or advice on how to resolve this issue. Should I adjust the calibration settings to better match the black target levels, or is there another aspect I might be overlooking?

Thank you in advance for your help!

 

Attachments:

You must be logged in to view attached files.

SpyderX Pro on Amazon  
Disclosure: As an Amazon Associate I earn from qualifying purchases.

[Ben]

If its just perception both should have the same contrast ratio.   No way to increase contrast with software since it can not lower RGB 0,0,0 .    Set both to the same black level of monitor 2 and a white level both can achieve.    If you run a native black level and white level they will be different and always look different.

One point is monitor 1 is at 9400k temperature so has a lot of adjusting to do.  Warm is the recommend color temp for D65.   For a professional to have different monitors except for testing what it looks like on native users screens is strange to me.   I’m not a professional so I would not know.

Another point is Spyders are not good.  Spyder X elite is good and better than older ones but Xrite has better color meter corrections to match the monitor.   I am a Colorchecker display pro user and do not know Spyders.   Almost got a Spyder X elite but glad I got a Xrite colorimeter.

[Ben]

Blue is off on the 2nd one.   Could check it native to see if it matches blue color ramps all the way to 100%.   This chart shows is delta E  2.28 off.  Its 3 L to high which is less than 13 RGB levels on your screen going by block 3 which 13,13,13.   Its better than mine Vizio v series but way worse than the 1st monitor.    I would go for delta E under 1.   The blue hue is off little but not sure it will fix it.    #30 is .09 over C.  I think C is saturation and saturation control brightness so lower blue saturation 1 or more or use a ramp to set saturation.    HCFR is good for checking saturation.

Thanks for the picture it does help to see what the problem is.

• This reply was modified 1 month, 1 week ago by Ben.

[Vincent]

@Antonio, you are verifiying behavior color managed… we don’t know how display actually behaves.
As explained many times, before attepting a LUT3D or color managed verification, just verify if display profile matches display bahevior and look for anomalies in measured a*b* on greys.
Windows desktop is not color managed and your diaplay actual gamma is going to show there

Second, visual mismatch in white can happen because inaccurate measurement device or correctuion (it’s an spyder x… so it is possible) or because your vision not exactly the same as std observer. THis is corrected choosing the whistest display as reference and then using white point coordtinates -> visual white point editor (3 circles icon) and tehn match visually.
A display visually matched cannot use absolute colorimetric intent in a LUT3D against an std profile like sRGB / Rec709. Use relative whitepoint,

[Author]

Posts