double-check that the regression is correct (in terms of version). Also take a look at bugs with the 13.1v2 backport tag.
If it turns out that this is a feature request, let's revisit our estimation and re-write the ticket.
Problem summary
The sidecar file path is muxed between different Read data causing a failure in the Cryptomatte node.
Customer reported version
Nuke 13.1v3
Customer reported platform
Linux
Steps to reproduce
1) In Nuke, read in a Cryptomatte exr with a sidecar metadata. ex: https://github.com/Psyop/Cryptomatte/tree/master/sample_images/sidecar_manifest
2) Read in any other image file from a different directory than the where the Cryptomatte file resides. ie. C:\Users\USERNAME\Desktop\
3) Add a Copy node and adjust the knobs to remove any channels, set Layer Copy to All. Set BBox side to A, metadata to A and range A.
4) Add a CopyMetaData node and have Input A for the Read2 node and Input B for the Cryptomatte .exr 'Read1'.
5) Create a Cryptomatte node downstream and view the sidecar file path., then View it by pressing 1 on the keyboard.
6) Swap the Copy node inputs (Shift+X) and observe the Viewer and Cryptomatte node sidecar filepath for changes.
Expected behavior
The filepath should understand the relative input for the data used in the Cryptomatte node for merged layer inputs.
Actual behavior
The sidecar file path is interweaved between both inputs for the metadata of the Cryptomatte .exr and the additional input from the Copy source A. The error appears in the Viewer as: Cryptomatte2: "manifest.json" is not a valid sidecar manifest file path.
Workaround
There is no available workaround at this time.
Reproduced by Support in:
Nuke 13.2v2 - Windows 10, CentOS 7
Nuke 13.2v1 - Windows 10
Nuke 13.1v5 - Windows 10
Nuke 13.1v2 - Windows 10, CentOS 7 - regression
Earliest version tested
Nuke 13.1v1 - This issue doesn't appear in this version and has regressed
