Problem summary Frame Range nodes display 1-1 for frames when downstream of specific Deep nodes.
When using a 'DeepRecolor' node, the frame range will be reset from the image source to '1-1' when adding a 'FrameRange' node.
Customer reported version
Nuke 11.1v1
Customer reported platform
Ubuntu
Steps to reproduce
1) Create a DeepRead node and add deep footage.
2) View the frame range for the DeepRead node in the Properties bin.
3) Create a FrameRange node downstream and view the frame range output.
4) Add a DeepReformat node then another FrameRange node, observing the frame range output.
Reproduced by Support in:
Nuke 15.1v1 - Windows 10, macOS 13 Ventura
Nuke 12.0v1 - Windows 10, macOS 13 Ventura
Earliest version tested
Nuke 12.0v1 - This issue occurs in all tested versions of the software.
Expected behavior
Deep nodes should not change the frame range when using a FrameRange node.
Actual behavior
Specific Deep nodes cause input values to become 1-1 in both the 'FrameRange' node in the GUI and when the 'node.frameRange ()' callback is used. The Deep nodes affecting the FrameRange node include: DeepFromFrames, DeepRecolor, DeepReformat, DeepToPoints, DeepTransform.
Workaround There is no available workaround at this time.