ID 596453 - Reading/Writing MXF files produces additional details in the Terminal

Reading/Writing MXF files produces additional details in the Terminal

 

Customer reported version:
Nuke 16.0v1

 

Customer reported platform:
Windows 11

 

Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph.
2) Create a Write node, and set it to create an MXF file, such as: "C:/tmp/test_file.mxf"
3) Render the MXF and observe the Terminal output: [mxf @ 000001b1ffddc7c0] Encoder did not produce proper pts, making some up.
4) Create a Read node and select the MXF file, observing the Terminal output: [mxf @ 000001b1ffe2e040] Stream #0: not enough frames to estimate rate; consider increasing probesize

 

Expected behavior:
No additional information should be logged to the Terminal when Reading/Writing MXF files in Nuke.

 

When using MXF files, extra details are printed to the Terminal. Other observed messages besides those listed above include:

[mxf @ 000001b87e988200] wrapping of stream 0 is unknown[mxf @ 000001b87e988200] wrapping of stream 5 is unknown

 

[mxf @ 000001b87e988200] Could not find codec parameters for stream 0 (Video: none, none(progressive), 4096x2048): unknown codecConsider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options

 

[mxf @ 000002554c1879c0] "OPAtom" with 2 ECs - assuming OP1a

 

Workaround:
No known workaround at this time.

 

Reproduced by Support in:
Nuke Studio 16.0v4 - Windows 11, macOS 14 Sonoma

Nuke Studio 16.0v1 - Windows 10, macOS 14 Sonoma

Nuke Studio 15.2v1 - Windows 11 - Regression

 

Unable to reproduce in:
Nuke Studio 15.1v9 - Windows 11

 

Earliest version tested:
Nuke Studio 15.1v9 - This issue does not appear in this version and has regressed.