AY-6611_Hiero to Nuke colorspace

[ynbot]

Please describe the issue you have acountered?

It seems the color management in Hiero isn't working correctly with the OCIO environment variable. It looks like the Hiero AYON Color management isn't properly activated. As a result, incorrect colorspace names are used during publishing from Hiero, and these aren't recognized by the Nuke loader. This causes the read nodes to use default settings.

How to replicate the issue?

No response

Additional context:

link to discussion on Discord (might be a private channel)

This issue was automatically created from Clickup ticket AY-6611

[jakubjezek001]

I was communicating with client and tried to investigate what could be the root cause for this issue. Here is the communication https://discord.com/channels/517362899170230292/1264903363959455774/1292822886435786764

[robin-ynput]

I continued investigating this issue and could get to the following conclusion, this triggers more question on my side actually.

0. Consistent OCIO config is properly loaded for the client on both Hiero and Nuke
1. When working in Hiero the client manually changes the colorspace set for the EXR input as something else different then default scene_linear
2. He then goes on an publishes the result as plate
3. When loading the resulting plate EXR in Nuke, he expects the OCIO colorspace previously set manually in Hiero to show up automatically in Nuke and mentions this might be a broken feature that used to work before

Investigation on the Loading side:

• on clip load, Nuke reads input colorspace from representationData["colorspaceData"] (or alternatively representationData["colorspace"] and version_entity["attrib"].get("colorSpace") flagged as backward compatible) https://github.com/ynput/ayon-nuke/blob/develop/client/ayon_nuke/plugins/load/load_clip.py#L533

• on clip load, Hiero reads input colorspace from version_entity["attrib"]["colorSpace"] only https://github.com/ynput/ayon-hiero/blob/aec1c8ffa711c7f34f458a8bbf931ccd6c90b523/client/ayon_hiero/plugins/load/load_clip.py#L96

Investigations on the publishing side:

• The colorspace information seems correctly set in versionData through the collection. But this is not a place any of the loaders attempt to reach for. https://github.com/ynput/ayon-hiero/blob/aec1c8ffa711c7f34f458a8bbf931ccd6c90b523/client/ayon_hiero/plugins/publish/precollect_instances.py#L161

• The Extract Colorspace Data plugin is properly called from the exr representation of the plate but seems completely stangers to the source colorspace set in the Host. It only validates global project OCIO config path and files rules set. https://github.com/ynput/ayon-core/blob/360a7d2d8dab3c5f6ea15439355565fcbc1f85d2/client/ayon_core/pipeline/colorspace.py#L1222

Questions

• Am I missing anything obvious here ?
• Should it work via the backward version_data entry hence updating the loading code ?
• Should it be somehow part of the Extract Colorspace data logic and we are missing source specific logic in the publisher ?