ID 512579 - Nuke Studio/Hiero detects an incorrect frame range when reading ProRes MXF files from the ARRI cameras

Follow

Problem summary
Nuke Studio/Hiero detects an incorrect frame range when reading ProRes MXF files from the ARRI cameras. This issue has been reproduced with footage from the Arri ALEXA Mini LF and Arri ALEXA 35.
 
This issue only appears to happen when reading files into Nuke Studio/Hiero, and not in Nuke's Node Graph.
 
Customer reported version
Nuke 13.2v2
 
Customer reported platform
Windows 10
 
Steps to reproduce
 
1) Open Nuke Studio.
 
2) Import the attached MXF file (Import > Import File(s)...).
 
3) Double click the clip to open its Properties and notice the Original Range knob values.

 


4) Dropping the clip on to the timeline will also display most of the track item in red, as the frame range is incorrect.

 


 
Expected behaviour
Nuke Studio/Hiero should detects the correct frame range when reading ProRes MXF files from the Arri ALEXA Mini LF.

In this example, the frame range of the shot should be 1 - 259.
 
Actual behaviour
Nuke Studio/Hiero detects an incorrect frame range when reading ProRes MXF files from the Arri ALEXA Mini LF.

In this example, the frame range of the shot is detected as 1 - 112188.
 
Workaround
Pressing Rescan on the clip's Properties panel should correctly update the frame range.
 
Before:

 

 

After:

 


 
Reproduced by support
This bug has been reproduced in:

Nuke Studio 14.0v5 - Windows 10 - Linux CentOS 7
Nuke Studio 13.2v2 - Windows 10 - Linux CentOS 7
Nuke Studio 13.0v1 - Windows 10 - Linux CentOS 7 - Regression
 
Unable to reproduce bug in:

Nuke Studio 12.2v11 - Windows 10 - Linux CentOS 7
 
Earliest version tested
Nuke Studio 12.2v11
- This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why