Problem summary When exporting a clip from Nuke Studio to be created as a comp, you will be required to generate both a project file and a Write node, then have these linked.
By default this is setup in the 'Nuke Basic Shot' preset.
We have recently discovered that if both the project file and Write node are in the same location, with the frame padding (####) removed, this will cause a python recursion error.
This python recursion exceeded error will run through the log and cause and error when exporting the preset.
Note: This error occurs in Nuke 11.1v1 releases and later over all three operating systems and using either the 'Export' or 'Create Comp' options.
Customer reported version nuke.12.2v3
Customer reported platform windows10
Steps to reproduce
1) Open a new Nuke Studio session (11.1v1 or later)
2) Import and drag a clip into the timeline, to create a new sequence
3) Right-click on the clip in the sequence, and select 'Create Comp Special' (setting a directory if prompted)
4) Within the 'Basic Nuke Shot' export preset, select the 'Nuke Project File' structure and move it within the 'renders' directory above or below the 'Write node'.
5) Alter the Write node from a 'dpx' format to 'mov' (which does not require padding)
6) Remove the frame padding (####) from the Write node structure Result: Recursion occurs in log
7) Click 'Create Comp' Result: Error message
Expected behaviour recursion python error should not occur and not block the exporting of the comp
Actual behaviour recursion python error occurs and stops the comp from being created.
Workaround There are two workaround to this issue:
1) Retain the frame padding. The mov and mxf writers do not interpret the hashes and they do not get added to the output file.
2) If you want to remove the frame padding, ensure that the project file and Write node are being written to two separate folders
Reproduced by support This bug has been reproduced in: Nuke 12.2v3 - Windows 10 - MacOS 10.15.6 - CentOS 7 Nuke 12.2v1 - Windows 10 Nuke 12.1v1 - Windows 10 Nuke 12.0v1 - Windows 10 Nuke 11.3v1 - Windows 10 Nuke 11.2v1 - Windows 10 Nuke 11.1v1 - Windows 10 - MacOS 10.15.6 - CentOS 7
Unable to reproduce bug in: Nuke 11.0v4 - Windows 10 - MacOS 10.15.6 - CentOS 7
Earliest version tested Nuke 11.0v4 - This issue doesn't appear in this version and has regressed
