Problem summary
When creating a comp container from a timeline that contains several clips in excess of 1000+ frames, if the comp is opened within the Node Graph there will be a significant lag in the script.
It appears from testing that the comp container is waiting for actions in the timeline to occur, and once this occurs the comp will resume correctly.
Additional notes:
- Even if the shot being exported is short, it appears there is a calculation occurring on the timeline related to the longer clips causing the lag in the Node Graph.
- While this occurs in all three operating systems, it appears that in Linux and Mac it takes a more complex project and several longer shots for this to occur.
Customer reported version
nuke.12.2v3
Customer reported platform
n_a_linux
Steps to reproduce
1) Create a new project in Nuke Studio
2) Import several mid length clips (1-200) frames and several longer clips (1000-2000 frames)
3) Drag these clips in the timeline to create a new sequence
4) Select one of the shorter clips, right-click and select 'Effects, Create Comp'
5) After setting the location, double-click on the newly created comp container in the new track. Result: Lag occurs within the Node Graph when opened for a short duration.
Expected behaviour
No lag time when loading a comp container within Nuke Studio
Actual behaviour
Lag when opening a comp container in Nuke Studio
Workaround
Try to avoid using several 1000+ frame clips within Nuke Studio if you planning on opening the project via the comp containers.
Another option is to open the Nuke script's within a Nuke session outside of Nuke Studio.
Reproduced by support
This bug has been reproduced in:
Nuke Studio 12.2v3 - Windows 10 - MacOS 10.15.6 - CentOS 7
Nuke Studio 12.2v1 - Windows 10
Nuke Studio 12.1v1 - Windows 10
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.3v1 - Windows 10
Nuke Studio 11.2v1 - Windows 10
Nuke Studio 11.1v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10
Nuke Studio 10.5v1 - Windows 10
Nuke Studio 10.0v1 - Windows 10 - MacOS 10.15.6 - CentOS 7
Earliest version tested
Nuke Studio 10.0v1
- This issue appears to be in all versions of the product