Problem summary
Exporting an ARRI MXF file as an EXR sequence results in incorrect arri/optics/lens_state metadata values.
The first few frames of the EXR sequence do not seem to update at all, when these metadata values change per frame.
This issue effects both rendering from Nuke and Nuke Studio/Hiero.
It seems that the issue may be on the first rendered frame but having rendering via the frame server makes the issue worse (as each worker process will have this problem on its first frame).
Customer reported version
Hiero 15.1v3
Customer reported platform
macOS 13
Steps to reproduce
1) Open Nuke.
2) Read in the attached MXF file.
3) Create a Write node, and set the file path to write out an EXR sequence.
4) On the Write node, change the metadata knob to all metadata.
5) Export a number of frames, in this example I wrote out frames 60-70.
6) Read in the exported EXR sequence and compare the two sets of metadata. You can compare the metadata of the 2 shots in the metadata panel.
Expected behaviour
The metadata on exported EXRs should match the original MXF file.
Actual behaviour
Exporting the MXF out as an EXR sequence results in mismatching metadata values.
The first four frames of the EXR sequence (numbered frame 60-64) seem to have the metadata from the first frame of the MXF file. After this, there still seems to be a mismatch.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v3 - Windows 11 - macOS 12
Nuke 14.1v1 - Windows 11 - macOS 12
Earliest version tested
Nuke 14.1v1
- The file format was not supported before this version.
