Keyframed movements continue after keyframes end

[Andy Neil]

Try making add edits on either side of the keyframed movement. It’s hard to tell what’s going on without seeing your project. It sounds like you have a bezier curve between two keyframes with the same value (0,0). Since FCPX defaults to bezier keyframed movements, it’s screwing up the interpolation between the end of one animation and the beginning of another. Adding add-edits so that the keyframes are isolated might fix that for you. Of course you may have to do the keyframing over again.

You could also try changing the interpolation to linear and see if that clears it up.

Andy

https://www.timesavertutorials.com

[Bill Davis]

Sounds like you’re dealing with the default “ease in and out” keyframe behavior built into X.

There’s been TONS written on this over the past two years. Do a google search on “FCP-X keyframes” and study the replies.

Essentially, there’s not just ONE kind of keyframe in X, tand the access to setting the keyframe type is a bit burried and obscure relative to the interface.

It’s worth studying up on if you’re going to keep using X.

Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.

[Michael Spikes]

Ahh, I think I found it. Thank you Andy for your suggestion of doing an “Add Edit” (blade) right after my last keyframe, and before my next keyframe. In the new “split” clip, although I took out any keyframes, the image still moved around the screen as if I did. It also seems that you cannot edit the curves for Transform movements–just the opacity…. but that seems totally strange. (It’s mentioned in the FCPX manual.)

Anywho, what I found that worked was turning off the transform in the split clip by clicking the blue square next to it either in the expanded video animations panel or the inspector. Now the clip is still. What a pain. This used to be much easier in FCP7…

[Nikolas Bäurle]

You need to set the interpolation to linear. Using the keyframe controlls in the viewer you simply click on each keyframe and change it to linear.

using only the inspector X sets the interpolation to linear. You can click and drag to change a value in the inspector, so you can still place images intuitively.

In the viewer or timeline the interpolation depends on the order or changes made to each keyframe. In the viewer each bezier keyframe has handles you can drag to change the amplitude of the movement.

Personally I prefer movement when animating stills for certain projects, especially when stacking images or having stills bounce off of each other, gives it a more organic look.

Nik

“Always look on the bright side of life” – Monty Python

[Nikolas Bäurle]

I need to disagree with Andy on the “Add Edit” solution. This movement is not a bug but simply a bezier Keyframes. You can adjust all of this in the viewer I watched your example video and your full frame keyframes are beliers, which causes the movement.

if you click on the transform button in the viewer you will should see an animation path with a long curve.

Keyframing in X work perfectly fine and is a lot better than in FCP 7.

“Always look on the bright side of life” – Monty Python

[Andy Neil]

[Nikolas Bäurle] “I need to disagree with Andy on the “Add Edit” solution. This movement is not a bug but simply a bezier Keyframes.”

You didn’t disagree with me. You stated the same thing I said, only differently. I never said the behavior was a bug, and I said it sounded like bezier interpolation. Read my last sentence, I even say to change the interpolation to linear.

[Nikolas Bäurle] “Keyframing in X work perfectly fine…”

1) Keyframing does NOT work perfectly fine in X as exemplified by the OPs issue. In fact, I’ll go so far to say it sucks for any but the simplest of keyframe tasks. It defaults to bezier when it should default to linear. And it isn’t even smart enough to realize that when you place two keyframes with the same value at either end of a segment of time, you don’t want movement. So, no, it’s not perfectly fine.

[Nikolas Bäurle] “…and is a lot better than in FCP 7.”

Well, that wasn’t a particularly high bar to overcome.

Andy

https://www.timesavertutorials.com

[Nikolas Bäurle]

Sorry Andy I misinterpreted your response.

Personally I like the Keyframing, it’s not on the level of Motion or AfterFX, there is some improving to be done, but it still works very well, I use it pretty much everyday, in a tight schedule. Perhaps it’s just a matter of taste.

“Always look on the bright side of life” – Monty Python

[Mark Morache]

Michael… give this a try.

https://www.youtube.com/watch?v=tEu93c1kIa0

It’s a very strange workaround, but if your problem is interpolated bezier movement between two of the same keyframe values, this should clear it up.

Basically, you start at the first keyframe, go forward one frame and add and delete a new keyframe. I usually do this three times: add-delete-add-delete-add-delete. Then go to your next keyframe, back up one frame and do the same thing.

I believe when you add a keyframe one frame beyond another, it forces the bezier curve for the transform to become zero, and when you delete the keyframe, the zero curve stays. I don’t get satisfaction from just trying to edit the transform points in the window. Not every parameter goes linear by doing that. My add/delete keyframe trick works however.

Hope this helps.

———
Don’t live your life in a secondary storyline.

Mark Morache
FCPX/FCP7/Xpri/Avid
Evening Magazine,Seattle, WA
https://fcpx.wordpress.com

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Bret Williams]

I’ve seen this too. I can’t believe anyone would say keyframing is better in X. Different yes. Better, no. Both are convoluted in different ways. Apple truly doesn’t understand keyframing. Even Motion is a bit archaic. They could take a few lessons from Adobe.

[Michael Spikes]

Thanks for all of the replies on this thread. I now have more weirdness in my project (this time complete with screenshots!) After using the “add-edit” trick (I’ll try the other things in another project) I get to my last keyframed movement, and now my image will not move on the X axis at all.

In this shot, you can see that my video (on the left) is shrunken down along with a screenshot of a website that the speaker is referring to. Notice the X&Y position.

In this shot, on the second keyframe, the image scales back up to 100% — but no matter how hard I try to do so, I can’t adjust the X position to anything but -251.2, not through dragging the image, dragging the number, or double clicking and typing it in. When I delete the keyframe, and start over again, I can then type in X=0 on the last keyframe, but the image just JUMPS in one frame, instead of over time–although the setting are the same as seen here.

Is this a bug–or am I seriously doing something wrong?