Problem summary:
A "Could not create reader" error occurs when loading ARRI Alexa 35 MXF footage in Terminal or Execute mode
Customer reported version:
Nuke N/A
Customer reported platform:
Windows 10
Steps to reproduce:
1) Launch Nuke and create a Read node in the Node Graph.
2) Select some ARRI Alexa 35 .MXF footage and click Open.
3) Navigate to File > Save Comp As..., and Save the Nuke script to a location of your choice.
4) Close Nuke and open a Command Prompt or Terminal window.
5) Use the -t command line flag to launch Nuke and open the file saved in step 3. The full command should look something like this: "C:\Program Files\Nuke14.0v4\Nuke14.0.exe" -t \path\to\script.nk
6) Observe the error message, ERROR: Read1: Could not create reader:
Expected behavior:
Opening a Nuke script without using the GUI should not report any additional errors.
Actual behavior:
Opening a script containing ARRI Alexa 35 MXF footage without the GUI produces a "Could not create reader" error. However, it seems as though it's still possible to render the file successfully from Terminal (-t) or Execute (-x) mode, despite the error message.
Workaround:
No known workaround at this time.
Reproduced by Support in:
Nuke 14.0v4 - Windows 10, CentOS 7
Nuke 14.0v3 - Windows 10
Nuke 14.0v2 - Windows 10, CentOS 7 - Regression
Unable to reproduce bug in:
Nuke 14.0v1 - Windows 10, CentOS 7
Earliest version tested:
Nuke 14.0v1 - This issue doesn't appear in this version and has regressed
