Problem summary Adjusting the pattern and search areas of the Tracker node's track anchor creates a keyframe on the frame number that is set on the Tracker node's reference frame knob. By default, this is set to 1.
Customer reported version N/A
Customer reported platform N/A
Steps to reproduce
1) Open Nuke.
2) Create a Constant node.
3) Downstream from the Constant, create a Tracker node and view it.
4) Go to any frame that is not frame 1.
5) In the Tracker node's properties, click add track.
6) Adjust the size of the pattern and search areas of the track anchor in the Viewer. NOTE: You may need to adjust the pattern and search areas multiple times before the issue occurs.
Expected behaviour The Tracker node should only add key frames on frames where the user has moved/resized the track anchor.
Actual behaviour The Tracker node adds a key frame at frame 1, or your reference frame, when the pattern and search areas of the track anchor have been resized on a different frame.
Workaround Unknown.
Reproduced by support This bug has been reproduced in: Nuke 14.0v5 - Windows 10 - CentOS 7 Nuke 14.0v4 - Windows 10 - CentOS 7 - REGRESSION
Unable to reproduce bug in: Nuke 14.0v3 - Windows 10 - CentOS 7
Earliest version tested Nuke 14.0v3 - This issue doesn't appear in this version and has regressed