The question is about the Gamma Cycles node.
In this period I am studying the linear workflow in Computer Graphics and how it is managed by Blender.
I noticed that Cycles automatically handles the jpg-png (sRGB in general) color space linearization process by simply setting "Color" in the image texture node.
While instead, we do not want to linearize to preserve sRGB we set "No Color Date".
That's what I thought I understood. Is it right?
The doubt comes to me, when I use the Gamma node. Theoretically if I insert 0.22 to a "Color Data" image (linearized by Cycles) I should get an sRGB image for manual conversion from Linear to sRGB (Color Management disabled). But the reverse thing is, the image is as dark as if I had inserted a double linearization (0.454545), the automatic cycles and my manual.
Theoretically, I expect the gamma node to work as in Nuke where (in a linearized space and then converted to sRGB in the preview) set at 2.22 I see a brighter picture.
In Blender, the accounts return me to setting the menagement color to "none" (Display Device) where the image is dark and contrasted, as does the Cycles internally.
But, I still do not understand the behavior of the Gamma node. Can anybody tell me what's going on internally and why?
Thanks for the answer, cegaton.
The things you said I understood. But, probably, I did not explain it well, the gamma blender node works differently than other programs. Here's an example.
This is the original image.
This is correct with a 0.454545 in Natron (dark image).
This is correct with a 0.454545 in Blender (brighter image).
0.454545 is the conversion curve to convert sRGB (2.22) so I expect the image to be darker, while in Blender it corrects it inversely.
The settings are identical. Both were interpreted as sRGB and then linearized and displayed sRGB but the gamma node works in reverse.