State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:154045|
Problem summary
When a cv or point on a Bezier is modified, a new keyframe will be set. This allows for the modification of points over time to create accurate shapes for rotoscoping.
If the user would like to change the cv or point over all keyframes, it is possible to do this by activating the 'ripple edit' button within the bezier's options.
It has been discovered though that if a cv or point is created from a selected shape after the ripple edit has been activated, this will not correctly propagate as expected to the other set keyframes.
Customer reported version
nuke.n/a
Customer reported platform
n_a_mac
Steps to reproduce
1) Create a Roto node
2) On frame 1, draw a simple Bezier shape
3) Move the timeline slider to frame 100, and alter the position of the shape setting a keyframe.
4) With the Bezier shape still selected, move the timeline slider to frame 50
5) Turn on ripple editing in the bezier options
6) Ensuring the bezier shape is still selected, add a new cv using the ctrl+alt (PC) or alt+cmd (Mac) shortcut
7) Modify this newly created cv
Result: When moving the timeline slider back to either frame 1 or 100, the cv moves back to the original position, and does not ripple correctly through these set keyframes.
Expected behaviour
When the ripple edit function is active, it should ripple
Actual behaviour
what actually happened
Workaround
If the cv is created, then the shape is deselected, when modified the cv will ripple correctly through all keyframes
Reproduced by support
This bug has been reproduced in:
Nuke 13.0v2 - Windows 10 - MacOS 10.15.6 - CentOS 7
Nuke 13.0v1 - Windows 10
Nuke 12.2v1 - Windows 10
Nuke 12.1v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10
Nuke 9.0v1 - Windows 10
Nuke 8.0v1 - Windows 10 - MacOS - CentOS 7
Earliest version tested
Nuke 8.0v1
- This issue appears to be in all versions of the product
We're sorry to hear that
Please tell us why