- This topic has 11 replies, 3 voices, and was last updated 2 years ago by
.
-
Posts
-
Greetings. When I bought a new monitor, I first bought spyder-x pro and then i1 display plus because I wanted to get the closest possible colors on my 2 devices. Although I don’t understand most of the things, I read the posts on the forum and did something, but I wanted to open a topic to make sure I was right.
My Equipments and Softwares;
Windows 10 Pro 22H2, Latest DisplayCal and ArgyII CMS 3.2.0
MSI G274QPF-QD Qled, Dell SE2717H and i1 Display Plus
I accessed the ccss file of MSI G274QPF-QD from hardwareunboxed. I tried to calibrate it as I gave the pictures below. There is a problem with the blue color in a way I don’t understand.
My DisplayCal settings;
Verification Settings; (I made the verification files I produced using these settings. I don’t know if I did it right. )
Purpose; I want my two monitors to be as close as possible to the same colors at the standards they should be.
For example; I’m so used to using high nits on stock settings that I thought the monitor turned off when it dropped to 140 nits. I’ve been playing with i1 display plus for the past 2-3 days. In this process, I started to get used to it because I stayed as a result of the tests I did between 120-140.Can you help me with exactly which setting I should choose or change, like in for dummies books?
It is reading blue high lumance but its saturation is right. It does not have rec 709 blue. Quantum dot is wide gamut so fully covers rec 709 and more p3 than LED can. They never will look the same since they are different Technlogies. I do not know if blue is right but I would guess it is. The patterns will let your eyes see if the brightness of blue matches the white brightness using the color ramps. I do not think you can blue filter your screen though. Even a android phone can do a blue filter with the camera lens with the Thx tune up app on google store. https://www.avsforum.com/threads/avs-hd-709-blu-ray-mp4-calibration.948496/ .
Is it wierd that 22 greys are not as close as all the others to D65? 0,0,0 was measured 2 times and is in 2 spots. One close and one not as much. This is for the QD led. The other white led only has 5 greys not near d65.
Your desktop is not color managed so it will not look the same except in color managed apps. They both color calibrated and white balanced by xyz + matrix display profile. It is probably better to use single curve plus matrix color profile since it will not adjust blue as much but will make one color gamma for red , green and blue that fits. You can try that one curve color profile.
I’m very sorry, but I’m having a hard time catching what you’re talking about. If there is a problem, what exactly do I need to do? I realized that there might be a difference because of the Qled- WLed difference, but spyderx made one yellow and the other blue focused. I think there won’t be that much tonal difference, what is the path I should follow? In the pictures I shared 3 page settings I made in Displaycall. Are they wrong? Thank you so much for help
SpyderX Pro on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Don’t worry about the greys. The calibration did its best. There is no dummies for screen calibration. You have to understand lots of settings and testing and charts to understand. The mouse can zoom in on the SRGB color space chart. Everything is on the targets so its good. Blue is off a little. I guess google will find you some stuff. The blue is wrong in lumance-brightness the same as it is in the A and B of LAB. LAB is the toughest definition of color to understand. L is luminance. A and B are questions to me. A and B are coordinates on colorspace I think.
A simple profile might work better for both. Profile type on the 3rd picture is usually single curve + matrix and just 34 colors to test. If you test 89 colors it will do middle brightness of colors and a full brightness of colors and then calibrate.
Your calibration report should be unchecked simulation report srgb since the qled is not srgb. It is impossible to change native color. Using color managed apps the screens will be the same. There is things I missed since it is complicated. Is the ccss right? the report says “Correction:
LCD Quantum Dot LED (Samsung QLED Q9) <Samsung Q9 75_ (i1 Pro).ccss>” You settings page says it is MSI qled correction.First of all I see no point aiming to an sRGB TRC on a widgeamut that needs to be used color managed. Usually easier to aim to 2.2 relative closer to native gamma ramp.
Second if display is welel behaved it may be easier to aim to a 1 single curve + matriox + BPC profile. XYZLUT captures better display behavior but may lead to some rounding errors due to 3 independent TRC on some color managed apps.
And last, you are verifying display profile behavior on an hypotetical color managed app showing an sRGB image = predict which RGB triples “in gamut” colors are equivalent to sRGB colors.
High dE can be caused by profile not capturing actual display behavior (unlikely on an XYZLUT profile unless display is very unstable) or more likely due to out of gamut color.
You can use DisplayCAL profile info tool, sleect sRGB as reference and generate a 3D view (upper icons) so you can inspect in L*a*b* if there is a bit of sRGB blue outside 3D boundaries of your display gamut. Typical 2D plot cannot show it since you are seeing a 2D projection. That luminance difference reported by Ben is likely to be an out of gamut event, hence uncorrectable, but checkDon’t worry about the greys. The calibration did its best. There is no dummies for screen calibration. You have to understand lots of settings and testing and charts to understand. The mouse can zoom in on the SRGB color space chart. Everything is on the targets so its good. Blue is off a little. I guess google will find you some stuff. The blue is wrong in lumance-brightness the same as it is in the A and B of LAB. LAB is the toughest definition of color to understand. L is luminance. A and B are questions to me. A and B are coordinates on colorspace I think.
A simple profile might work better for both. Profile type on the 3rd picture is usually single curve + matrix and just 34 colors to test. If you test 89 colors it will do middle brightness of colors and a full brightness of colors and then calibrate.
Your calibration report should be unchecked simulation report srgb since the qled is not srgb. It is impossible to change native color. Using color managed apps the screens will be the same. There is things I missed since it is complicated. Is the ccss right? the report says “Correction:
LCD Quantum Dot LED (Samsung QLED Q9) <Samsung Q9 75_ (i1 Pro).ccss>” You settings page says it is MSI qled correction.
I have read a lot of threads on this forum and I don’t understand a lot of things. I think the level of English I know and the quality of the translation site is also a bit of a problem. I did a lot of tests before I started this thread, I think I uploaded the wrong one. I have added 2 more reports to the topic.
While I thought I was explaining things in a simple way that people around me did not know but I knew, I realized here how difficult it was for the person I was talking to. I also ask questions to Chatgpt 4o and I have an AMD card. I learned amd srgb emulation last night, and now I calibrated it that way. The colors are a little fainter, but I haven’t produced a test chart yet.
First of all I see no point aiming to an sRGB TRC on a widgeamut that needs to be used color managed. Usually easier to aim to 2.2 relative closer to native gamma ramp.
Second if display is welel behaved it may be easier to aim to a 1 single curve + matriox + BPC profile. XYZLUT captures better display behavior but may lead to some rounding errors due to 3 independent TRC on some color managed apps.
And last, you are verifying display profile behavior on an hypotetical color managed app showing an sRGB image = predict which RGB triples “in gamut” colors are equivalent to sRGB colors.
High dE can be caused by profile not capturing actual display behavior (unlikely on an XYZLUT profile unless display is very unstable) or more likely due to out of gamut color.
You can use DisplayCAL profile info tool, sleect sRGB as reference and generate a 3D view (upper icons) so you can inspect in L*a*b* if there is a bit of sRGB blue outside 3D boundaries of your display gamut. Typical 2D plot cannot show it since you are seeing a 2D projection. That luminance difference reported by Ben is likely to be an out of gamut event, hence uncorrectable, but checkThank you, Mr. Vincent. The reason why I tried to do this calibration thing and why I sold my spyder x and bought the i1 display plus was because I read your comments in past threads. Hopefully I will get to the point where I understand what you are talking about, thank you for your comments. I will learn the things you mentioned with Mr. Ben by searching the forum. Thank you for not leaving the subject unanswered.
I wish you healthy and peaceful days.
Oh, I got it. Now I understand. I didn’t pay attention to the profiling part because I memorized the menus like a robot. I’ll test it this way.
@Vincent I think you suggested srgb emulation for AMD in your comment to a few people. I finally found where it is, do you think I should use it this way?
Finally good results I guess. I chose Rec.709 and Gamma 2.2 for verification because I calibrated it to 6500k and gamma 2.2. I think it’s the right one.
2024-07-18 17:14:32; AMD rgb emulation ON
2024-07-18 17:35:15; AMD rgb emulation OFF
Oh, I got it. Now I understand. I didn’t pay attention to the profiling part because I memorized the menus like a robot. I’ll test it this way.
@Vincent I think you suggested srgb emulation for AMD in your comment to a few people. I finally found where it is, do you think I should use it this way?Only for gaming, assuming that native EDID xy coordinates are more or less accurate, that your display is set to an OSD mode in native gamut and that calibrated gamma is close to 2.2/sRGB.
Use HCFR or other software to track resulting gamma. I do not remember if AMD sRGB emulation also emulates sRGB TRC or leaves display as is.When you end the game, disable sRGB emulation. You cannot use AMD sRGB emulation and a custom native gamut ICC made with DisplayCAL with Photoshop or other color managed apps. Color managed apps will read that native gamut profile and color mamaged according to that, hence with AMD sRGB emulation active it wil look abnornally desaturated.
EDIT: I’ve not tested to enable AMD sRGB emulation and the profile in DIsplayCAL. It should work as a generic sRGB clamp. Of course you can use Photoshop with taht actiuve as long as you use the custom ICC profile made with sRGB emulation active.
High speed calibration takes less measurements in grayscale in calibration stage (before profiling). IDNK how well behaved is your uncalibrated monitor but as general rule I’ll aim for medium speed at least.
Anyway… it looks that sRGB/Rec709 blue is a little out of gamut. A way to test it is 3D view.
