Got 3 calibration variables in the way for color correction. How to keep Win10 out of the loop as much as possible, and how to proceed with calibrating this thing when all panels are different?
Ok, I'm yet another person struggling with the color of a TN panel monitor (Dell S2417DG). The monitor is nearly in all ways spectacular, and one of the few 24" 1440p monitors out there.
However, the color desaturation in this monitor is a deal breaker, and I'm trying really hard to calibrate this thing to raise the colors out of "washed out". This particular TN monitor is known for having this problem, apparently worse than some other TN's, so I have to be careful.
A HUGE WRINKLE in all of this however is that I cannot figure out how Windows 10 handles its own calibration scheme. As near as I can figure out, it does this entirely before the nVidia drivers get ahold of the source information. It doesn't seem to directly teeth into the nVidia drivers themselves by "asking" it to adjust the settings for it.
So: If I use the windows 10 calibration [anti-]wizard and modify the Gamma control, I now have the following:
Win10 Gamma ---fed to---> nVidia Gamma ---fed to---> My monitor's Gamma
UGH! Is this right? This is akin to having a tape-deck ramp up its own volume and feeding it to an amp which feeds to a speaker that has its own volume control. Let's forget about games that try to assert their own calibration hooey for the time being.
Suggestions? Punt and go with 4ms IPS? It seems a shame: There just are no other 24" 1440 144+Hz monitors out there and I'll have to go with 27", and lower dotpitch.