Problem summary
When using the 'Read File' option within Nuke's Write node, the node looks at the exported EXR's metadata node_hash value to link to its input node.
This works as expected for NUKE Colorspace Management workflows.
For OCIO Colorspace Management workflows, the export does not set a correct node_hash value, leading to the feature becoming unusable.
Screenshot Reference:
Customer reported version
Nuke 11.2v5
Customer reported platform
CentOS 6
Steps to reproduce
1) Open Nuke, setup Colorspace Management to OCIO
2) Create a simple script with a Write Node
3) Render the Write node as an EXR
4) After rendering successfully, select the 'read file' checkbox within the Write node
Result: The Write node will display an exception stating that the input hash does not match the EXR.
Doing the same reproduction above with NUKE Colorspace Management provides the correct result.
Workaround
Unknown.
Reproduced by Support in:
Nuke11.3v1- Windows 7 - Mac10.13 - CentOS7
Nuke11.2v1 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v1 - Windows 7
Nuke10.5v1 - Windows 7
Nuke10.0v1 - Windows 7 - regression
Unable to reproduce bug in:
Nuke9.0v9 - Windows 7 - Mac10.13 - CentOS7
Earliest version tested
Nuke 9.0v9 - This issue no longer appears in this version and has regressed ( OCIO Colorspace UI was rehauled with Nuke10.0 )
Expected behavior:
Exported Image metadata node_hash should match Write node's input node.
Actual behavior:
Exported Image metadata node_hash does not match, causing exceptions.
