Problem summary
The "nearest frame" fails when expressions are used for the file knob when viewed outside a group/gizmo.
Customer reported version
nuke.13.2v1
Customer reported platform
windows10
Video:
Steps to reproduce
1) In Nuke, load the attached script.
2) Double-click the Group node and select the file knob to browse for the file.
3) Update the Group node frame range > First to frame 1124
4) Select the correct file, then view the Group node.
5) Update FrameSlider_Range to 'Visible'
6) Playback the Viewer and observe any errors.
7) Go to a frame outside the original frame range of the footage, then click Reload in the Properties bin for the Read node.
Expected behavior
The error should not appear for the incorrect frames when 'nearest frame' is chosen for the missing frames knob while using an expression in the file path.
Actual behavior
An error appears in the Viewer as: "ReadError: No such file or directory." However, sometimes scrubbing the timeline makes the error go away.
Workaround
Using the direct path to the file works without erroring.
Reproduced by Support in:
Nuke 13.2v1 - Windows 10, CentOS 7
Nuke 13.1v1 - Windows 10,
Nuke 13.0v8 - Windows 10
Nuke 13.0v2 - Windows 10, CentOS 7 - regressions
Unable to reproduce bug in:
Nuke 13.0v1 - Windows 10, CentOS 7
Earliest version tested
Nuke 13.0v1 - This issue doesn't appear in this version and has regressed