ID 362175 - Stereoscopic Nuke scripts with only one view as an input, will error on rendering if a TCL expression is added before writing this single view
Problem summary
Within Nuke it is possible to read in, work on and render separate stereoscopic views (left, right).
There has been an issue discovered if one of the two views is not being Read in and the script contains either a TCL or Python operation an error will occur when rendered out as single view from a stereoscopic project. This occurs as the TCL/Python expression will attempt to apply itself to the empty view and create the following error:
Read error: No such file or directory
Note: this does not occur with a combined exr stereoscopic image, only if one view is imported into a stereoscopic script.
Customer reported version
nuke.10.5v5
Customer reported platform
n_a_linux
Steps to reproduce
1) Import just the left view of a stereoscopic image sequence into a left/right stereoscopic Nuke script
2) Within the Read node, ensure that the image is being interpreted as the respective channel, through either using the %v or %V extension.
Example: stereotest_%v.%04d.exr will interpret this as stereotest_left.0001.exr
3) Create a Text node and enter in any Python or Metadata through a TCL expression.
Example: [frame]
4) Create a Write node using the same conventions as the Read node, with a different name
Example: stereotestrender_%v.%04d.exr
5) Click Render, and in the dialogue box select just the 'left' view (see image below)
Result: Read error occurs
Workaround
There are two viable workarounds depending on workflow:
1) Within the Write node, change the views to only 'left' in the preferences before rendering.
or
2) Create a 'JoinViews' node before the Write node, ensuring that the 'right' view is not connected to anything. This will force the TCL to only apply to the left view during the render.
Reproduced by support
This bug has been reproduced in:
Nuke 11.2v3 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Nuke 11.2v1 - Windows 7
Nuke 11.1v5 - Windows 7
Nuke 11.1v1 - Windows 7
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.5v7 - Windows 7
Nuke 10.5v1 - Windows 7
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v7 - Windows 7 - CentOS 6.9 - MacOS 10.13.4 - regression
Unable to reproduce bug in:
Nuke 9.0v6 - Windows 7 - CentOS 6.9 - MacOS 10.13.4
Earliest version tested
Nuke 9.0v6
- This issue no longer appears in this version and has regressed
Expected behaviour
The TCL expression should not be causing an error by writing to a view that is not present
Actual behaviour
The TCL expression writes to a view that is not present, causing an error and not allowing the rendering of frames for either view.
