Problem summary Scripts containing a Retime node, with its 'before' knob set to 'black', and a Kronos node downstream fail to render. When rendering in the GUI, the render will stop with no warnings/errors displayed. However, rendering via command line displays an error like the following:
Warning: Retime4: Interest(channels=0xf), but request() not called.
Scrubbing the timeline also seems to not correctly update the image in the Viewer - previous frames are displayed when scrubbing over the black frames.
Customer reported version N/A
Customer reported platform N/A
Steps to reproduce
1) Open NukeX.
2) Read in some footage.
3) Create a Retime node downstream from the Read node.
4) Check the output range knob and set its value to a frame outside of the Read node's original frame range. For example 1001.
5) Also set the before knob to black.
6) Adjust the frame range on the Root node (Edit > Project Settings), so there are some black frames at the beginning of your frame range.
7) Add a Kronos node downstream from the Retime node.
8) On the Kronos node, press the Reset button next to the Input Range.
9) Create a Write node and set it to write out an EXR sequence.
10) Render the Global frame range (so including some black frames).
Expected behaviour The sequence should be rendered.
Actual behaviour Scripts containing a Retime node, with its before knob set to black, and a Kronos node downstream fail to render.
Workaround Setting the Retime's before knob to hold or continue seems to prevent the issue.
Reproduced by support This bug has been reproduced in: Nuke 13.1v1 - Windows 10 - Linux CentOS 7 - macOS 10.15 (Catalina) - Regression
Unable to reproduce bug in: Nuke 13.0v6 - Windows 10 - Linux CentOS 7 - macOS 10.15 (Catalina)
Earliest version tested Nuke 13.0v6 - This issue doesn't appear in this version and has regressed