Bug: Clip motion position disobeys keyframes
Steps to reproduce:
- Throw any clip on your timeline
- Add 3 Position keyframes. (The bug is more obvious if they're several seconds apart.) Confirm the position values for all are the default 960,540.
- Change the position value for the 1st keyframe to 960,0
- Change the position value for the 2nd keyframe to 950,540
Play and behold... between the 2nd and 3rd keyframe, the clip moves in the Y axis!
And yet the 2nd & 3rd keyframes are from 950,540 to 960,540. So instead of a slow movement to the right, it's adding a down&up movement (my Y value peaks at 579.9 before returning to 540).
- This has been in Premiere forever, and I just tested the same behavior in CC2018 and the latest CC2020.
- If you try to force a "fix", e.g. adding a 955,540 keyframe in between, Premiere will defy you, doing the same up&down maneuver twice now... so you can slice&dice it ad infinitum.
- I used to think it had to do with bezier algorithms I didn't understand, but as you can see, it has nothing to do with that and the behavior occurs with linear "dumb" keyframes.
IMO it's a high priority bug since such a fundamental feature is broken. For years I noticed that many pushes and "Ken Burns" moves behaved oddly, and I finally boiled it down to this basic problem. I also believe this user experienced the same issue, but it was poorly described: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/36635713-keyframe-movement-that-actually-works
Mauricio Kessler commented
Same here and its driving me crazy. Impossible to work like this in a project where this is essential.
My esteemed colleague Greg Tarlton has this one sorted: 1) select and right click your keyframes; 2) click Spatial Interpolation; 3) click Linear.
Glad this is a feature and not a bug. We are now trying to determine if Linear can be the default!
Here's a sample of the bug and my workspace.
Good description and I agree, Drew, this bug has been posted in various guises over the last couple of years here and on other forums. In my experience this problem has been resident in Premiere for years. Adobe pls let's get this sorted ASAP - there really is no reasonable workaround!