- This topic has 13 replies, 3 voices, and was last updated 1 year, 7 months ago by
.
-
Posts
-
Good morning, for a few days I’ve been trying to calibrate my new Dell U3223QE monitor with the SpyderX Pro. With both the Datacolor program and DisplayCal I noticed that the Dci-P3 coverage is lower than the declared one (98%). I read another post but it is related to Linux. I have Windows 11 Home 24H2 with a clean installation. To test I loaded the Dell Dci-P3 profile, activated the 10bit color from the Rtx3060 video card and calibrated the monitor with low brightness in a dark room. Am I doing something wrong? Do you have any advice, please 🙂 Thanks
Best regards. Stefano 🙂SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.don’t care about %, where are the primaries. Take a look ok resulting profile CIE xy or CIE a*b* vs sRGB. Do the same with factory profile.
Also to use that monitor properly as a widege gamut for color manage envireoments use Custom Color OSD mode.SpyderX should use “wide LED” mode. It’s not very accurate but that’s all you have.
DCI-P3 factory mode likely will aim for DCI-P3 white and it’s very unlikely that you want that. So it’s easyer to use native gamut in custom color and aim to D65
Thanks Vincent, to calibrate it I used the OSD custom colors mode with the three colors adjustment. HDR was disabled (should I enable it?) and the profile loaded in Windows was the DCI-P3 from Dell… I understood little of what you wrote due to my little experience with color profiles and adjustments. I will look for info on the various parameters you indicated. Thanks 🙂
With your custom profile loaded (the one made by DisplayCAL) run DisplayCAL-profile-info.exe
Check where are placed RGB primaries. 100% srGB 108% volume looks very sRGB to me. Maybe you are running some layer over basic OS, AMD driver, whatever you did IDNK.
Then do the same with factory profile which stores EDID primaries.Hi Vincent, I’ll try to do as you say, but unfortunately due to my lack of experience I must first understand what the parameters you mentioned are. Thank you very much for your help, we’ll update as soon as I’ve done the tests you say. Bye 🙂
Hi Vincent, I tried to reset everything, including DisplayCal and Nvidia parameters. I did the calibration with DisplayCal having loaded the Dell “standard” profile into the monitor, in the three RGB color adjustment window I had a predominance of blue but I didn’t touch anything, I did the calibration, surprise, the Dci-P3 coverage is now at 96%. I still have doubts about the fact that I didn’t touch the three colors, if I do it from the monitor’s OSD the “Standard” profile goes away and the Dci-P3 coverage drops again… which is the most realistic profile? the one done with or without the RGB color adjustment? Thanks 🙂 Bye. Stefano
If you set a target whitepoint different from natibe (D65 for example) if you do not correct RGB gains DisplayCAL(ArgyllCMS) will do it for you limiting 1 or 2 channel max output on VCGT. Inspect calibration curves and you’ll see. Maybe you over correct some OSD settings in custom color mode.
I changed the RGB colors to center them in DisplayCal before starting the calibration. I’m doing some more testing in the meantime. Thanks 🙂
I have an i1Display Pro Plus.
My monitor is a Philips 27E1N8900 OLED. Graphics card is an RTX 4090.
Under 24H2, monitor profiling seems to be broken. It’s as if the monitor isn’t detected, and defaults to sRGB. True for DisplayCal/Argyll CMS, and Calibrites Profiler. The Profile Info feature of DisplayCal shows it clearly.
MS support told me that it’s a known bug. Today’s 26100.2161 update didn’t affect it.
Thanks, now I understand some things. Anyway I stopped the tests because I have to get the replacement monitor because mine has a hallucinating ips glow! Thanks
I have an i1Display Pro Plus.
My monitor is a Philips 27E1N8900 OLED. Graphics card is an RTX 4090.
Under 24H2, monitor profiling seems to be broken. It’s as if the monitor isn’t detected, and defaults to sRGB. True for DisplayCal/Argyll CMS, and Calibrites Profiler. The Profile Info feature of DisplayCal shows it clearly.
MS support told me that it’s a known bug. Today’s 26100.2161 update didn’t affect it.
Did you do a MS Paint test? I mean, monitor+windows keeps simulating sRGB all the time? a 255 green a 255 red patches in native gamut OSD preset look widegamut or sRGB in MS PAINT?
Do you tried to boot from a Linux USB pendrive with no color management or HDR support? (maybe Linux Mate or elementary os): Does it look widegamut on raw R 255 or G 255?
This would point to te culprit, if it is a W11 issue related to sRGB simulation when HDR mode is active on WIndows, or if it is a monitor firmware issue.When any of you see this kind of problems try to isolate the culprit this way, testing monitor behavior with the lower layer number you can. You can use a rpi pattern generator too.
Nope.
And I probably won’t. try any of those things, even the ones that aren’t beyond me.
The issue did not exist on Win 11Â version 23H2. It’s an acknowledged bug in 24H2. I suppose that MSÂ verifying the bug could have been just jollying me along, but I hope not.
A couple of minor details:
The display is not in HDR mode.
The display is set to 30 bit color. I have a 30 bit test gradient (not generated by me) that displays properly.
