HI everyone, when loading the color space node in nuke it seems not to pick up the input colorspace.
When looking at the code it says
# OCIOColorSpace
elif baking_colorspace["type"] == "colorspace":
baking_colorspace = baking_colorspace["colorspace"]
# format colorspace string with anatomy data
baking_colorspace = get_formatted_colorspace(
baking_colorspace, self.formatting_data
)
if not baking_colorspace:
raise ValueError(
f"Invalid baking color space: '{baking_colorspace}'"
)
node = nuke.createNode("OCIOColorSpace")
message = "OCIOColorSpace... '{}'"
# no need to set input colorspace since it is driven by
# working colorspace
node["out_colorspace"].setValue(baking_colorspace)
colorspace = baking_colorspace
else:
raise ValueError(
This file has been truncated. show original
but when i load the node it shows like this
it doesnt set the input colorspace according to default,
As far as I know, when loading via AYON loader, it follows this regex pattern in settings. this pattern is applied to the file path of the loaded product.
https://help.ayon.app/articles/2833967-nuke-addon-settings#0zt4kzwd4b4
The read node is proper it picks up the default color space, like so
Its only when i load the ocio color space node, that it doesnt pick up the default as the input,