ID 504933 - When Missing Frames is set to "nearest frame" and Localization Policy is set to "on" in the Read node, the Viewer will freeze on a random frame

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
When Missing Frames is set to "nearest frame" and Localization Policy is set to "on" in the Read node, the Viewer will freeze on a random frame.
 
Customer reported version
Nuke 13.1v3
 
Customer reported platform
MacOS 11
 
Steps to reproduce
 
1) Open Nuke, create a Read node, read in some footage and connect the Read node to the Viewer node.

2) In the Read nodes properties window, change the Missing Frames to nearest frame and the Localization Policy to on.

3) Wait for the footage to localize and then press Play.
 
Expected behaviour
The footage should play through to the end.
 
Actual behaviour
If the footage was not already localized then it will freeze on a random frame.
 
Workaround
Open the Read nodes properties window and press the reload button.
 
Reproduced by support
This bug has been reproduced in:
Nuke 13.1v3 - Windows 10 - macOS 10.15.3 - CentOS7
Nuke 13.1v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v1 - Windows 10 - macOS 10.15.3 - CentOS7
 
Unable to reproduce bug in:
Nuke 9.0v9 - Windows 10 - macOS 10.15.3 - CentOS7 - Regression
 
Earliest version tested
Nuke 9.0v1 - This issue doesn't appear in this version and has regressed
 
 

    We're sorry to hear that

    Please tell us why