You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Motion Generator not properly working in FCPX

Hi everyone!


I'm struggling with a basic animation I'm trying to do in Motion.

I need a preset for a series I edit in FCPX, so I created a generator in Motion, featuring two drop zones, a counter and some animated elements.

In Motion, everything looks great and does exactly what it's supposed to. But once I open it in FCPX, it's totally off. The duration is not the same as in Motion, the counter is way slower and the animation does not play to the end.

Do you guys have any idea what's going on here? I'm not a Motion pro, but in my opinion, everything should work just fine.

Here is a link to my generator:

Dropbox


Please help me out here!


Thanks,


Benjamin

iMac Pro

Posted on Dec 30, 2020 2:12 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 30, 2020 3:20 PM

Hahaha, thanks for your opinion! I get what you're saying. But my project in FCPX has the same frame rate, so I don't think that's the issue.

I tried different markers; build out on my first frame, build in on my last and various steps in-between.


Anyway, I just found a workaround that seems to work, even in my exported file.

I deactivated the "Animate" checkbox of my counter and set two keyframes at the "Value" slider. One at the beginning of my countdown at 69 seconds and the other one at the end of it at 1 second. All the other counters in my project worked fine, for they were fixed at a single value (69 and 0). The countdown was obviously faulty. Maybe the counter generator has a bug or something. However, since I changed the animation from "Animate" to "Value", everything is fine.

Thanks for all the help, guys!


BTW, it took me 3-4 days and a lot of frustration to figure this out xD

7 replies
Question marked as Top-ranking reply

Dec 30, 2020 3:20 PM in response to fox_m

Hahaha, thanks for your opinion! I get what you're saying. But my project in FCPX has the same frame rate, so I don't think that's the issue.

I tried different markers; build out on my first frame, build in on my last and various steps in-between.


Anyway, I just found a workaround that seems to work, even in my exported file.

I deactivated the "Animate" checkbox of my counter and set two keyframes at the "Value" slider. One at the beginning of my countdown at 69 seconds and the other one at the end of it at 1 second. All the other counters in my project worked fine, for they were fixed at a single value (69 and 0). The countdown was obviously faulty. Maybe the counter generator has a bug or something. However, since I changed the animation from "Animate" to "Value", everything is fine.

Thanks for all the help, guys!


BTW, it took me 3-4 days and a lot of frustration to figure this out xD

Dec 30, 2020 4:04 AM in response to CountryCore

Hi Benjamin


I think you just need to add build in and build out markers to the project. The markers will prevent the timing distortion that happens when you adjust the generator duration in FCP. I'm not sure how you use the generator in FCP but from what you describe, you might just need 1 build in marker placed at the very last frame.


Learn about them here

https://support.apple.com/en-nz/guide/motion/motn141bc9de/mac


Edit - I see Luis already replied with this info too.


Dec 30, 2020 3:43 AM in response to CountryCore

The duration you set in Motion is “relative”. Let me try to explain: say you make your generator be 10 seconds in Motion, and that you have something (a text, say) appear in the first 5 seconds; then you use it in FCP and drag it to last 20 seconds: then that text will appear for 10 seconds.


Now if you want something to last for a specific amount of time regardless of how long the whole generator is, you need to add specific markers in your Motion project. For example if you add a “build-in” marker 2 seconds into the project then the first section will always last for 2 seconds, no matter how much you extend the generator in FCP timeline.


I will look at your project later today, as I am not at my mac now.

Dec 30, 2020 8:23 AM in response to CountryCore

Thanks for your input, guys!

This seems to have solved the issue (sometimes).

Maybe my apps are broken, but sometimes it works and sometimes it doesn't.

I put a build-in mark on my very last frame and the duration of my generator seems to stay as animated. Before that, it was always about 10 seconds short in FCPX.

But my countdown sometimes works and sometimes doesn't. I have no idea why it does that, I didn't change anything on the counter. I guess it's just up to pure luck now.

Dec 30, 2020 2:48 PM in response to CountryCore

It's not pure luck.


Your project is set to a fractional frame rate (29.97). Depending in which kind of project it is used in FCPX will determine how the template behaves with timing, and unless it is exactly the same frame rate, it won't work entirely as expected. Fractional frame rates screw everything up. Period. You can fix this aspect of your project without having to start all over again:


https://fcpxtemplates.com/how-to-fix-fractional-frame-rates-in-templates/


As Luis suggested, on the first frame of your project you should set a Build Out Mandatory marker (select the Project "layer" or click in the Layers List outside of any other object - or Deselect All) if you need to maintain the timing of the Motion animations. However, when using timing markers, if you change the length of your generator in the FCPX storyline, you will effectively change how the template starts and executes in FCPX. You will either cut into the animation (but it will finish out from that point) or it will create a pause frame until the timing can progress to the end. However, in general, this is how you want countdowns to behave.


No project created in Motion should be in a fractional frame rate. [IMO - they shouldn't even be offered... in Motion OR FCPX! (Or AE/Premiere, Resolve, etc. etc... in other words: anywhere, including cameras.)]

Motion Generator not properly working in FCPX

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.