ID 358350 - [Hiero/NukeStudio] When importing MXF footage, the clips 'reel' metadata value is not being interpreted within Hiero and Nuke Studio correctly.

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
Since the release of 11.1v2, Hiero and Nuke Studio have had the ability to import the MXF codec using footage from various sources, such as the Alexa, Sony and Panasonic cameras.

One issue that has been discovered recently, is that the 'reel' metadata is not being interpreted correctly within Hiero/Nuke Studio when importing MXF footage.

Note: This issue is isolated to the 'hiero/reel' metadata value in Hiero/Nuke Studio and works correctly within Nuke using the specific camera's metadata value.

Customer reported version
11.1v4

Customer reported platform
MacOS 10.12.6 (High Sierra)

Steps to reproduce

1) Create a new project Hiero/Nuke Studio in a release 11.1v2 (or after)

2) Import an MXF encoded file and drag the clip into the timeline to create a new Sequence.
Note: You can find an example MXF file to test from the Arri website below:
http://www.arri.com/camera/alexa_mini/learn/alexa_mini_sample_footage/

3) Switch the workspace to 'Conforming' (Shift + F1).
Result: In the Spreadsheet view, you will see that the 'Reel' table entry for the clip is empty
​

​

4) To confirm this is not only within the Spreadsheet:

a) Create a Text soft effect on the clip

b) In the message box, type in the following to call several metadata values

[metadata hiero/clip]
[metadata hiero/reel]
Result: No values are being relayed through the 'hiero/reel' metadata in the viewer, however the 'hiero/clip' values are.
​
​

5) To confirm this is isolated to the MXF format:

a) Import an alternative footage format that includes reel metadata, eg R3D.

b) Drag the new clip into the current Sequence (changing the footage to match the sequence if required)
Result: Reel value is present in Spreadsheet for new clip
​
​

6) To confirm the metadata reel value exists in the MXF clip

a) Switch to the 'Compositing' workspace

b) Import the original MXF clip into the Nodegraph

c) In the Read node's 'Metadata' tab scroll down until you see the Reel value.


In this example Nuke is interpreting the reel name using the 'arri/camera/ReelName' metadata value, but different camera's will have different value names.​

Workaround
The only current alternative is to encode the media to a MOV-based format, where Hiero/Nuke can read the reel information correctly.

Reproduced by support
This bug has been reproduced in:
Hiero 11.2v2 - Windows 7 - MacOS 10.12.6 - CentOS 6.9
Hiero 11.2v1 - Windows 7 
Hiero 11.1v4 - Windows 7 
Hiero 11.1v2 - Windows 7 - MacOS 10.12.6 - CentOS 6.9

Nuke Studio 11.2v2 - Windows 7 - MacOS 10.12.6 - CentOS 6.9
Nuke Studio 11.1v2 - Windows 7 - MacOS 10.12.6 - CentOS 6.9

Unable to reproduce bug in:
Hiero 11.1v1 - Windows 7 - MacOS 10.12.6 - CentOS 6.9
Nuke Studio 11.1v1 - Windows 7 - MacOS 10.12.6 - CentOS 6.9

Earliest version tested
Hiero 11.1v1
Nuke Studio 11.1v1
- Unable to import MXF files until 11.1v2 releases

Expected behaviour
Hiero/Nuke Studio should be able to interpret MXF reel metadata information

Actual behaviour
Hiero/Nuke Studio is currently unable to interpret MXF reel metadata information

    We're sorry to hear that

    Please tell us why