Problem summary:
An extra key at frame 0 is added when a Table_Knob becomes animated
This is known to affect CameraTracker and Tracker nodes.
Customer reported version:
Nuke N/A
Customer reported platform:
N/A
Steps to reproduce:
1) Launch Nuke and create a Tracker node in the Node Graph
2) In the Properties panel, click the add track button
3) Right-click the created Track and select Delete key
4) Right-click the Track again and select Set Key
5) Observe how an additional keyframe is set at frame 0:
Expected behavior:
Adding a key or calling setAnimated() on a Table_Knob should not introduce any extra keyframes.
Actual behavior:
When a Table_Knob becomes animated, an additional keyframe appears at frame 0. This does not appear to depend on the timeline range.
Workaround:
No known workaround at this time.
Reproduced by Support in:
Nuke 16.0v6 - Windows 11, macOS 14 Sonoma
Nuke 15.0v1 - Windows 11
Nuke 14.0v1 - Windows 11
Nuke 13.0v1 - Windows 11
Earliest version tested:
Nuke 13.0v1 - This issue appears to be in all tested versions of the product
