Understanding Move Behaviour

Hi

I am not sure of your question.

I think what you need is to set build in and build out markers in your Motion template.

Add template markers in Motion – Apple Support (AU)

Right click or use the keyboard M to add a marker

Right click again to get the marker menu, then use edit marker -

Choose build in optional or mandatory. An optional market will give you a check box in the published parameters to turn the in animation on or off in FCP.

Add another marker and edit for a build out.

If you choose as optional, you will have these published

Everything between the markers will loop in FCP - so, in FCP, if you make stretch the template or make it shorter, the animation does not slow down or speed up.

Does this help the issue?

There is no way to display the offsets in FCP so that they are visible - that information is already there if you published the offset parameters.

Hi

By your example, the move behavior is not the most practical tool for this.

Also, at the basic level of operation, we do not publish keyframes. In FCP, any published keyframe will be ignored.

If we want to instruct the Z position parameter from value A to value B, then use a ramp behavior.

We set the end value to what we need. We can then publish the end value to provide the control in FCP so that we can change the value.

Use the offset parameters to control the start and the end of the behavior - so you can control the duration of the animation. You can publish these to FCP.

Use the curvature parameter to set the easing of the animation. However, with the ramp bevahior we can only get as good as ease in/ease out.

If you want a different style of easing for the animation, then we need to look at a different method.

But explore this method for now and let us know if it works well or if you want a better ease option for the animation.

Let's look at the move behaviour also.

I read your post again and see that you prefer the move behavior because it has speed options. These speed options are better than the ramp curvature function.

I think your problem is that you have keyframed that parameter. You don't need to keyframe the parameter. Just set the z position value you want and the behavior will animate.

In this example I am using decelerate.

You can publish the z value to FCP.

However, the Move behavior does not provide any duration control as you see it does not have any start and end offsets.

The only behavior that provides us with both speed controls and duration controls is the sequence text behavior. This behaviour only works for text instructions and it can not be applied to non text layers.

You need to explore and experiment to find a way to create a relationship between a sequence text behavior and a non text parameter.

...I forgot to include...

There are 2 other behaviours that function the same as the ramp behavior - Logarithmic and Exponential. A logarithmic will give you something similar to decelerate.

I do not use these often, but Fox_m may have good advice for using these to create better easing animations than just the curvature on the ramp behavior can provide.

I have experimented with these before, and I know that we can stitch an exponential with a logarithmic to create various ease animations.

It makes it complicated publishing the in and out offsets, so these parameters need to go on a rig - and then publish the rig.