ID 535814 - Specific knobs are missing when a MOV or MXF Write node is created with Nuke's Python interpreter on Windows

Problem summary:

Specific knobs are missing when a MOV or MXF Write node is created with Nuke's Python interpreter on Windows. This problem does not occur when running Nuke in Terminal mode (-t) or when using Nuke's Script Editor.

Customer reported version:

Nuke 13.2v3

Customer reported platform:
Windows 10

Steps to reproduce:

1) Download the attached WriteNodeTest.py file and open a Command Prompt.

2) Paste the following into the Command Prompt, after making the necessary adjustments:

C:\Program Files\Nuke<version>\python.exe" "C:\path\to\the\WriteNodeTest.py"

3) Launch Nuke and navigate to File > Run Script...

4) Select the WriteNodeTest.py file and open a Script Editor window to compare the results, pictured below:

Expected behavior:

Write nodes created with the same code should have identical knobs, whether the code was run via the Script Editor, Terminal mode (-t), or Nuke's Python interpreter.

Actual behavior:

On Windows, Write nodes with a MOV or MXF file_type are missing certain knobs when created with Nuke's Python interpreter. The full list of missing knobs is below:

MOV missing knobs:

mov32_new_qt_behavior, mov32_ycbcr_matrix, mov32_codec, mov32_codecoptions, mov32_pixel_format, mov32_fps, mov32_quality, mov32_keyframerate, mov32_audiofile, mov32_audio_offset, mov32_units, mov32_settings, mov32_write_timecode, mov32_advanced, mov32_flatten, mov32_use_format_aspect, mov32_ycbcr_matrix_type, mov32_write_nclc, mov32_write_gamma, mov32_write_prores, meta_codec, meta_encoder, format, mov64_format, codec, mov64_codec, fps, mov64_fps, dnxhd_codec_profile, mov64_dnxhd_codec_profile, mov64_dnxhr_codec_profile, mov_prores_codec_profile, mov_h264_codec_profile, mov64_pixel_format, mov64_quality, mov64_ycbcr_matrix_type, audiofile, mov64_audiofile, audio_offset, mov64_audio_offset, units, mov64_units, Advanced, mov64_advanced, dnxhd_encode_video_range, mov64_dnxhd_encode_video_range, dataRange, mov64_fast_start, writeTimeCode, mov64_write_timecode, gop_size, mov64_gop_size, b_frames, mov64_b_frames, mov64_bitrate_divider, mov64_limit_bitrate, bitrate, mov64_bitrate, bitrate_tolerance, mov64_bitrate_tolerance, quality_min, mov64_quality_min, quality_max, mov64_quality_max, mov64_write_nclc, bitrateTol, gopSize, bFrames, mbDecision, mov64_mbDecision, DNxHR_SDK_Version

MXF missing knobs:

mxf_video_codec_knob, mxf_op_pattern_knob, mxf_edit_rate_knob, mxf_codec_profile_knob, mxf_tape_id_knob, mxf_dnx_encode_video_range, mxf_advanced, dataRange, DNxHR_SDK_Version

Workaround:
No known workaround at this time.

Reproduced by Support in:

Nuke 14.0v3 - Windows 10

Nuke 12.2v4 - Windows 10 - Regression

Unable to reproduce bug in:

Nuke 14.0v3 - CentOS 7, macOS 11

Nuke 12.2v3 - Windows 10

Earliest version tested:
Nuke 12.2v3 - This issue doesn't appear in this version and has regressed

We're sorry to hear that

Please tell us why