Problem summary
Nuke prints the error "mov64Reader Reader failed to read frame: End of file" when working with footage that starts at frame 0.
Customer reported version
nuke.10.5v5
Customer reported platform
10.11
Steps to reproduce
1) Launch Nuke and read in a .mov or .mp4 file that begins at frame zero.
2) Press the play button on the timeline and note that when the footage gets to the last frame in the sequence it will print the error. "mov64Reader Reader failed to read frame: End of file"
Workaround
Create a timeoffset node and compensate for the 0 frame
Adjust your project settings to offset by one frame and then subtract the final frames where the error is printed.
Reproduced by support
This bug has been reproduced in:
Nuke11.0v3 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke11.0v1 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke10.5v7 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke10.5v1 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke10.0v7 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke10.0v1 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke9.0v9 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Nuke9.0v1 - MacOSX 10.13 - Windows 10 - Linux CentOS 7.4
Unable to reproduce bug in:
Nuke 8.0v7- MacOSX 10.13 - Windows 10 - Linux CentOS 7.4 (Regression)
Earliest version tested
Nuke 8.0v7- MacOSX 10.13 - Windows 10 - Linux CentOS 7.4 (Regression)
Expected behaviour
Nuke would compensate for the footage starting at frame 0 and set it's default frame to frame 0, or offset one frame to match the footage.
Actual behaviour
Nuke offsets the footage to frame one, but does not compensate for frame 0 resulting in the last frame of the footage being a null frame, which in turn prints the error.