- This topic has 14 replies, 4 voices, and was last updated 1 week ago by
.
-
Posts
-
I am using a Spyder X Pro to calibrate my display. I want to linearize it and set the whitepoint to 6500K.
So I used the following settings:
Whitepoint: 6500K
White level: 170 cd/m2
Gamma: 1.0, absolute.All rest was set to default.
During the calibration, DisplayCal interactive display adjsutment told me my to mess with the RGB gains (I used Intel Graphics Center, there is no other way), until all bars were at the correct positions. After everything was properly adjusted, the calibration continued with no issues.
I got the following results:
17:27:34,609 Setting up the instrument
17:27:34,611 Instrument Type: Datacolor SpyderX
17:27:34,611 Serial Number: 61076384
17:27:34,611 Hardware version: 4.91
17:27:34,611 Current calibration response:
17:27:34,611 Black level = 0.1778 cd/m^2
17:27:34,611 50% level = 85.17 cd/m^2
17:27:34,611 White level = 169.47 cd/m^2
17:27:34,611 Aprox. gamma = 0.99
17:27:34,611 Contrast ratio = 953:1
17:27:34,611 White chromaticity coordinates 0.3121, 0.3293
17:27:34,611 White Correlated Color Temperature = 6533K, DE 2K to locus = 5.2
17:27:34,611 White Correlated Daylight Temperature = 6535K, DE 2K to locus = 0.6
17:27:34,611 White Visual Color Temperature = 6345K, DE 2K to locus = 5.0
17:27:34,611 White Visual Daylight Temperature = 6514K, DE 2K to locus = 0.6Everything seems fine, except that my display white is very much red. I immediately suspected something was wrong. How does the report claims a white correlated color temperature of 6533K when my display is reddish? Maybe my eyes fooling me? So I used a light meter to measure color temperature (I used an app in my phone), and it reports a temperature of around 5600K. This is a lot different than D65.
Definitely, something is wrong in this calibration.
To control for the fact that I might have adjusted the RGB gains incorrectly, I also repeated the calibration with the interactive display adjustment disabled , so DisplayCal adjusted the RGB gains by itself. But the results were almost the same. I am not posting the report, it is almost identical to the previous one.
Now, my display manufacturer claims its temperature is D65. So I repeated the calibration, but now using the “as measured” option for white point. Here are the results:
17:36:04,360 Setting up the instrument
17:36:04,360 Instrument Type: Datacolor SpyderX
17:36:04,360 Serial Number: 61076384
17:36:04,360 Hardware version: 4.91
17:36:04,360 Current calibration response:
17:36:04,360 Black level = 0.3609 cd/m^2
17:36:04,360 50% level = 85.43 cd/m^2
17:36:04,360 White level = 163.15 cd/m^2
17:36:04,360 Aprox. gamma = 0.93
17:36:04,360 Contrast ratio = 452:1
17:36:04,360 White chromaticity coordinates 0.3016, 0.3333
17:36:04,360 White Correlated Color Temperature = 7075K, DE 2K to locus = 12.7
17:36:04,360 White Correlated Daylight Temperature = 7068K, DE 2K to locus = 9.9
17:36:04,360 White Visual Color Temperature = 6486K, DE 2K to locus = 12.3
17:36:04,360 White Visual Daylight Temperature = 6637K, DE 2K to locus = 9.5The white pint looks much more white. Also, my mobile app light meter reports a temeperature of 6200K, which is much closer to D65 than when I set the temperature at 6500 in DisplayCal.
So either DisplayCal or Spyder X are the wrong here, not my eyes, not my light meter app, and not the display manufacturer.
I can’t find any mistake by my part in the calibration settings. I disabled any RGB adjustment gains when not being used in calibration. All my Windows 11 system settings are default.
Spyder X Pro was bought 2 weeks ago.
So what is going on here? Why is DisplayCal doing a wrong calibration when I aim for D65? Why is it to much red?
All best.
SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.As an update of my previous post, I send in attachment a print screen of the white point chromaticity editor. When I type the D65 coordinates, I get a white red window. Definitely something is wrong here.
I am using a Spyder X Pro to calibrate my display. I want to linearize it and set the whitepoint to 6500K.
[…]So either DisplayCal or Spyder X are the wrong here, not my eyes, not my light meter app, and not the display manufacturer.
I can’t find any mistake by my part in the calibration settings. I disabled any RGB adjustment gains when not being used in calibration. All my Windows 11 system settings are default.
Spyder X Pro was bought 2 weeks ago.
So what is going on here? Why is DisplayCal doing a wrong calibration when I aim for D65? Why is it to much red?
All best.
You got a wrong device. Nodoby buys spyders, you have a very limited device that may measure wrong unless you buy or rent an spectrophotometer, since its set of colorimeter correctiosn is limited and it does not work with distrubuted spectral corrections like Xrite/Calibreite i1d3, so other people’s spectral measurment for teh same display model or backlight tech won’t be portable to your SpyderX.
Return for refund and get an i1d3 colorimeter (~160€ model akin to old colormunki display won’t be supported for HW calibration monitors, so you’ll need the >230€ model if you want those features)
If not possible you’ll have to guess backlight type of each display you want to measure and apply in DisplayCAL’s upper right corner “MODE” the proper bundled colorimeter correction for each display.
LED sRGB only display = White LED / Standard LED
LED P3/AdobeRGB Displays = Wide LED but even this may be innacurate since it is using a single correcion for several (at least) backlight types.Then do as Kuba’s said. Do not use RGB sliders in GPU controls, let DisplayCAL handle it, even if RGB sliders are off let DIsplaYCAL to continua and it will try to correct on GPU LUTs, close to waht you tried to do in GPU controls.
If due to SPyderX limitations regarding bundled pack of corrections, you get a “tinted” white, use visual white point editor and choose a reference white by eye appraisal. Color managed apps won’t care about it… but if you use display profile to make LUT3Ds remember to use “relative colorimetric” instead of absolute or visually picked white will be undone.
It is Windows 11. What correction is it and where can I find it? I couldn’t find anything for SpyderX.
Unfortunately its passed the refund period.
I have been using WLED, as Im using a MSI katana laptop with a generic monitor.
I was hopeing something was wrong that was not wrong. A lut loader conflict I was thinking. I was wrong. I think your Spyder X should work fine. It needs the right correction.
Specs say it is WLED, I believe that means white LED.
https://www.panelook.com/B156HAN08.4_AUO_15.6_LCM_overview_48179.html
I have always used the LCD White LED options, but also tried different modes and it didn’t change anything.
In order to adjust the gains, I have to use Intel Graphics Center. It behaves a bit strangely, but in the end all bars were at middle. If I disable interactive adjustment, I get the same results anyway.
Specs say it is WLED, I believe that means white LED.
https://www.panelook.com/B156HAN08.4_AUO_15.6_LCM_overview_48179.html
16.7M 45% NTSC
low cost ~60% sRGB White LED, yes.
In order to adjust the gains, I have to use Intel Graphics Center.
Don’t adjust them, reset to default values on Intel control panel, let DisplayCAL do it for you, just click on continue even if RGB bars are not aligned.
How can I get that correction?
For a Spyderx? other than bundled WhiteLED/Standard LED? You’ll need to buy or rent an spectrophotometer supported by ArgyllCMS.
Otherwise use visual white point editor (icon on the right if you choose color coordinates instead o Color Temp), get a white that resemples D65 and live with it. LUT3D made with way must be relative colorimetric or visually matched whitepoint will be undone.
By the way:
Everything seems fine, except that my display white is very much red. I immediately suspected something was wrong. How does the report claims a white correlated color temperature of 6533K when my display is reddish? Maybe my eyes fooling me? So I used a light meter to measure color temperature (I used an app in my phone), and it reports a temperature of around 5600K. This is a lot different than D65.
Color correlated temp is yellow – blue axis. Pink green axis info is missing. You can be exactly 6500K CCT and by pink with a lab grade equipent. There are several many any 6500K CCT white but oly a few are around D65 (no green pink tint)
I ended up doing a colorimetric correction using this device: https://www.jeti.com/Products/Spectroradiometer/specbos1211-2
Things seem much better now, but I still need to confirm.
What I can say is that it was SpyderX’s fault. And the device was new. Datacolor should be ashamed of selling such inaccurate devices.
