- This topic has 200 replies, 40 voices, and was last updated 7 months, 3 weeks ago by
.
-
Posts
-
Yes, I bought the i1Display Pro yesterday and conducted some tests. I compared it with the SpyderX.
To summarize, I’m not sure what I’m doing wrong, but all my results are identical to those from the SpyderX and its software.
————–
First, I tried using i1Profiler. Unfortunately, the software couldn’t recognize the device, and I couldn’t use it. I didn’t mind and gave up. Problem for later.
————–
Dell Color Management program.
I noticed that it can only calibrate the GAMMA sRGB. Unfortunately, the U2723EQ monitor doesn’t provide the gamma 2.2 option. It resets the monitor and calibrates it with the Standard/sRGB profile in sRGB gamma. Custom Mode RGB is not allowed. The results are good. I also attached the images. Monitor doesn’t offer gamma 2.2 by default, maybe that’s why?—————
DisplayCAL.
As the CCSS, I selected the second option from the link
https://colorimetercorrections.displaycal.net/?get&type=ccss&manufacturer_id=DEL&display=DELL%20U2723QE&instrument=i1%20DisplayPro%2C%20ColorMunki%20Display%2C%20Spyder4&html=1I chose it as the correction.
Whitepoint: 6500K
Gamma: 2.2
White level: 160cd/m2Single Curve + matrix, medium
For the white balance, it had me set OSD to R:100, G:95, B:94 (see the attached file CAL_Kelvin).
I calibrate/profile it.The result was quite good, and the report looked very promising. see CAL 6500 RAPORT.
The only difference is that when I used SpyderX with DisplayCAL, there was a little red tint at RGB0. This doesn’t happen with the i1Pro. However, when I used the SpyderX software, there was also no red tint.
——————
SpyderX
Later, I compared it with SpyderX. I opened the SpyderX software and, knowing that it wouldn’t measure white balance (no correction available), I wanted to see how much difference there would be in the white balance. The result was only a 50 Kelvin difference! I was surprised. Either the correction isn’t working, or SpyderX was showing the correct value. Results ware exactly same with i1Pro
Then, to take the test one step further, I calibrated the MacBook Air screen.
Spectral: LCD PFS Photoshop WLED IPS, 99% P3 (MacBook Pro Retina 2016)
White balance: 6500K
White level: 160.00 cd/m2Single curve + matrix, medium.
Result: The white balance had nothing to do with the DELL monitor. There was much more magenta.
I calibrated with the SpyderX software to 6500K, and the result: It was identical to the DisplayCAL results.In short, right now, there is no difference between SpyderX and i1Display Pro.
Shouldn’t the correction file close the white balance difference? Where is the mistake, I wonder?
Calibrite Display Pro HL on Amazon SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.In short, right now, there is no difference between SpyderX and i1Display Pro.
I mean, there is no difference in the MacBook Air’s screen when compared to the SpyderX and DisplayCAL at the white point (D65 Kelvin). Magenta heavy.White point (D65 Kelvin) test, DELL vs SpyderX:
I calibrated/profiled my DELL using the SpyderX software and the DELL software, and there was a noticeable difference in the Kelvin values !!AFTER!! calibration. The SpyderX resulted in a more greenish tint (BAH), whereas the DELL software produced a more balanced result. Of course, this doesn’t mean much because I can’t calibrate to a gamma of 2.2 with this setup. This test was only for evaluating the white point, specifically 255, 255, 255.
Comparison of DELL software vs. DisplayCAL:
I think DisplayCAL is slightly better at achieving the white point, but the results are almost identical. It’s pretty good! Shame on Dell software has no 2.2 support.
Do we really need to calibrate to gamma 2.2 for photography?
My Photoshop is always used on-screen, and I almost never print. In this case, wouldn’t sRGB gamma be more suitable? (Wasn’t the sRGB curve designed for CRT monitors?)I’m still wonder why the white balance not match between MacBook airs and Dells with correct corrections CCSS.
So, how do I go about doing this? I calibrate and create an ICM profile with Displaycal and then I run DWM LUT?
As said before, do you need it? do you have calibration actifacts on screen due to GPU?
Most people won’t need it or won’t notice those defects (banding)
BTW, DMWLUT “runs” a LUT3D, but you have to calculate it first. As in any lut3d calulated with displaycal, source is simulated one, destination is display colorspace.
Regarding the other stuff.
That Dell app if it does not take measurements would be using EDID info as data. IDNK that app.
Also the paperweight called SpyderX has a SINGLE correction for all led widegamut displays (all 5+ “modern” spectral power distribution), just one. While on an i1d3 you can feed several ones. This means that AT BEST SpyderX can aim near target on one display type while at best i1d3 can aim near target in ALL of them.
the new calibration looks nice, no green to pink variation in grey, less then 0.5a*, nice. It should work properly on win although you are using a fake TRC that have an impact near black… because it’s a fake TRC (not for BPC, but TRC itself).
Regarding macbook calibration if it is a XDR screen you should use mac app for whitepoint calibration. If not, if calibrating as any other laptop display (that includes the iMacs) whitepoint will be corrected using VCGT and macOS may not like it.
Or maybe your (body) fault, as an statistical outlier in std obs, given that both are WLED PFS but may vary the wvlength where the spikes rise. AFAIK there were some Dells with blue peak moved a few nm to longer wvlength to advertise as “true low blue light”.
Observer variation issues can only be solved by visual match. Remember that you cannot use abs colorimetric LUT3D with standard profiles if visually matched white.Gamma is irrelevant on color managed apps (if we exclude that apple “fake”, or did in the past, default TRC) … as long as you capture ***actual*** TRC (single channel actual TRC).
And since all apple apps using appel CMM may expect the fake TRC with a linear start… whatever it shows is out of control and unreliable. PS should be the reference if you use the actual TRC (and you are not)BTW, how are we here after a year? did you not assume that apple CMM is not to be trusted yet?
Regarding the other stuff.
That Dell app if it does not take measurements would be using EDID info as data. IDNK that app.
It’s measures with i1 Display Pro. It’s does pretty deasent job actualy, easy and strait forward. Result are same as DisplayCAL, beside gamma (sRGB gamma).
Maybe Dell is aware of this limitation in macOS, which is why their software only allows calibration to sRGB gamma. And it’s just works because of the sRGB gamma, Lightroom, Photoshop ACE, CMM, everything is same. I will try this also with Windows, maybe there is then a option for gamma 2.2.
Video of the process: https://youtu.be/0itnIWZrIzE?si=CWwJmhp0U-TRqGiC
Also the paperweight called SpyderX has a SINGLE correction for all led widegamut displays (all 5+ “modern” spectral power distribution), just one. While on an i1d3 you can feed several ones. This means that AT BEST SpyderX can aim near target on one display type while at best i1d3 can aim near target in ALL of them.
the new calibration looks nice, no green to pink variation in grey, less then 0.5a*, nice. It should work properly on win although you are using a fake TRC that have an impact near black… because it’s a fake TRC (not for BPC, but TRC itself).
I need to learn how the TRC acts. I will perform this test also on Windows and see how its goes.
By the way, you mean with FAKE TRC-> Calibrated (changed) gamma, right? (srgb gamma monitor but calibrated for gamma 2.2, so the TRC its now fake)?
Regarding macbook calibration if it is a XDR screen you should use mac app for whitepoint calibration. If not, if calibrating as any other laptop display (that includes the iMacs) whitepoint will be corrected using VCGT and macOS may not like it.
Or maybe your (body) fault, as an statistical outlier in std obs, given that both are WLED PFS but may vary the wvlength where the spikes rise. AFAIK there were some Dells with blue peak moved a few nm to longer wvlength to advertise as “true low blue light”.It’s a XDR screen. Maybe macOS is not liken it. I need try this on Windows. Before with SpyderX was not succesfull, maybe it’s now okey with i1Display Pro.
Dell has in Standard Mode ‘low blue light’ tecnology indeed. Perhaps, Dell software calibrates in Standard mode.
Observer variation issues can only be solved by visual match. Remember that you cannot use abs colorimetric LUT3D with standard profiles if visually matched white.
I will just igrone that laptop screen, i also dont need it. I work always with one screen at the time, and thats definity not the small screen.
Gamma is irrelevant on color managed apps (if we exclude that apple “fake”, or did in the past, default TRC) … as long as you capture ***actual*** TRC (single channel actual TRC).
And since all apple apps using appel CMM may expect the fake TRC with a linear start… whatever it shows is out of control and unreliable. PS should be the reference if you use the actual TRC (and you are not)“And since all apple apps using appel CMM may expect the fake TRC with a linear start” -> Understood.
ACE -> Actual TRC.
BTW, how are we here after a year? did you not assume that apple CMM is not to be trusted yet?
No, I understood and believed what you said from the very first day. My goal is not to test or question your knowledge. It’s just that, due to my job, I’m deeply involved in technical fields (software, electronics), and since I’ve developed an interest in these kinds of things, I can’t rest until I understand how something works (unfortunately). I tend to test and simulate my thoughts and the things I learn from you to confirm if I’ve understood them correctly. However, this topic has dragged on a bit too much, and I feel like I need to bring it to a close.
Back then, I wasn’t even aware of concepts like gamma and TRC, to be honest. ‘Just used recommended gamma 2.2’. I was solely focused on “profile” and ignored the white point due to limitations. Now that I’ve started paying attention to blacks, I felt the need to dive back into research, and once again, I’ve learned a lot from you.
In fact, 3 days ago, I reread that entire topic from start to finish and realized how little I understood you at the time. Now, I can follow you much better (though still not well enough =)). To be honest, keeping up with you is no easy task. You explain things with such technical depth that it’s challenging for someone new to this field to follow. I don’t see this as a negative, but rather as my shortcoming, so please don’t take it the wrong way =) I often rely on ChatGPT for help and translation to better understand things.
I’ve gained complete control over the profiling aspect (single curve). As for calibration, I feel like I’m starting to get it under control, thanks to the i1Pro. I still need to research and grasp the fake/TRC concepts better through graphical representations. ChatGPT will surely help me with that, and I hope I’ll understand things even more when I follow an online course.
Of course, it’s true that getting the same level of blacks in Lightroom’s Develop module as with Apple CMM feels odd. Honestly, I would have expected blacks like those in Photoshop’s ACE. On the other hand, the Library module matches Photoshop ACE. In short, even within Adobe’s product lineup, there are inconsistencies with ACE. I’ll also test these profiles with the i1Pro. Otherwise, I’ll have no choice but to rely on Apple CMM.
This is a software-related topic, and it’s better not to digress. If DisplayCAL truly becomes unsupported and unusable in the future (as Windows 11 seems to be complicating things in this area), what software will we rely on? Currently, i1Profiler isn’t working, and Dell’s software only supports sRGB. Will we be forced to rely on devices/software with inaccurate corrections again?
I can’t edit my previous message, but I want to correct a mistake:
Dell has gamma 2.6, but only for DCI-P3, so its not a macOS limitation. Just a design choise.
It’s not an XDR screen; it’s a regular laptop display.
Regarding the other stuff.
That Dell app if it does not take measurements would be using EDID info as data. IDNK that app.
It’s measures with i1 Display Pro. It’s does pretty deasent job actualy, easy and strait forward. Result are same as DisplayCAL, beside gamma (sRGB gamma).
Maybe Dell is aware of this limitation in macOS, which is why their software only allows calibration to sRGB gamma. And it’s just works because of the sRGB gamma, Lightroom, Photoshop ACE, CMM, everything is same. I will try this also with Windows, maybe there is then a option for gamma 2.2.
Video of the process: https://youtu.be/0itnIWZrIzE?si=CWwJmhp0U-TRqGiC
Unlikely since they have no colorimeter correction for modern displays (even with an i1d3)… and if they do it’s by chance: a wrong EDR or a hardcoded matrix correction for every model, close to spyderx limitation, even greater since we can assume that datacolor corrects each unit to one single spectral power distribution they label wide led or whatever thay callit these days.
But it’s nice that Dell allows sone kind of HW cal for the “lesser” ultrasharp (non UP**** ultrasharps)Regarding results DIsplayCAL vs vendor HW cal it depends on QC. If QC is good, if out of the box the grey is near perfect in color tint, monitor vendor HW cal works… excluding all issues with innacurate device or missing colorimeter corrections.
If out of the box grey is not calibrated to have no color… well… you need ArgyllCMS. This is the combined a*b* range in reports.Also the paperweight called SpyderX has a SINGLE correction for all led widegamut displays (all 5+ “modern” spectral power distribution), just one. While on an i1d3 you can feed several ones. This means that AT BEST SpyderX can aim near target on one display type while at best i1d3 can aim near target in ALL of them.
the new calibration looks nice, no green to pink variation in grey, less then 0.5a*, nice. It should work properly on win although you are using a fake TRC that have an impact near black… because it’s a fake TRC (not for BPC, but TRC itself).
I need to learn how the TRC acts. I will perform this test also on Windows and see how its goes.
By the way, you mean with FAKE TRC-> Calibrated (changed) gamma, right? (srgb gamma monitor but calibrated for gamma 2.2, so the TRC its now fake)?
Look at your HTML report, you choose a fake TRC in DisplayCAL or in the tool used to create that “_DIsplayCAL_i3_3nm_6500k”.
You can store actual TRC and BPC on, or you can store a fake TRC all the way down to black.
Single curve matrix + BPC profile in DisplayCAL should not create that kind of TRC, unless something changed in newer argyll versions. It should create a TRC that “bends” like measurements.
That profile stores 2.2 all the way down instead of bending to 2.1, 2.0… near black. This seems closer to the behavior if you chose gamma + matrixIf it was actually created with single curve matrix maybe you shouldreport the issue to ArgyllCMS mailist. It can be the source of your “lifting” near black issue, not because TRC says RGB 0 => L*0 but because near black that TRC do not bend to tract actual gamma response.
Regarding macbook calibration if it is a XDR screen you should use mac app for whitepoint calibration. If not, if calibrating as any other laptop display (that includes the iMacs) whitepoint will be corrected using VCGT and macOS may not like it.
Or maybe your (body) fault, as an statistical outlier in std obs, given that both are WLED PFS but may vary the wvlength where the spikes rise. AFAIK there were some Dells with blue peak moved a few nm to longer wvlength to advertise as “true low blue light”.It’s a XDR screen. Maybe macOS is not liken it. I need try this on Windows. Before with SpyderX was not succesfull, maybe it’s now okey with i1Display Pro.
Then use DIsplayCAL to measure actual white, then use Apple app to calibrate to D65 providint that white as reference for “current whitepoint”. There are Youtube videos about that, although most of the capture the measured white ina wromng way. Anyway, the istructions about how to set white in Apple app are OK
Dell has in Standard Mode ‘low blue light’ tecnology indeed. Perhaps, Dell software calibrates in Standard mode.
no that’s different. that is a warmer white and any dispay with RGB Gain controsl can do that. I’m talking about “low blue light” in any config since the spectral power distribution in blue spike is moved a litte to red, to it fits in that marketing schema “blue light bellow X nm is at minimum”. Plotting SPD should show that, blue near 460nm instead of typical 450
Observer variation issues can only be solved by visual match. Remember that you cannot use abs colorimetric LUT3D with standard profiles if visually matched white.
I will just igrone that laptop screen, i also dont need it. I work always with one screen at the time, and thats definity not the small screen.
Gamma is irrelevant on color managed apps (if we exclude that apple “fake”, or did in the past, default TRC) … as long as you capture ***actual*** TRC (single channel actual TRC).
And since all apple apps using appel CMM may expect the fake TRC with a linear start… whatever it shows is out of control and unreliable. PS should be the reference if you use the actual TRC (and you are not)“And since all apple apps using appel CMM may expect the fake TRC with a linear start” -> Understood.
ACE -> Actual TRC.
No, i meant what I wrote abobe. Why is your profile storing 2.2 instead of more realistic values, even if at the bottom of the TRC it stores RGB 0 -> L* 0
Single curve + matrix should not behave like that, that is closer to gamma + matrixBTW, how are we here after a year? did you not assume that apple CMM is not to be trusted yet?
No, I understood and believed what you said from the very first day. My goal is not to test or question your knowledge. It’s just that, due to my job, I’m deeply involved in technical fields (software, electronics), and since I’ve developed an interest in these kinds of things, I can’t rest until I understand how something works (unfortunately). I tend to test and simulate my thoughts and the things I learn from you to confirm if I’ve understood them correctly. However, this topic has dragged on a bit too much, and I feel like I need to bring it to a close.
Back then, I wasn’t even aware of concepts like gamma and TRC, to be honest. ‘Just used recommended gamma 2.2’. I was solely focused on “profile” and ignored the white point due to limitations. Now that I’ve started paying attention to blacks, I felt the need to dive back into research, and once again, I’ve learned a lot from you.
In fact, 3 days ago, I reread that entire topic from start to finish and realized how little I understood you at the time. Now, I can follow you much better (though still not well enough =)). To be honest, keeping up with you is no easy task. You explain things with such technical depth that it’s challenging for someone new to this field to follow. I don’t see this as a negative, but rather as my shortcoming, so please don’t take it the wrong way =) I often rely on ChatGPT for help and translation to better understand things.
I’ve gained complete control over the profiling aspect (single curve). As for calibration, I feel like I’m starting to get it under control, thanks to the i1Pro. I still need to research and grasp the fake/TRC concepts better through graphical representations. ChatGPT will surely help me with that, and I hope I’ll understand things even more when I follow an online course.
Of course, it’s true that getting the same level of blacks in Lightroom’s Develop module as with Apple CMM feels odd. Honestly, I would have expected blacks like those in Photoshop’s ACE. On the other hand, the Library module matches Photoshop ACE. In short, even within Adobe’s product lineup, there are inconsistencies with ACE. I’ll also test these profiles with the i1Pro. Otherwise, I’ll have no choice but to rely on Apple CMM.
Maybe this is related to what i wrote above in this message
This is a software-related topic, and it’s better not to digress. If DisplayCAL truly becomes unsupported and unusable in the future (as Windows 11 seems to be complicating things in this area), what software will we rely on? Currently, i1Profiler isn’t working, and Dell’s software only supports sRGB. Will we be forced to rely on devices/software with inaccurate corrections again?
“vanilla” DisplayCAL (Florian’s) works in W11.
Erkan’s DIsplayCAL (the “newer” displayCal) in Windows is facing issues but remember that vanilla displaycal did not work at all in the latest 2 versions of macOS, so development was focused on those OSes and soem linux. WIndows users can use the older one meanwhileIt’s not an XDR screen; it’s a regular laptop display.
Then whitepoint needs to be corrected as in any laptop, with VCGT on GPU. One or two channel max output is going to be limited, lets say as an example RGB 255 255 255 from OS becomes 255 254 253 on HW. Depending on dithering and GPU it may cause a mild tint although that value is the closer you can get to target whitepoint.
BTW just checked a 1xcurve + matrix + bpc targeting D65 g2.2 I made with DisplayCAL and argyll 3.3.0 and… it stores 2.2 all the way down! I checked a few older profiles and it worked that way too.
Weird, I believed that single curve + matrix + BPC would bend TRC a little to make it more realistic near black even if RGB 0 was L*0.
Maybe I saw that behavior with 3xCurve + matrix + BPC and extrapolate it to single curve.Nevermind, skip my coments about this in my previous messages. Also on a 1800:1 display like yours efect should be negible.
Regarding the other stuff.
That Dell app if it does not take measurements would be using EDID info as data. IDNK that app.
It’s measures with i1 Display Pro. It’s does pretty deasent job actualy, easy and strait forward. Result are same as DisplayCAL, beside gamma (sRGB gamma).
Maybe Dell is aware of this limitation in macOS, which is why their software only allows calibration to sRGB gamma. And it’s just works because of the sRGB gamma, Lightroom, Photoshop ACE, CMM, everything is same. I will try this also with Windows, maybe there is then a option for gamma 2.2.
Video of the process: https://youtu.be/0itnIWZrIzE?si=CWwJmhp0U-TRqGiC
Unlikely since they have no colorimeter correction for modern displays (even with an i1d3)… and if they do it’s by chance: a wrong EDR or a hardcoded matrix correction for every model, close to spyderx limitation, even greater since we can assume that datacolor corrects each unit to one single spectral power distribution they label wide led or whatever thay callit these days.
They should be in C:\ProgramData\Portrait Displays\CW\data\i1D3, like MSI’s calman based app and others. Maybe with dell app is different but look for the EDRs.
If you had a i1d3 c6 it should offer more, that’s the toll with Calman based tools
in MacOS they should be /Applications/Dell Color Management.app/Contents/Frameworks/i1d3SDK.framework/Versions/A/Resources/Calibrations
“Calman Toll”, as in calibrite’s app. All corrected by RG_phosphor (GBLED) or RGB LED (old and unsed QD-like spd with a red spike mover far away to longer wavelengths and unrealistic to newer displays)
Xrite (i1Profiler 3.7.1, latest one with i1d3 support) had one for these multimedia WLED PFS 9*% P3 displays and of course “full calman” has one PFS family (the same that are bundled with DisplayCAL) for i1d3.
Just happens that they do not include it in those “lesser” software tools they made for monitor vendor. This is calman/Dell fault.
Hey Vincent and everyone,
I recently conducted some tests comparing Dell’s color calibration software, DisplayCAL, and SpyderX’s native software using both a SpyderX and an i1 Display Pro.
- Results with Dell Calibration Software:
macOS:
You can calibrate the Standard, sRGB, Rec. 709, and DCP-P3 native modes, and the software does a decent job.
It corrects colors effectively, but it only calibrates to the sRGB gamma curve. This works fine for all apps, and you get consistent blacks.
However, you cannot calibrate the “Custom Mode,” which allows fine-tuning of the RGB sliders.
Delta E after calibration: 0.45.Windows:
The software is buggy on Windows 10 (I don’t have Windows 11 machine yet).
It’s unstable, and the calibration report claims gamma 2.2 calibration, but the software actually calibrates to the sRGB gamma curve.
My tests confirm it’s sRGB gamma, even though the reports are inconsistent.
Delta E after calibration: 0.95 (roughly twice as high as on macOS).Conclusion:
The software is limited but decent. Install it, calibrate/profile your display, and use it.- Results with DisplayCAL Software:
macOS:
The latest installation method (Erkan’s script) works perfect.
The program might repeatedly download the driver, but that’s a minor inconvenience.
Using the i1 Display Pro and calibrating with Single Curve + Matrix (BPC ON) at medium speed, I achieved a Delta E of 0.2.Windows:
DisplayCAL works well on Windows 10. For Windows 11, Vincent mentioned that older versions of the software might be needed.
Gamma correction is applied correctly via the GPU, and color-aware apps handle it well.Conclusion:
This is an excellent software solution, though installation might be a bit advanced for non-technical users in the future. With the i1 Display Pro, you have a lot of customization options.SpyderX Comparison:
macOS and Windows:Compared to the i1 Display Pro, the SpyderX performs poorly for white balance, producing a noticeable greenish tint.
Color gamut correction is good, but low-end blacks (1,1,1) are slightly elevated. Still, this isn’t a major issue. (1:1800 contact situation)
For beginners, SpyderX paired with its native software is simple to use. Just remember to disable white balance correction during profiling.Conclusion:
Good for beginners. If you’re okay with manually adjusting white balance and brightness, there’s no need to upgrade from the SpyderX unless you require advanced features. You want to buy this? Don’t buy it =)Final Thoughts:
I prefer DisplayCAL because it lets me calibrate to gamma 2.2 and adjust custom RGB slider settings.I also performed black-level tests, but I’ll share those results in another post since this topic focuses on software. For anyone curious about black levels, check out this thread: Black Levels at Standard sRGB ICC vs Profiled ICC (Page 2).
Hey Vincent and everyone,
I recently conducted some tests comparing Dell’s color calibration software, DisplayCAL, and SpyderX’s native software using both a SpyderX and an i1 Display Pro.
- Results with Dell Calibration Software:
macOS:
You can calibrate the Standard, sRGB, Rec. 709, and DCP-P3 native modes, and the software does a decent job.
It corrects colors effectively, but it only calibrates to the sRGB gamma curve. This works fine for all apps, and you get consistent blacks.
However, you cannot calibrate the “Custom Mode,” which allows fine-tuning of the RGB sliders.
Delta E after calibration: 0.45.Windows:
The software is buggy on Windows 10 (I don’t have Windows 11 machine yet).
It’s unstable, and the calibration report claims gamma 2.2 calibration, but the software actually calibrates to the sRGB gamma curve.
My tests confirm it’s sRGB gamma, even though the reports are inconsistent.
Delta E after calibration: 0.95 (roughly twice as high as on macOS).Conclusion:
The software is limited but decent. Install it, calibrate/profile your display, and use it.DeltaE to what? and using what instrument, which correction?
Dell app is not able to measure WLED PFS with an i1d3 because Dell had no paid Portrait Displays (Calman guys) for that (or because Portrait Displays do not want to bundle that in “lesser products” only in Calman).
Hence if you are validating using dell report tool, you are measuring with a wrong “ruler” and you used that wrong ruler to do your “carpentry work”.
“Measurements will match”, since you are using same ruler, but your wood wardrobe may not be actually 100cm x 100cm as you wanted, but 95×95As it has been explained many times here, you can use DisplayCAL to measure and validate some other tool work in two ways:
-with the same “wrong ruler”, to inspect “inner” issues in the first calibration tool, like grey range issues (color tint a* oscilations in greyscale, typically) or not being able to get the desired target, even using the “wrong ruler” to evaluate.
-with the “proper ruler” to inspect how far your results are from your actual target.
Each approach is usefulAnyway, as in Eizo ColorNavigator or Viewsonic o former Benq calibration tool, for HW calibratable monitors, there is a way to overcome this lack of proper “software” colorimeter corrections (for i1d3 all corrections are software, this is the reason we can “upgrade” to new displays).
-find a spectral power distribution that matches your display (CSV, CCSS)
-find which “wrong” EDR your app is usin, inspect its structure (argyll oeminst app)
-use a tool to convert that “text” spectral data to Xrite EDR binary format, like CCSS2EDR python tool, and store it in a EDR. Better if preserve original “wrong” EDR structure (number of samples, headers and such)
-replace old EDR with new EDR (replace it every time monitor vendor app updates)Several threads about that.
Since actual error between wrong EDR and good EDR for a particular display depends on colorimeter firmware data, for one i1d3 error could be higher and for another i1d3 smaller. Both statistically equal in accucary with the good edr for that display, but with high varation when using the wrong one.
This means that by chance, it could be almost no whitepoint error using a wrong edr on some i1d3Hey Vincent and everyone,
I recently conducted some tests comparing Dell’s color calibration software, DisplayCAL, and SpyderX’s native software using both a SpyderX and an i1 Display Pro.
- Results with Dell Calibration Software:
macOS:
You can calibrate the Standard, sRGB, Rec. 709, and DCP-P3 native modes, and the software does a decent job.
It corrects colors effectively, but it only calibrates to the sRGB gamma curve. This works fine for all apps, and you get consistent blacks.
However, you cannot calibrate the “Custom Mode,” which allows fine-tuning of the RGB sliders.
Delta E after calibration: 0.45.Windows:
The software is buggy on Windows 10 (I don’t have Windows 11 machine yet).
It’s unstable, and the calibration report claims gamma 2.2 calibration, but the software actually calibrates to the sRGB gamma curve.
My tests confirm it’s sRGB gamma, even though the reports are inconsistent.
Delta E after calibration: 0.95 (roughly twice as high as on macOS).Conclusion:
The software is limited but decent. Install it, calibrate/profile your display, and use it.DeltaE to what? and using what instrument, which correction?
Dell app is not able to measure WLED PFS with an i1d3 because Dell had no paid Portrait Displays (Calman guys) for that (or because Portrait Displays do not want to bundle that in “lesser products” only in Calman).
Hence if you are validating using dell report tool, you are measuring with a wrong “ruler” and you used that wrong ruler to do your “carpentry work”.
“Measurements will match”, since you are using same ruler, but your wood wardrobe may not be actually 100cm x 100cm as you wanted, but 95×95As it has been explained many times here, you can use DisplayCAL to measure and validate some other tool work in two ways:
-with the same “wrong ruler”, to inspect “inner” issues in the first calibration tool, like grey range issues (color tint a* oscilations in greyscale, typically) or not being able to get the desired target, even using the “wrong ruler” to evaluate.
-with the “proper ruler” to inspect how far your results are from your actual target.
Each approach is usefulAnyway, as in Eizo ColorNavigator or Viewsonic o former Benq calibration tool, for HW calibratable monitors, there is a way to overcome this lack of proper “software” colorimeter corrections (for i1d3 all corrections are software, this is the reason we can “upgrade” to new displays).
-find a spectral power distribution that matches your display (CSV, CCSS)
-find which “wrong” EDR your app is usin, inspect its structure (argyll oeminst app)
-use a tool to convert that “text” spectral data to Xrite EDR binary format, like CCSS2EDR python tool, and store it in a EDR. Better if preserve original “wrong” EDR structure (number of samples, headers and such)
-replace old EDR with new EDR (replace it every time monitor vendor app updates)Several threads about that.
Since actual error between wrong EDR and good EDR for a particular display depends on colorimeter firmware data, for one i1d3 error could be higher and for another i1d3 smaller. Both statistically equal in accucary with the good edr for that display, but with high varation when using the wrong one.
This means that by chance, it could be almost no whitepoint error using a wrong edr on some i1d3Hi Vincent,
Thank you for your explanation. This test what I did is just a test for beginners like me. Just calibrate/profile it and compare with DisplayCAL, with correct correction CCSS. (i1 display pro + downloaded CCSS from DisplayCal database).
Then, just compare it to other programs and everything looks the same with Dell application. Switch between profile and se with your eyes if there is a visible differences. That’s all. Nothing special and fancy. No visible by eyes? It’s good for me.
There is only one more question which I can’t explain. Can u maybe check that post as well for us?
https://hub.displaycal.net/forums/topic/black-levels-at-standard-srgb-icc-vs-profiled-icc/page/2/#post-142534Thank you for your support.
