- This topic has 9 replies, 3 voices, and was last updated 1 year, 6 months ago by
.
-
Posts
-
Hello,
my monitor is a Quantum Dot Mini LED and I own a xrite i1display pro plus.
im having trouble calibrating an profiling the monitor because I am not achieving the marketed color gamuts for AdobeRGB and DCI-P3
So I was asking myself if the colorimeter is actually capable? Because Calibrite only advertises that the new HL generation would be able to calibrate Mini LED. So maybe that’s the fault? But I’m only trying to calibrate for SDR 120cd/m2, Gamma 2.2, so do I actually need a colorimeter that can handle 1000nits+?
Secondly I’m unsure which colorimeter correction to use. I’ve tried the only one for Quantum Dots (for Samsung I believe) and the only one I could download that’s specific to this monitor. Both only got me so far as in -5% of the specified color gamut coverage of the monitor. Same with a generic WLED profile
What could I try and change?
Also, as a more general question: ist it better to have a larger color gamut coverage and more DeltaE or a smaller coverage and less DeltaE (I’m talking about +/-0.5 max DeltaE)?
Im still new to the topic so bear with me
Thank you so much, any help is appreciated.
Calibrite Display Plus HL on Amazon Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.It does not really matter if color gamut is not 100 percent or Delta E is 0 . Just get both as close to right as possible. You probably would not tell the difference visually. You need to use visual content to see if it matters. Im not sure what correction is right or what to use for a mini led screen. I am not a expert.
Hello,
my monitor is a Quantum Dot Mini LED and I own a xrite i1display pro plus.
im having trouble calibrating an profiling the monitor because I am not achieving the marketed color gamuts for AdobeRGB and DCI-P3
So I was asking myself if the colorimeter is actually capable? Because Calibrite only advertises that the new HL generation would be able to calibrate Mini LED.
The old ones can too, at least up to their max nit spec.
Calibrite Profiler claim about “mini led” colorimeter correction is fake. It is likely using GB-LED colorimeter correction.
DisplayCAL i1d3 colorimeter correction bundle (import from tools menu) includes a “P3” QLED. DisplayCAL colormeter database also has some AdobeRGB +P3 gamut QLED, mostly Asus models:
https://colorimetercorrections.displaycal.net/
Remember to use CCSS files only (spectral) for corrections.So maybe that’s the fault?
no
But I’m only trying to calibrate for SDR 120cd/m2, Gamma 2.2, so do I actually need a colorimeter that can handle 1000nits+?
no, you just need a colorimeter that can be updated in a distributed way to new backlights. Yours is able to do that as any i1d3 colorimeter.
Remember that old colormunki display or new calibrite display SL are i1d3, but won’t work with Hardware calibration solutions from monitor vendors, like Eizo ColorNavigator, the ones from MSI, Benq… etc.
Buying the “cheap” i1d3 brothers instead of the current i1d3 pro version (HL) have these implications. They will work properly with DIsplayCAL/ArgyllCMS but you loose HW cal support if your current of future monitors had this feature.Secondly I’m unsure which colorimeter correction to use. I’ve tried the only one for Quantum Dots (for Samsung I believe) and the only one I could download that’s specific to this monitor.
Explained above.
Both only got me so far as in -5% of the specified color gamut coverage of the monitor.
Explained by Ben. Also agresive changes on RGB gains to get your desired whitepoints or toying with “contrast” osd settinsg may have a little impact on this.
Same with a generic WLED profile
That one is not a good correction for display
What could I try and change?
Also, as a more general question: ist it better to have a larger color gamut coverage and more DeltaE or a smaller coverage and less DeltaE (I’m talking about +/-0.5 max DeltaE)?
dE to what and in which conditions?
You could have a mean 0.5dE and get a pretty useless result, mostly because what colorimeter measured with the configuration you choose do not match actual color coordinates.Any complains about calibration results should attach an DisplayCAL HTML verification report, full file, not screenshots, becuse it is easy to spot typical user misconfigurations this way.
Im still new to the topic so bear with me
Thank you so much, any help is appreciated.
The old ones can too, at least up to their max nit spec.
Calibrite Profiler claim about “mini led” colorimeter correction is fake. It is likely using GB-LED colorimeter correction.
Thats interesting. Do you know more details about this? So this is basically “cheating”? That would leave people with incorrect calibrated and profiled displays without them knowing…. Are there any other corrections that might not be handled correctly?
DisplayCAL i1d3 colorimeter correction bundle (import from tools menu) includes a “P3” QLED. DisplayCAL colormeter database also has some AdobeRGB +P3 gamut QLED, mostly Asus models:
https://colorimetercorrections.displaycal.net/
Remember to use CCSS files only (spectral) for corrections.If I go Tools > Corrections > which entry do I have to chose? I have tried “Import colorimeter corrections from other display profiling software” and that gave me this (see screenshot). Unfortunately nothing with QLED and P3 or AdobeRGB. Or am I missing something?
If I check for online colorimeter corrections I find only one for this model (Philips 27B1u7903) but it has “WLED” in its name, so I don’t know if that would be any good.
If I look around for Asus models I fail to find any for QLED. Maybe you could point me to a specific one?
I found one for the Acer x32QFP which is also QuantumDot, MiniLED and IPS. But to be honest im fishing in the dark here.
no, you just need a colorimeter that can be updated in a distributed way to new backlights. Yours is able to do that as any i1d3 colorimeter.
Remember that old colormunki display or new calibrite display SL are i1d3, but won’t work with Hardware calibration solutions from monitor vendors, like Eizo ColorNavigator, the ones from MSI, Benq… etc.
Buying the “cheap” i1d3 brothers instead of the current i1d3 pro version (HL) have these implications. They will work properly with DIsplayCAL/ArgyllCMS but you loose HW cal support if your current of future monitors had this feature.Got it, thanks.
dE to what and in which conditions?
You could have a mean 0.5dE and get a pretty useless result, mostly because what colorimeter measured with the configuration you choose do not match actual color coordinates.Any complains about calibration results should attach an DisplayCAL HTML verification report, full file, not screenshots, becuse it is easy to spot typical user misconfigurations this way.
Im trying to calibrate and profile my monitor in its native gamut to D65, Gamma 2.2 and 120nits as a starting point in order to try to create a base line in my color managed apps (mostly Photoshop and LRC) in order to also use soft proofing for my online print service.
With Calibrate Profiler I get great DeltaE values but might have the wrong colorimeter correction (As MiniLED is only available for their HL line I can only chose between White LED, RGB LED, GB LED and PFS Phosphor. And I have no clue if any of those would be better than the other.
If I use DisplayCal I can chose among those in the screenshot. I haven’t testes the Acer one I mentioned yet, but might do. Still I feel like im missing A LOT of information here, and it seems google only gets me so far.
So any help here is greatly appreciated.
Big problem for me is, when I use Calibrite Profiler, I have to rely on their validation (like you said might be for the wrong corrections, so its useless) as I can’t run validation on <Current> as I have described in my other post. Also I can look at the color space coverage in the ICC profile in ColorSync on Mac. And here the profiles from Calibrites Profiler seem to cover the widest gamut. But if and how that is relevant IDNK.
So maybe if I could figure out which correction is the right one for me Id have a more solid starting point.
The old ones can too, at least up to their max nit spec.
Calibrite Profiler claim about “mini led” colorimeter correction is fake. It is likely using GB-LED colorimeter correction.
Thats interesting. Do you know more details about this? So this is basically “cheating”?
EDR is missing.
That would leave people with incorrect calibrated and profiled displays without them knowing…. Are there any other corrections that might not be handled correctly?
This usually means “potentially” wrong whitepoint. It depends on actual unit behavior (spectral sensivity data stored in firmware, search here on in AVS forum… to lengthly to explain it over and over gaian), some lesss some more.
Calibrute profiler has
White LED, for old LED sRGB only displays: laptops, Dell U2415… those ones
GB-LED, for Dells like U2713H (10+ years old) or older models like Eizo CS2730
RGB OLEDs, it may fit some Samsung OLEDs. This is not the same as QD or TV W-OLED
It also has CCFL, some specific proyectors… but used nowadsys those 3.That’s all
DisplayCAL i1d3 colorimeter correction bundle (import from tools menu) includes a “P3” QLED. DisplayCAL colormeter database also has some AdobeRGB +P3 gamut QLED, mostly Asus models:
https://colorimetercorrections.displaycal.net/
Remember to use CCSS files only (spectral) for corrections.If I go Tools > Corrections > which entry do I have to chose? I have tried “Import colorimeter corrections from other display profiling software” and that gave me this (see screenshot). Unfortunately nothing with QLED and P3 or AdobeRGB. Or am I missing something?
Samusng QLED TV Q9
If I check for online colorimeter corrections I find only one for this model (Philips 27B1u7903) but it has “WLED” in its name, so I don’t know if that would be any good.
If I look around for Asus models I fail to find any for QLED. Maybe you could point me to a specific one?
PA32UCG, that is a typical QLED with AdobeRGB green and P3 red.
dE to what and in which conditions?
You could have a mean 0.5dE and get a pretty useless result, mostly because what colorimeter measured with the configuration you choose do not match actual color coordinates.Any complains about calibration results should attach an DisplayCAL HTML verification report, full file, not screenshots, becuse it is easy to spot typical user misconfigurations this way.
Im trying to calibrate and profile my monitor in its native gamut to D65, Gamma 2.2 and 120nits as a starting point in order to try to create a base line in my color managed apps (mostly Photoshop and LRC) in order to also use soft proofing for my online print service.
With Calibrate Profiler I get great DeltaE values but might have the wrong colorimeter correction (As MiniLED is only available for their HL line I can only chose between White LED, RGB LED, GB LED and PFS Phosphor. And I have no clue if any of those would be better than the other.
If I use DisplayCal I can chose among those in the screenshot. I haven’t testes the Acer one I mentioned yet, but might do. Still I feel like im missing A LOT of information here, and it seems google only gets me so far.
So any help here is greatly appreciated.
Let’s asume that your QLED has AdobeRGB green and P3 red or close to that.
Import PA32UCG CCSS. Target white D65 (6500 daylight). calibartin speed medium or low (IDNK if you dislay is good or bad behaved, asume worst case).
Profile type single curve matrix (assume good idealized behavior after grey calibration) + blakc point compensation (so color managed apps wil believe infinite contrast)Run , validate, OK? then Ok.
If white has an unwanted color tint there are several causes, lots of threads about this, use whitepoint editor till you get a pleasing white
Big problem for me is, when I use Calibrite Profiler, I have to rely on their validation (like you said might be for the wrong corrections, so its useless) as I can’t run validation on <Current> as I have described in my other post.
I’ll update that thread.
Anyway ***IF*** calibrite profile had the same access to colorimeter corrections, the workflow will be the same: a matrix profile. AFAIK old i1Profiler used up to 20 grey ramp measurements per channel on calibration stage. This will be akin to “fast” speed on DisplayCAL. It may be good enugh on well behaved displays, those displays without severe color tint on uncalibrated greyscale.
Also I can look at the color space coverage in the ICC profile in ColorSync on Mac. And here the profiles from Calibrites Profiler seem to cover the widest gamut. But if and how that is relevant IDNK.
So maybe if I could figure out which correction is the right one for me Id have a more solid starting point.
I have tried a few backlight corrections but am none the wiser, really. But I also haven’t done it yet in an organised, structured manner.
First 3 are only only profiled as described on the calibration of Calibrites Profiler, all of them come back with huge Delta values.
Next are two different calibrations done with DisplayCal and various corrections (“LCD GB-r-LED/RG Phosphor LED” and “LCD GB-r-LED”). For those gamut coverage is almost 100% for AdobeRGB and 97-98% P3. But Max DeltaE is around 4-5
Then there is two for Asus PA32UCG cess. They seem to work good from a deltaE value, but the coverage of AdobeRGB is around 85%. Maybe I’m doing sth wrong.
Then there is one with the Samsung OLED correction and while this seems to increase the gamut coverage, the avgDeltaE and MaxDeltaE are way worse. See for yourself.
I haven’t had the time for mid or low calibration speed, will do this tonight when the kid is asleep. Sorry for this download but I still feel like fishing in the dark. Im just trying to get a structured understanding of what I’m actually doing here.
Why are you using thise CCSS on an UP2720Q which is very likely to be a W-LED PFS (like newer Eizos or bundled HP Z24x G2)?
Anyway colorimeter correction will affect WP, so grey errors you see in a*b* axis are likely to be present on UP2720Q (of your mac GPU is acting wildly). Bad calibration or bad QC from Dells buil-in calibration system.Also “UP2720Q_#2_2024-12-28_11-30_120cdm?_D6500_2.2_F-S_XYZLUT+MTX” report is very unlikely to be what you wanted since:
-it uses GPU calibration
-it is a profile type that macOS CMM does not like
You are not verifiying UP2720Q HW calibration this way.Also all of them seems to be made in the wrong way if you wanted to verify Calibrite Profiler VCGT grey calibration
” PHL_27_#3_2024-12-28_12-22_120cdm²_D6500_2.2_F-S_1xCurve+MTX” ” PHL_27_#3_2024-12-28_12-47_120cdm²_D6500_2.2_F-S_1xCurve+MTX”
” PHL_27_#3_2024-12-28_13-14_120cdm²_D6500_2.2_F-S_1xCurve+MTX”
” PHL_27_#3_2024-12-28_13-40_120cdm²_D6500_2.2_F-S_1xCurve+MTX”
For comparisions between calibration software you should try first how good it measures using the same (wrong) correction as Calibrite profiler. Whatever you used, which IDNK. Using that wrong correction for a QLED white should be on spot and grey scale without errors.If a display after full calibration in displayCAL with a matrix porfile shows white OK, greyscale OK but relatively high errors near primaries that means tha display is bad behaved, poor QC & electronics.
This means that such display should be profiled by a 3d mesh profile (XYZLUT) but macOS does not like it.If a display after full calibration in displayCAL with a matrix porfile shows white OK, greyscale OK but relatively high errors near primaries that means tha display is bad behaved, poor QC & electronics.
This means that such display should be profiled by a 3d mesh profile (XYZLUT) but macOS does not like it.Forget what I wrote: you are messing with color management. CIE a*b* plot show over or undersaturaion like if user is applying a wrong display porfie or is running ArgyllCMS measurenent window under color managenent, or you are changing from one OSD mode to another.
Same for Dell UP. Use DisplayCAL/ArgyllCMS properly.
Im very sorry for the confusion. The first (Dell UP2720Q) were trying to validate the calibration done by calibrites profiler on the Dell. This was intended for the other thread. Again, I am sorry.
The rest of the reports are from calibrating and profiling the Philips Monitor using DisplayCal and various corrections.
If a display after full calibration in displayCAL with a matrix porfile shows white OK, greyscale OK but relatively high errors near primaries that means tha display is bad behaved, poor QC & electronics.
This means that such display should be profiled by a 3d mesh profile (XYZLUT) but macOS does not like it.Forget what I wrote: you are messing with color management. CIE a*b* plot show over or undersaturaion like if user is applying a wrong display porfie or is running ArgyllCMS measurenent window under color managenent, or you are changing from one OSD mode to another.
Same for Dell UP. Use DisplayCAL/ArgyllCMS properly.
Can the measurement window be run under color management? This is very confusing to me. Is it a Mac speciality? And how do I avoid this?
Maybe I am missing some crucial fundamental about using DisplayCal in general, here….
Im very sorry for the confusion. The first (Dell UP2720Q) were trying to validate the calibration done by calibrites profiler on the Dell. This was intended for the other thread. Again, I am sorry.
The rest of the reports are from calibrating and profiling the Philips Monitor using DisplayCal and various corrections.
If a display after full calibration in displayCAL with a matrix porfile shows white OK, greyscale OK but relatively high errors near primaries that means tha display is bad behaved, poor QC & electronics.
This means that such display should be profiled by a 3d mesh profile (XYZLUT) but macOS does not like it.Forget what I wrote: you are messing with color management. CIE a*b* plot show over or undersaturaion like if user is applying a wrong display porfie or is running ArgyllCMS measurenent window under color managenent, or you are changing from one OSD mode to another.
Same for Dell UP. Use DisplayCAL/ArgyllCMS properly.
Can the measurement window be run under color management? This is very confusing to me. Is it a Mac speciality? And how do I avoid this?
It should work without issue (unless you are running in a VM).
It looks like if you changed OSD mode. Profiles are only valid for the OSD mode and OSD values you used to create them. Change them and no longer valid.
Maybe I am missing some crucial fundamental about using DisplayCal in general, here….
