Quote - The biggest advantage compared with shaders is that gamma correction may be processed for each color individually.

After I'm ready with this version, I'll make a version based on Poserfiles (scene, character, prop, material). Any texture found in this file is loaded then, can be corrected, saved (with another filename) and a version of this file is saved with the new/modified textures attached.

ADP - I saw your new script - very nice - thank you for that.

I just want to clarify something here. You said "The biggest advantage compared with shaders is that gamma correction may be processed for each color individually."

You seem to be saying that I am somehow not processing each color individually in the shader. But I am processing each channel individually. That is what Color_Math nodes do. You define an operation and it performs them individually on all three channels, then assembles the resulting color from the 3 internal calculations.

So, a Math_Color:Pow(er) node raises each Channel of Value_1 to the power indicating by the corresponding channel in Value_2. As I'm using it, I put WHITE (1, 1, 1) in Value_2 and then connect that to a math node that equals 2.2. So the power is the vector RGB(2.2, 2.2, 2.2).

There is no reason to do it, but you can actually raise each channel to a different power, using different RGB values in Value_2.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)