Editor Position keyframes with Ease broken

There have been other discussions about easing Position and Scale in Ken-Burns-style dynamic zooms, but this is a simple case with just a Position animation.

Create a Basic Title (Text, not Text+) in Edit. Use the default text. Set four keyframes to animate its motion onto and off of the screen. I went 20 frames from the beginning of the clip and clicked the diamond to the right of the Position X and Y. Then I went 20 frames from the end of the clip and clicked the diamond to create another. These are keyframes 2 and 3, respectively, at X 960 and Y 540.

Now go to the beginning of the clip handset a keyframe and move the text to the left, offscreen. This is X -230 Y 540 for me. Similarly go to the last frame in the clip and set a keyframe that is also off the left of the screen X -230 Y 540. These are keyframes 1 and 4, respectively.

Play the clip and the animation works perfectly.

Go to keyframe 3 and right click on the red diamond and select "Ease Out". Play the clip again the text will fly out to X 7680 before snapping back to X -230. It's crazy.

[Shrinivas Ramani]

Hi Wayne

Could you provide a link to a project export (DRP) and highlight the clip for us? Even a minimal project - single timeline single edit is fine, as we just need to examine the keyframe behavior.

Thanks
Shrinivas

I've sent a DRP link via PM. Thanks!

viewtopic.php?f=33&t=130880

Thanks, Jim. There are multiple issues dealing with easing keyframes from Edit that are out there, some of them long-standing.

I think what I'm seeing is new in beta 6, but has a similar effect, in the end, to some of the issues that people have had with trying to ease both Scale and Position at the same time. Those issues might arguably be due to the interaction of changing Position and Scale non-linearly, so they might be a case where an intuitive result requires different behavior even if what's currently happening is technically correct. (I.e. if you are moving the center of your image and also scaling the image from that center, the results will not be what you think you're getting though they won't look wonky until you introduce non-linearity in both.)

But in my case, it's the simplest Position-only use case so I'm confident that either something is corrupted in my timeline/project or its a bug. Which, if it is a bug would make the other issues worse. Or might be underlying them. This might be the breakthrough we've been waiting for.