- This topic has 3 replies, 3 voices, and was last updated 1 week, 2 days ago by
.
-
Posts
-
I have wide gamut display with 188% sRGB, 130% AdobeRGB, 133% DCI-P3 volume. Uncalibrated looks oversaturated in red colors. Calibrated looks, subjectively, OK for me. To have properly sRGB standard on wide gamut with Nvidia cards, it is recommend to handle ICM by novideo_srg, instead of using DisplayCAL for loading ICM with sRGB profile on monitor OSD. But this brings me to question: What’s the point of having wide gamut monitor and then clamp it to sRGB if I generally use color managed apps like Lightroom and Photoshop? Firefox should be colour managed as well. Shouldn’t be priority to edit in wider gamut and then soft proof in sRGB if needed?
Also… sRGB clamped by novideo_srgb looks too desaturated for me.
It looks exactly as it should.
Also… sRGB clamped by novideo_srgb looks too desaturated for me.
Also… sRGB clamped by novideo_srgb looks too desaturated for me.
It looks exactly as it should.
When using colorspace simulations the dafault display ICC profile in OS must be set to whatever you are simulating.
So on non color managed apps like games or Office “It looks exactly as it should”, but if you kept driver/EDID/custom display profile as default display profile Photoshop will belive that monitor is still widegamut (although you are simulating sRGB) and will color managed desaturating in excess.
The whole point of novideo_sRGB is to use it in non color managed apps, or maybe to use nvidie dither in GPU calibration while simulating an idealized version of display native colorspace, but using DWMLUT is wiser for that 2nd use.
