I think it’s funny because I have gotten into red-cyan anaglyph stereograms both for screen and print and found that the more “advanced” hardware and techniques I use the worse results I get.
I have a high color gamut Dell monitor and what it does it takes (0, 255, 0) in sRGB space and turn it into something like (16, 186, 15) because the primaries are a little more saturated than the sRGB primaries. You wouldn’t want sRGB pure green turned into “hit by a green laser pointer green” would you?
The trouble is red got mixed in with my green so now there is a “ghost” image in the wrong eye.
If I view an image in a tk canvas on Windows, tk does no color correction so I don’t see the ghosts, but if I use a modern application like Photoshop or a web browser it does color correction and I do see them. I know I could get better results if I made an image in a high color gamut space but haven’t yet operationalized this because I’m more interested in print than screen at the moment. I was thinking pretty seriously of making a WebGL viewer that does the anaglyph processing in the browser but that’s a non-starter if I can only output in the sRGB color space.
As for print I have the same problems, I know I get worse results if I load a color profile for the specific paper I use and have Photoshop manage colors than if I set the printer to use ICM color calibration. I’m in the middle right now of setting up some controlled experiments that let me measure the ghosting caused by color “correction” which is not a “correction” at all for stereograms.
> making a WebGL viewer that does the anaglyph processing in the browser but that’s a non-starter if I can only output in the sRGB color space.
There's apparently now WebGL support for display-p3[1] on Chrome and Safari.[2] Anaglyph shaders can be straightforward[3] - I had fun playing with shallow-3D desktop UIs.
https://en.wikipedia.org/wiki/Anaglyph_3D
I have a high color gamut Dell monitor and what it does it takes (0, 255, 0) in sRGB space and turn it into something like (16, 186, 15) because the primaries are a little more saturated than the sRGB primaries. You wouldn’t want sRGB pure green turned into “hit by a green laser pointer green” would you?
The trouble is red got mixed in with my green so now there is a “ghost” image in the wrong eye.
If I view an image in a tk canvas on Windows, tk does no color correction so I don’t see the ghosts, but if I use a modern application like Photoshop or a web browser it does color correction and I do see them. I know I could get better results if I made an image in a high color gamut space but haven’t yet operationalized this because I’m more interested in print than screen at the moment. I was thinking pretty seriously of making a WebGL viewer that does the anaglyph processing in the browser but that’s a non-starter if I can only output in the sRGB color space.
As for print I have the same problems, I know I get worse results if I load a color profile for the specific paper I use and have Photoshop manage colors than if I set the printer to use ICM color calibration. I’m in the middle right now of setting up some controlled experiments that let me measure the ghosting caused by color “correction” which is not a “correction” at all for stereograms.