- This topic has 18 replies, 10 voices, and was last updated 6 months ago by
.
-
Posts
-
In which way? over or under saturated vs expected color.
Colors are undersaturated. From the test pattern, it looks like many colors are affected, not just one. What data do you want to look at? I can try to do some tests tonight.
A typical <USER> error is to profile in OSD preset native gamut, then switch to sRGB OSD mode while keeping custom ICC profile for that display in OS.
Display OSD mode & settings and profile walk together, change only one and configuration is no longer valid.Or Windows messing with HDR mode. All of these off on both sides, HW and SW.
I highly doubt it. I double-checked everything. The monitor is set to Custom Mode 1 – basically, user settings with adjustments. I don’t switch anything before or after.
HDR is disabled in Windows too. I even enabled it and then disabled it again.
Sorry for not providing the details earlier – I did not want to overtake this thread with my own issue. Can you send me a PM, maybe? If you have some time to help me out with this weird puzzle, that is.
In which way? over or under saturated vs expected color.
Colors are undersaturated. From the test pattern, it looks like many colors are affected, not just one. What data do you want to look at? I can try to do some tests tonight.
+
A typical <USER> error is to profile in OSD preset native gamut, then switch to sRGB OSD mode while keeping custom ICC profile for that display in OS.
Sound like that. Or that you are using some software layer by some laptop manufacturers like Asus to simulate sRGB on the fly on GPU, or that you are runing an user app doing that like AMD’s sRGB simulation, novideo_sRGB or something like that.
An HTML report without any simulation active will show this in CIE a*b* plot, undersaturation.
Using simulate sRGB but NOT use simulation profile as display profile will show also undersaturation close to what you see in PhotoshopAlso measuring raw RGB 0 255 0 on MS Paint and argyllCMS spotread app (with params “-x -X PATH_TO_CCSS_CORRECTION_FILE.ccss”) will show under saturation vs “illuminat relative green primary” from DIsplayCAL profile info an so on.
All looks like user misconfiguration or some rogue app simulating sRGB on that widegamut display
Is there a way to check from Apple Silicon mac info aobut outgoing video signal?
(My mbp has still Sonoma.)Equivalent what AGDCDiagnose used to be?
System Information used to tell bit depth and chroma sampling, but of course they had to take them away.
Frequently Asked Questions
“It is relatively straight-forward (although may require a little practice) to match two or more displays that allow sufficiently fine-grained white point adjustment via their hardware controls (note that adjusting the videoLUT channels via potentially available graphics card driver options will not work as it interferes with calibration that uses the videoLUT as well). Pick one display as the reference, display a white (or light gray) patch on both of them, making sure not much else is on screen that could be distracting, and then adjust the other displays to match the reference display. You can use the visual whitepoint editor of DisplayCAL to have a nice, distraction-free white patch on each display. Afterwards, calibrate and/or profile the adjusted display normally (it is important to set the whitepoint target for the adjusted display in DisplayCAL to “As measured”, and if you’re creating a 3D LUT, setting the 3D LUT rendering intent to “Relative colorimetric” so that calibration or the 3D LUT do not change the whitepoint).
If one or more of the displays do not offer sufficient whitepoint adjustment controls, you can use the visual whitepoint editor to do the adjustment in software instead. The process is almost the same, except that after you have achieved a visual match, you hit the “measure” button to measure the white and set it as calibration target instead of using “As measured”.You may be confused at this point and think, “but if we match the whitepoint by eye, doesn’t this make calibration and profiling redundant?”. The answer is, no it doesn’t, due to the way our visual system works, as described above, which perceives color relative to a white reference. Calibration and profiling will make sure that colors are reproduced correctly in relation to the whitepoint match we have just obtained.
I have been trying to match my two Philips monitors but can’t seem to get it right. I have tried to match the whitepoints visually and also using the the whitepoint editor to measure the correct value, but they are still a way off. I assume I have to calibrate the reference monitor first and then “measure” the whitepoint on the reference monitor. I also assume that all other settings for the calibration of the reference monitor are to be used on the second display. Any suggestions on where I am going wrong?
