Home › Forums › Help and Support › I need a lot of help calibrating my Dell XPS 9510 OLED display
- This topic has 5 replies, 2 voices, and was last updated 4 years, 9 months ago by
Vincent.
-
AuthorPosts
-
2021-08-19 at 13:53 #31305
I’m completely new to this world, so I need somebody to explain everything to me like I’m 5.
The situation: I bought the new Dell XPS 15 9510 that comes with an OLED screen. Then I bought a SpyderX Pro thinking that it was able to recognize OLED. I was wrong. So then I bought a ColorChecker Display Pro.
The ColorChecker Display Pro did recognize the OLED. However, it gave me three options for OLED.
- The first time around, I selected the third option (WOLED) and I just went through the process, selecting whatever I thought was correct with no real rhyme or reason. I could have selected the wrong settings. I don’t know. Somebody I was talking to over on Reddit said the profile was good.
- The second time around, I selected the second option (RGB OLED family) and I tried to be more conscious of the settings I selected. This time, I also created a 3D LUT to use with MadVR and PotPlayer as it seems MadVR doesn’t accept ICC profiles. But I know even less about 3D LUTs.
Okay, we’re now all up to speed. Some questions:
- Which settings should I choose when calibrating through DisplayCAL?
- How do I set it up so that every app is correctly colour-managed?
- How do I know when something is correctly colour-managed? (Web browsers, photo viewers, etc.)
- Do I have to create a separate ICC profile/3D LUT for MadVR?
- How do I go about setting up the 3D LUT in the MadVR settings?
- Should I have multiple settings for different types of content? (e.g. BT.709, DCI-P3, etc.)
SpyderX Pro on Amazon Calibrite Display Pro HL on Amazon Calibrite Display SL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2021-08-20 at 14:37 #31311OLEDs are difficult to profile because ABL. Yours should be RGB OLED.
There are lot of apps that are not color managed, try dogelition DWM LUT on these. For color managed apps just calibrate&profile then install profile as default display profile (use Displaycal loader if you can).
Since OLED profile badly you can use same detailed XYZLUT profile for all. In LUT3D it is the destination profile. Source profile is the colorspace you want to simulate (rec709, 2.2 or 2.4 gamma).
If you wish to keep global 1D LUT calibration from ICC profile, create LUT3D without embeding VCGT. ALso if you choose the opposite (apply VCGT in LUT3D) you cannot have as default profile the one you made with displayCAL (because it has 1D LUT grey calibration).
MadVR and DWMLUT use different formats, you should make une LUT3D for each one even they have the same params.
-
This reply was modified 4 years, 9 months ago by
Vincent.
2021-08-20 at 15:12 #31313Reminder:
I’m completely new to this world, so I need somebody to explain everything to me like I’m 5.
RGB OLED or RGB OLED family? I went with the latter. I don’t know what the difference is.
Everything else you said is going way over my head.
2021-08-22 at 16:30 #31339Spectral power distribution is almost the same on both CCSS, you can plot them with information button.
ABL, auto brightness limiter on OLED displays due to their delicate nature and burn pixels makes them difficult to profile because if ABL kicks in you won’t measure actual panel behavior but the atenuated one. That’s one of the reasons to avoid those small OLED displays for any serious color work. They do not behave the same way everytime. INDK how often ABL kicks in in your laptop you’ll have to figure it. Depening on that limit patch window size.
Then calibrate & profile using a detailed profile (XYZLUT+matrix). You can use that profile as source data to make LUT3D. When making LUT3D you can embed grey calibration stored in profile or skip it. Whatever you choose there should be only one grey calibration active, so if you enable grey calibration in one part of image pipeline, it cannot be on other stage or it will be applied twice.
It is possible that some browsers reject that XYZLUT profile and request to have a matrix type as display profile.
As a general rule avoid OLED laptops. If you can try to return for refund do it and get a good high contrast (1200:1) IPS screen with 9x%-100% sRGB coverage and just that (no widegamut P3/AdobeRGB), once calibrated it will behave like a good common sRGB display that you have been using before.
-
This reply was modified 4 years, 9 months ago by
Vincent.
2021-08-22 at 20:02 #31342I’m curious. What laptops have displays that only cover sRGB? All of the top laptops with similar specs to the 9510 come with wide-gamut displays.
I don’t want to downgrade the screen (16:10, 3.5k, black level), overall build quality, CPU (11th gen Intel i7), or the GPU (RTX 3050 Ti). My biggest issue with the laptop itself is just the fact that it comes with a wide-gamut display. And that wouldn’t be a problem at all if colour management wasn’t such a pain to deal with.
2021-08-22 at 20:11 #31343The PITA is ABL, not color management. If you do not care about ABL induced inaccuracies, make a profile from native primaries, like EDID option in File menu even without measuring (or a simple matrix profile in a setting where ABL does not mess up), then make a LUT3D in IRIDAS .cube for dogelition’s DMW LUT (from sRGB to display colorspace). Load LUT3D, assign sRGB as a display profile an your main problem is solved… but ABL will remain the same PITA as before.
Regarding high spec laptops I do not know, maybe MSI prestige series (IPS-like and sRGB only in some models) but IDNK full specs.
-
AuthorPosts