Time Remapping and Keyframes Don’t Work in CS4

[Blakeblake Blake]

Thank you!! I thought I was insane for having this problem.

I have spent hours BAFFLED that the very first thing I try to do in Premiere CS6 is apparently SOOO spectacular Adobe hasn’t ever thought to make it possible; make a change in speed AND change in motion in the SAME clip!!

I just began using CS6, making my first video, and I wanted to do a few simple edits and export it as a test.

I imported a video clip to a new sequence, added a couple keyframes to adjust the position, worked great. Then I added a couple keyframes to increase the speed of some parts of the clip using time remapping, seemed to work…

When I play the video all the way through the changes to the position start happening before it gets to the keyframe!!

I conclude after all this frustration that the time-remapping is changing the clip length but the key frames for motion are not synchronized with that and they initiate at the same point in “time” as original even though the clip is now shorter/ longer. This causes major confusion and renders it useless!

My B.S. workaround is to never do both in the same clip. I have to Razor a clip if I want to speed up a part then apply motion after its done. But only in sequence never at once.

Someone please post an answer that involves changing a setting in my Preferences that solves this silliness for all of us.

[Danielle Smit]

Has anyone found a workaround for this? (besides what has been mentioned in this thread)
I am using CS6.0.2
I found that the issue only occurs when I use time remapping with keyframes in effect controls. Not if I use the rate stretch tool.
Thank you!

[Adam Liss]

I’m still seeing this problem in CS5.5. The only fix I’ve found is to do my time remapping then nest that clip. Then you can apply keyframes like scaling and positioning in your original timeline.

-Pete

You are a genius. It’s not the prettiest solution, but it definitely works for what I need.

[Sam Goetz]

Just wanted to bump this post and note that this is STILL happening in Premiere CC!!

WTF?!

[Kasie Robinson]

Bump!

[Veronica Waddell]

It’s now CC 2014… (posting this in 2015)… and the bug STILL isn’t fixed!! GRR Adobe.

Thanks for the tip to nest the clip as a sequence. This shouldn’t be something we should have to work around, but being that we do, at least there IS a viable workaround.

[Ht Davis]

Time remapping from the clip assumes you are remapping the clip to a new frame rate to be processed out. Using the KeyFrame method to remap the time is the same function logically, but the program handles it differently.

The clip remap actually changes the indexing and frame count of the referenced clip, and placing any keyframes on that… …well, which index do you use? You have two of them. One is a standard set from the file, the other still needs to be built into timecode. IF you use the first, you’re inaccurate. If you try the second, the number of frames is different, and you have to account for that.

Try duping the clip in project panel, time remap it there, and then apply the clip to a sequence. Now keyframe it. IT should work.

The reason is as stated.

IF you are going to keyframe, then keyframe your entire effect. It will all be processed together.

This is also why nesting works. Sees the nested sequence as a new clip.