- This topic has 14 replies, 5 voices, and was last updated 1 week, 4 days ago by
.
-
Posts
-
Hello, I tried to calibrate a QD OLED screen but it ended up with a green tint. I’ve read that I need to change CIE 1932-2 to CIE 2012-2, but the option doesn’t seem to be available in the calibration settings?
Sorry that is version 3.9.17 problem. Are you in Windows ? Then you can uninstall and install 3.8.9.3. I have not tested those new versions yet. Everything is fine with the old version for me. The newer argyii is better for some screens and devices. Some calibration devices do not work with the old argyii. You can use the new argyii with 3.8.9.3 by telling displaycal where argyii is. I believe argyii is backwards compatible so new versions work where old versions did. The issues for 3.9.17 is on https://github.com/eoyilmaz/displaycal-py3/releases
I see your posts on the issues there.
Yes, I’m using it on Windows. I tried using version 3.8.9.3 as you suggested, but it didn’t make any difference. Perhaps the problem lies with the sensor I’m using? It’s a Spyder 2024, as shown in the second screenshot.
Yes, I’m using it on Windows. I tried using version 3.8.9.3 as you suggested, but it didn’t make any difference. Perhaps the problem lies with the sensor I’m using? It’s a Spyder 2024, as shown in the second screenshot.
You’ll need a Xrite/Calibrite i1d3 colorimeter to use multiobserver… in ArgyllCMS. Spyder X, X2, 2024… lack of spectral sensivity curves stored in firmware, or if present they do not expose its reading… so you are limited to a very few modes (built in matrices) and the observer they ware made for.
DisplayCAL is using CIE 1931 2 degree by default on the i1d3. Maybe you can add then with tools/advanced/additional commandline arguments.Nobody buys spyders these days if they had made a minimum online research… get an Xrite/Calibrite i1d3.
But if your problem is the color tint after calibration in your OLED display… just use DisplayCAL’s visual white point editor (whitepoint > color coordinates, the choose 3 ball icon on the right). Get a visual match to some D65 reference and calibrate to those alternative xy coords.
Remember to do not use “absolute colorimetric” in LUT3D if you do this approach an use rec709 D65 as calibration target for the LUT3D.SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Thank you both for your help, but unfortunately I can’t seem to achieve a satisfactory result by adjusting the white point editor.
I’d bought this colorimeter before I had an OLED screen, and it was stated that it was also designed for recent screen technologies such as OLED, so I’m really disappointed with my purchase now…I was going to say that you need to set a correction. Click the little globe icon next to the Corrections dropdown. It should open a popup with spectral corrections to choose from. I already had a look on the website version so choose the Spectral type called “Samsung Odyssey G60SD Graphics”. This would be standard for any X-Rite/Calibrite meter – however I’ve seen you’re on Spyder. Some Spyders do work with colorimeter corrections like CCSS (so I’ve heard) so give it a try.
If that doesn’t work, try “Tools > Corrections > Import colorimeter corrections from other display profiling software” and tick Spyder4/5. It should download some corrections that Datacolor supply and from there, you can select QD-OLED or any other narrow peak, accurate RGB type display.
For setting a custom observer, you have to tick “Options > Show advanced options” although I doubt a custom observer will give you any help. Your whitepoints are off because your meter can’t adjust its measurements to the human eye. That’s what the corrections are for. Either the CCSS I recommended will work great, or you’ll have to use one provided by the meter manufacturer that’s for a display type similar/identical to yours.
Most fancy monitors are calibrated from factory so odds are, you can just put it in sRGB mode/Warm color temp for the factory calibrated 6500K. From there, you can set DisplayCAL’s Calibration > Whitepoint = “As Measured” and it will match that factory whitepoint without deviating. That often gives better results for people struggling to dial in their whitepoint as you’re just copying the factory white.
I would say make sure you select the best colorimeter correction for your monitor, then continue trying to calibrate at D6500. If whites have a noticeable tint or cast, then try “As Measured” and it should help straightaway.
Even a fancy spectro won’t get you a good D65 white point for QD-OLED, with either CIE 1931 or 2012.
You need an older tech display as reference as use your eyes to do a perceptual matching.
Thanks for your help. I’ve tried the spectral corrections, but they aren’t compatible with my Spyder, and if I use the ones for the Spyder 4/5, I end up with the same tint issue.
However, I did as you said and used the white point as measured so that it wouldn’t change it, and I’ve managed to achieve a white point that isn’t perfect but is acceptable.
I still think, as I’ve read in several posts, that Calibrite colorimeter must be better for this type of monitor.@DaniJ I went down the whole rabbit hole with my LG C1, getting an i1Pro2 spectro for my meter over a minor deviating whitepoint (think it was pinkish or greenish). It wasn’t even that bad compared to QD-OLED today. All it needed was a meter profiling and then default settings with CIE1931 calibrated to the proper whitepoint.
QD-OLED is so bad, there is no way I can get a whitepoint match even with a profiled meter. I had to use As Measured or Judd Offset WP (0.3067, 0.318) for a visual white match. Judd was noticeably cooler but least distracting, As Measured was factory calibrated sRGB WP and a bit warm but the best overall match. Both are not perfect. Using D6500 coordinates are the worst, the WP looks so much yellower than all the other options. I don’t want to do a visual match as I only trust the meters and not my eyes, lol.
@SkayAz As Measured should measure the default whitepoint on your screen and set that as the target for calibration. This means whatever the whitepoint is in the monitor OSD should be the target whitepoint of your profile (basically the calibration isn’t changing your whitepoint but will do everything else). I recommend playing around with your monitor RGB controls. Really you should just use the factory sRGB mode which locks out all other controls, then run a calibration on top of that with “As Measured” and it will keep the same whitepoint as factory sRGB. The other option is to dial in the RGB controls manually – tick “interactive display adjustment” before starting calibration and it’ll show you onscreen what to change. Here you will see what your meter is thinking white is = whether your corrections are set correctly. You will be able to tell by eye if it’s off, especially on a panel like yours. I’m sure there must be advice for applying corrections with your Spyder. If not, go back to As Measured and default sRGB/warm color temp on OSD.Also Spyder meters don’t get much support in general. I’ve personally never used one. Generally it’s recommended to get a Calibrite (previously X-Rite) meter. They cost £200-300 instead of £100 but they never drift over time. All they need is a correction which you can either use a default from the list, click the download icon to use someone else’s .CCSS, or measure your own if you had a spectro (not worth it).
@SkayAz Check this, it has some instructions on installing the factory corrections for your meter, if that would help.
https://argyllcms.com/doc/oeminst.html
(ArgyllCMS binaries are located in appdata – roaming – DisplayCAL and then DL, I think. Find the folder, open a terminal and run oeminst)
It says .CCSS (Argyll/DisplayCAL spectral correction format) should work with your Spyder 5 meter. It also has a guide for installing the factory corrections if the community submitted ones won’t work. Personally I would advise to click the downloads/globe button next to the corrections dropdown and use someone else’s CCSS correction. You can view it on the graph before downloading to make sure it’s correct (sharp and even red green blue peaks).
All the best.
Let’s ignore the colorimeter for now and only focus on the spectro with the goal of getting good white using only the spectro.
The device measures a spectrum. You trust yours, I trust mine. But the spectrum is only half of the end result. It needs to be converted to a color and for this we multiply it with three functions determined 100 years ago by having ~10 people compare some colors (CIE 1931).
CIE 1931 produces visibly wrong results with QDOLED and also WOLED to a lesser degree. So until we get a proper function, using CIE 1931 on a QDOLED will produce a visible color cast, even with an expensive spectro. Same for 50 year old Judd-Vos functions or CIE2012.
Using perceptual matching is the only way I got neutral D65 out of the QDOLED. A pleasure to watch after that.
That’s what I did – I manually adjusted the white point by copying my IPS screen, but I can’t make the white point exactly the same either; I have to make it a bit cooler, otherwise the skin tones look a bit red compared to the IPS screen, even after calibration.
As for CCSS profiles, there aren’t any for the Spyder 2024 – it’s a bit of a shame when I see that there are several available for the Calibrite with my monitor model.
I can’t help thinking that the results would be better with Calibrite.
That’s what I did – I manually adjusted the white point by copying my IPS screen, but I can’t make the white point exactly the same either; I have to make it a bit cooler, otherwise the skin tones look a bit red compared to the IPS screen, ***even after calibration***.
That may not be a calibration issue.
Match white visually, since you can.
Calibrate greyscale (.cal file for VCGT) so all greys look the same as that whiet (on good displays it may not bee neded).
Same if doing it for a TV, calibrate the N-point greyscale so all greys are visually equal in color tint to visually matched whiteAfter calibration, display behavior is mesured and an ICC s created. There Spyder “may” measure with high error the red primary, so ICC and any LUT3D made after that ICC may carry an under/oversaturation or sRGB/Rec709 red.
On a TV, no ICC pipeline at all, this is done with the CMS of the TV where you use 6 axis controls to match Rec709’s RGBCMY
On this step, is that spyder is actually mis reading native red primaries, you’ll need to do a visual match (TV) or create a synth profile thay maybe some fake values.****But maybe there is no issue at all****, just you using non color managed image viewer or video player, hence you’re watching Rec709/sRGB content “direct nuber translation” to native gamut.
I can’t help thinking that the results would be better with Calibrite.
if last sentence applies, no matter which colorimeter or widegamut “tradictional” LED display you buy… you had not used color management.
