Quote - I'm confused

RV: The key lies in bb's statement:-

Quote - It doesn't have anything whatsoever to do with where you're plugging these values in. It has to do with what is the true numerical value you are trying to work with.

An example to illustrate:

Take a specific colour value: (0.5,1.0,1.0) - a light cyan. Suppose this same colour appears in two places in the calculation of diffuse colour in a particular (hypothetical) shader.

Firstly, it is intended to use a light cyan (to some extent) in the diffuse colour of the rendered surface. But your GC version of the shader will gamma correct that colour on output, so you should anti-gamma correct it on input.

But it is also used elsewhere in the shader to multiply the diffuse colour in order to reduce red channel intensity by 50%. In this case, you should not anti-GC it. If you do, you will reduce red channel intensity by around 78% (assuming GC=2.2).

A silly example maybe, but it illustrates the point that whether you Anti-GC or not depends on the purpose of each specific value within the calculation.

(Poser Pro provides a way to define a colour value to suit each of these purposes: the Simple_Color node is automatically anti-GC'd by Poser Pro, whereas a User_Defined RGB value is not.)

"If I were a shadow, I know I wouldn't like to be half of what I should be."
Mr Otsuka, the old black tomcat in Kafka on the Shore (Haruki Murakami)