State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:612468|
Customer reported version
Nuke 16.0v8
Customer reported platform
macOS 14
Steps to reproduce
1) In Nuke, create a Checkerboard node.
2) Create a Write node with a file path, and set the file type to .mov
3) Set the codec to H.264, then expand the Advanced knob.
4) Change the GOP to 0 and render a frame.
5) Read the rendered file back into Nuke, observing performance.
Expected behavior
Nuke should remain stable and open and display the Read node, error with a message, or prevent users from setting the GOP value to 0.
Actual behavior
Nuke hard crashes when reading in a H.264 file that was written with Advanced > GOP set to zero (0). Previous versions allowed the file to be read in without crashing and displayed an error message: "Invalid data found whne processing input"

In addition to the crash, the following output is seen in the Nuke console:

Workaround
There is no available workaround at this time.
Reproduced by Support in:
Nuke 16.0v8 - Windows 10/11, Rocky 9
Nuke 16.0v1 - Windows 10/11, Rocky 9
Nuke 15.2v1 - Windows 10/11, Rocky 9 - regression
Unable to reproduce bug in:
Nuke 15.1v10 - Windows 10/11, Rocky 9
Earliest version tested
Nuke 15.1v10 - This issue doesn't appear in this version and has regressed
We're sorry to hear that
Please tell us why