Hello,
I’m having issues getting consistent values for colourspace in a flame batch.
I have a project set up using ocio config 1.2 set in the OCIO variable. I have a PyWriteFileNode (which inherits from PyNode) linked to a read node. In the batch window the read node shows a colourspace of “acescg”. However, the new colour_space property doesn’t seem to work;
import flame
n = flame.batch.nodes[-2]
print(n.type, n.colour_space)
# 'Write File' None
If I use the workaround I implemented for <2026, I get the expected value;
import flame
from pathlib import Path
n = flame.batch.nodes[-2]
n.media_path_pattern = "<colour space>"
colour = Path(n.get_resolved_media_path(show_extension=False)).stem
print(colour)
# acescg
However, if I use a colour management node and transform the colourspace with ACES > ACES - ACEScc I get a different result;
print(colour)
# ACES_-_ACEScc
And then if I access the colourspace from metadata I get a different value again;
print(n.get_metadata()['autodeskColorSpace'])
# ACEScg
Which is not only in yet another format, but is now also incorrect, because in the previous step I set the colourspace to ACEScc, not ACEScg.
Metadata accuracy aside, these kinds of format changes make it really difiicult for pipeline to manage tooling.