Home › Forums › Help and Support › Experts help me calibrate QD-OLED
- This topic has 9 replies, 4 voices, and was last updated 2 weeks, 3 days ago by
Marcello Frisina.
-
AuthorPosts
-
2025-03-19 at 21:02 #143326
Hello, first of all, I apologize if my English isn’t good.
I’m a complete novice when it comes to calibrating a monitor. I’d like to know if anyone can help me calibrate it, detailing the settings I need to specify in the program. I’ll give you details about my monitor and colorimeter.
Mac m4 operating system
Monitor: MAG 321UPX QD-OLED
Specs:- QD-OLED
- Typical SDR: 250 nits
- Maximum HDR: 1000 nits
- Contrast ratio: 1500000:1
- DCI-P3*/ sRGB:99%/ 138,2%(CIE1976)
- Adobe RGB:97,5%
- 10 bit
- VESA DisplayHDR True Black 400
Monitor Calibrator: i1 Display Pro X-Rite
DisplayCAL 3.9.14
ArgyllCMS: 3.3.0.
I want to create two profiles, if possible. As I said, I’m a beginner. I want a photography profile using the Adobe RGB color space, and a video editing profile using the DCI-P3 color space. I don’t know if you can create those profiles and then add them to Photoshop and DaVinci Resolve or what the process would be to have two profiles.
My monitor only has one user profile where I can adjust the rgb values and of course the brightness.
Thank you very much in advance
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2025-03-20 at 12:36 #143333For better or worse you are on macOS…so no need to calibrate for specific colorspaces.
Maybe different brightness settings but thats all.1 profile, default settings. If no specific colorimeter correction for QDOLED use QLED or RGBOLED. Fix white manually if due to this colorimeter correction inaccuracy “white does not look white”
2025-03-20 at 13:10 #143338Hi, thanks for responding. But I don’t understand what you mean by not needing to calibrate in multiple profiles. Do you mean that if I go into Photoshop on Mac it automatically sets the AdobeRGB space? And if I go into DaVinci Resolve it sets the DCI-P3 space? As for the other thing you mentioned, I don’t know what you’re referring to. As I said at the beginning, consider that I’m a complete novice. I’ve never used DISPLAYCAL. I’ve watched videos, but things aren’t clear to me, and if I have to activate, for example, black point and white point compensation, and many other options that I don’t know about either.
2025-03-20 at 13:44 #143339Why would Photoshop limit native gamut to AdoberGB? what a waste
Google what color management is.
Photoshop or any color management app in Win/mac/linux will read source colorspace of a image (sRGB/AdobeRGB) and reencode its RGB numbers into another RGB numbers in display (profile) colorspace.On macOS for resolve there is a checkbox to request Resolve to do that in the sme way: “use mac profiles” or something like that, google it. = on the fly, from sour project colorspace to display colorspace.
Or you can create a LUT3D with a static/chrystalized transalation for just ONE colorspace, a LUT3D and set it into project properties, for each project.If display is good behaved, if it can be described accurately by a single curve matrix profile, use mac profiles option is easier and maybe accurate enough. Do a validation from reove output in displaycal to check it.
2025-03-22 at 19:41 #143341Hello again, I have done the calibration and I thought it was going to be pretty good because the delta is quite low or so I think but the screen looks pretty bad, I am attaching the data that the profile shows me to see if you can tell me the error as well as how the screen looks.
-
This reply was modified 1 year, 3 months ago by
FrancoVisual.
Attachments:
You must be logged in to view attached files.2025-03-22 at 20:08 #143348If screen looks bad maybe it’s your fault setting 70nit brightness.
Nothing you attached (excluding extremely low brightness) shows a relevant issue2025-03-22 at 21:19 #143349And what value should I put 120? And how do I put it in DisplayCal? Now I attach a photo of what the screen looks like. I don’t know if the problem is the whites or the blacks, since my screen looks very white, especially considering that since they are OLED, they have pure blacks.
Attachments:
You must be logged in to view attached files.2025-03-23 at 13:02 #143351Put whatever you want to fit whatever your room conditions are to fix whatever you mean with that vage and empy sentence “I think but the screen looks pretty bad”
You do not need to put a whire level/brightness in DIsplayCAL, just put a confortable brightness value while you fix white point color. But you can set a value in whitel level if you need such guide, it will be informative: if yiu do not match taht white level in nits, displaycal will ignore it without further correction.
2025-03-23 at 17:22 #143353Please attach the actual profile, not screenshots of it.
2026-06-09 at 5:04 #145930Did you ever figure this out? I had a moment last week when I thought maybe, just maybe Calibrite Profiler finally got the job done, but it’s pretty clear after use next to a hardware LUT calibrated reference display that my QD OLED (also an MSI, but the 321URX instead) is undersaturated post-calibration. I would like to try using DisplayCal again, but the problem is that whenever I do, low-luminance, near-black values are too elevated. This occurs whether gamma 2.2 or sRGB is set for DisplayCal. DisplayCal also seems to want to undersaturate the QD-OLED’s colors, but less so than Calibrite.
Anyway, Vincent has a tendency to request calibration reports, but the issue for me (and I’m assuming for you as well) is that the calibration reports are always flawless. “100% sRGB space coverage with a super teeny tiny delta-e bla blah” yeah, sure, like my eyes are lying to me… lol. That kind of report is useless if the hardware you’re using to measure the report is the very same hardware you used to calibrate the ICC being reported on. It’s more or less the display equivalent of “we have investigated ourselves, and have found nothing wrong.”
I’m not sure what the extent of your issues were, but if you found any leads on a solution, I’m all ears. Thus far, trying to calibrate this QD-OLED monitor properly has been quite difficult. At the moment, from a combination of my calibration reports and my own two eyes, using my QD-OLED with a calibrated ICC is kind of like using an extremely accurate display that can only output 90% of what it claims to be capable of. Thus, on MacOS, if Im in a color managed app displaying sRGB, suddenly, it’s like my monitor is only capable of 90% sRGB compared to my 100% sRGB covered reference display sitting right next to it. And the same goes for P3-Wide. Again, I’ll use a color managed app, throw up a P3 image to cross-reference, and once again, it’s desaturated compared to reference.
It’s a QD-OLED. It’s MORE than capable of displaying the rest of those color spaces. But for some reason, Calibrite and DisplayCal both like to desaturate the ICC. Maybe they’re overcompensating for the extremely unique spectral behavior of the QD-OLED panel? I’m not sure.
Anyway, again, I’d like to use whichever calibration app gets me closest to the right results. So far, that app (despite its flaws) has been Calibrite Profiler. But if there’s a way to get it looking right in DisplayCal, I’d like to know, so I thought I’d ask. I’m desperate for a solution at this point
-
This reply was modified 2 weeks, 3 days ago by
Marcello Frisina.
-
AuthorPosts