SYMPTOMS
When Tracker nodes are present in a script, Nuke can frequently become unresponsive for a few seconds or be slow to work with. This happens specifically when the Tracker nodes are generating preview patches for keyframes. Keyframe preview task messages can also appear when performing other tasks like rendering, and cause a significant slowdown.
CAUSE
Preview patches for the tracking keyframes (which appear at the top of the Viewer window during tracking) are pulled in from the upstream node tree, so all operations happening above the Tracker node are applied to the patches.
If there are a lot of keyframes, or CPU expensive operations above the Tracker node, it can take a long time to rebuild the patches for preview.
RESOLUTION
If you are experiencing slowdown with a similar setup, then please try turning off the keyframe previews during tracking.
You can turn off the keyframe previews in the Settings tab of the Tracker node by setting the following two options (which are highlighted red in the image below):
- Settings tab > General > show zoom window to never
- Settings tab > Keyframe Tracking > keyframe display to none
When you are doing hand-tracking, you can disable keyframe patch creation by turning off "create new key when track is moved" (highlighted below in yellow):
If this doesn’t stop Nuke from becoming unresponsive, the UI freezes might be related to the autosave functionality in Nuke. For more information, please see the following article:
Q100199: Slow performance/UI freezes when working with scripts that contain Tracker nodes
FURTHER HELP
We're sorry to hear that
Please tell us why
For more information on how to open a Support ticket, please refer to our Q100064: How to raise a support ticket article.