Advancing the State of Color Management in Windows
devblogs.microsoft.comFrom time to time I have the experience that "without color management your colors sometimes come out correctly but with color management colors always come out wrong".
Back in the 1990s it was discovering that it was a lot easier to make images for the web with the GIMP as opposed to Photoshop because Photoshop, designed for print, would gamma "correct" images incorrectly.
More recently I've been into
https://en.wikipedia.org/wiki/Anaglyph_3D
and had myself scratching my head about how things looked on my wide color gamut monitor until I discovered that, for my case, the wide gamut makes things worse instead of better.
If I compose images with PIL and display them in a tkinter app, a color value like (0,180,0) really is sent as (0,180,0) to the OS and then to the monitor and they appear as (0,180,0) in a screenshot.
If I save that image as a JPG or PNG and view it in Photoshop, a web browser, or windows photoviewer, that (0,180,0) is treated as sRGB so it is converted to something more like (16,176,16) by the application before it hands the image to Windows because the green on the wide gamut monitor is more spectrally pure than the sRGB green so it adds a little red and blue.
Without the 3-d glasses this makes the green look more like the sRGB green but with the 3-d glass it adds a little bit of red light that forms a "ghost" image that damages the 3-d perception.
This effect is very hard to "undo", if I were working in Photoshop I could attach a color profile to the image that would tell it the green primary is supposed to more pure and I might really get something like (2,179,3) sent to the monitor. A web browser always works in sRGB so there is no way to prevent wide gamut displays from vandalizing my stereograms on the web.