ID 357368 - Adding key frames to a Tracker or CameraTracker node via Python is very slow

Follow

Problem summary:
Adding key frames to a Tracker or CameraTracker node via Python is very slow.

Customer reported version:
Nuke 11.1v4

Customer reported platform
Windows 10

Steps to reproduce:
This example script shows a script that generate 10 tracks and keyframes them for 1000 frames

1) Open Nuke
2) Open the Script Editor and run the attached script
3) Notice that it takes a very long time to generate the keyframes - this has been timed at around 5 and a half minutes

Reproduced by Support in:
Nuke 11.2v1 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 6
Nuke 11.1v4 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 11.0v4 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v7 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v6 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v8 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v7 - Windows 10
Nuke 8.0v1 - Windows 10
Nuke 7.0v10 - Windows 10 - macOS 10.13 (High Sierra) - Linux CentOS 6

Earliest version tested:
Nuke 7.0v10 - This issue appears to be in all versions of the product

Expected behavior:
The key frames should be generated within a reasonable amount of time.

Actual behavior:
It takes over 5 minutes to generate the key frames.
 

    We're sorry to hear that

    Please tell us why