Problem summary: Visual artifacts can occur when rendering H.264 MOVs from certain scripts on macOS ARM builds of Nuke
This issue seems to affect both the "High 4:2:0 8-bit" and "Main 4:2:0 8-bit" H.264 Codec Profiles
Customer reported version: Nuke 16.0v1
Customer reported platform: macOS 15
Steps to reproduce: 1) Download the attached example_file.nk and launch the ARM version of Nuke on a macOS device 2) Open the example_file.nk 3) Navigate to Render > Render All Write Nodes... 4) In the dialog window, set the frame range to global (1-221) and press OK 5) Once the Render completes, View either Read node and observe how the rendered MOVs have visual artifacts:
Expected behavior: Rendered H.264 MOVs should align with that is displayed in the Nuke viewer, and not contain artifacts/corrupt pixels.
Actual behavior: When a H.264 Write node is rendered from a ARM build of Nuke on macOS, visual artifacts can occur in certain node configurations. Generally this seems to involve Merge nodes that are only active for a limited time, like when using a Switch node to bypass the Merge after a certain number of frames, setting an expression on the Merge node's disable knob, or setting the Merge node's Lifetime knobs.
Workaround: Setting the GOP to 1.
Reproduced by Support in: Nuke 16.0v4 - macOS 14 Sonoma (M1 ARM) Nuke 15.0v1 - macOS 14 Sonoma (M1 ARM)
Unable to reproduce bug in: Nuke 16.0v4 - Windows 11, macOS 14 Sonoma (M1 Intel) Nuke 15.0v1 - Windows 11, macOS 14 Sonoma (M1 Intel)
Earliest version tested: Nuke 15.0v1 - This feature (Native Apple Silicon Support) did not exist before this version
