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.

Apple Motion is still SUPER SLOW to Launch on M2

I'm on a new, clean M2 Mac Mini Pro. I thought Motion would launch MUCH faster than on my ancient mid-2014 MBP, but I'm sitting and waiting forever while it putzes around looking at every plugin (non-technical generalization intended).


I use my plugins in FCPx. FCPx launches super quickly. I don't even need or use all these plugins in Motion, but unlike Logic, I can't simply bypass them in Motion (which shouldn't even be necessary).


I've read some input from Luis Sequeira1 on an older thread about this issue. The problem is common and, shockingly, still exists on silicon. I shouldn't have to delete Chrome from my system. Further, if FCPx doesn't struggle when launching with my plugins, Motion shouldn't.


This is like when I had to start loading Bruce Lee on my C64 tape drive and come back 1/2 an hour later to play.

MacBook Pro (M2, 2022)

Posted on Sep 23, 2023 2:21 PM

Reply
16 replies

Dec 4, 2023 11:27 PM in response to donsmith

It looks like the problem is not with loading plug-ins, but the Project Browser (since it also occurs when Motion is already running).

If you start Motion holding down the Shift key, it will bypass the Project Browser and open more quickly.

But your idea of putting a sample title, generator, effect and transition in the Dock (which I believe is what you mean by the "bar at the bottom" works too.



Dec 4, 2023 5:16 PM in response to donsmith

Hi Don,


Best to make your feedback and feature requests here

Feedback - Motion - Apple


That is the channel that has oversight from the Motion development team.


It is interesting that there was no plugin or template product you could isolate to find the one causing the lag in loading.


As you may have seen already in this thread, there are a couple settings you can change to skip the 'browser' on start up.


May I ask what happens if you right click from the Motion icon in the dockbar and open a previous project from there? Do you still get the lag on start up?





Sep 23, 2023 3:38 PM in response to Adam F

Hi


The previous thread still all applies here.


For a baseline - remove all your plugins and then launch Motion. You should see Motion boot immediately.


If you have anything from Pixelfilm studios


The issue isn't with Motion, but with the 3rd party developers not catching up such that their plugins slow the launch process down. It is a 3rd party software issue.


It would be good for there to be some kind of detection - like on launch '3rd party plugin XYZ is not responsive' so that we can isolate and remove. That would go a long way to take the uncertainty out of it.


You can bypass a plug in Motion. Remove it from the directory and Motion will not attempt to run it.


Finder - movies - motion templates - you will find all the effects, titles, transitions and generator folders here. Put them in a different location. But - note that if you have these in use in any FCP project - they will be missing now. Any plugin that uses an installer that runs the hosted fxplug tools - contact the developer on how to uninstall.



If you launch Motion to the project browser by default, then yes, Motion will read check every plugin in that process.


If you want to change the default launch - go in to Motion preferences/project and change the launch mode from browser to project. Then use the 'choose' menu to set the default project settings.





Sep 23, 2023 3:51 PM in response to rowie302

I appreciate the thorough response, @rowie302


What doesn't make sense is that FCPx doesn't get hung launching or creating a new library, asset or project. While I don't doubt that PFS is potentially a culprit here, I have multiple plugins that I still use from PFS in FCPx (which is why I don't disable it altogether) with no problem at all. There must be other 3rd party plugins with similar issues.


Is Chrome still a problem? The link in the old thread links to a rant from 2020.


Apple that should be isolating this issue from slowing Motion down to a crawl. The example you gave for ignoring plugins is precisely what I was thinking.👍🏻


I did send a suggestion in.




Sep 23, 2023 4:02 PM in response to Adam F

Hi


As far as I know, Motion and FCP are not using the same process. It is not as if FCP is faster than Motion to do the same thing. Motion is the motion graphic engine of FCP - (others here can give a more exact explanation of that) - and Motion needs to know what FCP is running so that it can access anything installed template - this is the difference. FCP doesn't need to load anything until it is required to - at the time there is a template to be run - then FCP will process that case by case. Motion needs to load and process everything on start up.


In FCP you will see the lag in a different situation - when you add an unoptimised template to the project - then you will surely see the 'loading XYZ' prompt for excessive durations before it runs - or, beachballs FCP outright.


Chrome I have no knowledge on - I think that at the time back then, it was a known system resource hog that was slowing things down for Motion and other apps also.


Yes, would be other plugins causing issues. I note PFS because the observable trend here over the years with this topic has been that a PFS plugin was the cause.



Oct 8, 2023 12:59 PM in response to rowie302

rowie302 wrote:

. . . I note PFS because the observable trend here over the years with this topic has been that a PFS plugin was the cause.

✅ Got back into this today. What I'm finding is that Pixel Film Studios BIG plug-ins are causing the issue.


Specifically, I've narrowed it (in my case) down to:

Hand Drawn Elements Mega Pack - 3.73 GB in Titles (+ 3.08MB in Titles) - I don't even have all options installed

Backdrop Mega Pack - 3.85 GB in Generators!

Background Mega Pack 3D Renders - 4.41 GB in Generators!

FCPX Cartoon Mega Pack - 1.08GB in Generators + 404MB in Transitions


Clearly, Motion is going through every single graphics file inside of these monstrous packages. This takes the Motion launch from 6.8 seconds to the "not responding" for minutes - I'm pretty sure as much as 10+ over the past few years.


In recent years, I've moved to mostly FXFactory. I do like some of BretFX's plugins as well.

Is PFS just putting the assets in the wrong place? Are they misusing architecture?


Still sticking to my opinion (suggested to Apple as well) that we should be able to disable plugins from loading via prefs in Motion (really...in FCPx as well) just like we can in Logic.


Hopefully this will help others!



Oct 9, 2023 4:58 PM in response to Adam F

Following up. Here's the response I got on this from Pixel Film Studios:


"Hello! :) 


Thank you for contacting us! 


We have a guide on how to work around this issue here: https://store.pixelfilmstudios.com/motion-not-opening/ "


It's a bit of an obvious & ridiculous work-around (essentially what I did when testing before my last post). Basically, move plug-ins out when you need motion and back when you need FCPx. Seriously? 'Cause NOOOOBODY would have both running at the same time.🙄


Dec 4, 2023 4:56 PM in response to Adam F

I thought that Apple Motion was simply crashing on the load of a faulty plug-in. The inability to open started when I had an Intel iMac Pro, but continues with my M1 Studio Ultra. I would launch Motion and then the Force Quit panel would show that it was not responding. I would still wait a bit longer before force-quitting Motion.


Well, today, I accidentally let it try to launch for about ten minutes. When I came back to my computer, Motion had launched! Apparently, it had NOT been crashing but instead SOME plug-in was slowing the launch WAY DOWN. Way WAY down!


Before discovering it was just a massive loading slow-down, I went through the process of eliminating (in steps) ALL plug-ins to find the culprit. But, no joy. Yes, ALL plugins were absent at some point with no change in boot time.


Remember back for a few years and you might recall seeing an app load while listing what step it was on. I mean, steps were changing at a blur of high speed. In my bucket of wishes, I wish Motion would list the plug-in it is loading. Just watching plug-in names flashing by and then seeing one plug-in that stalls the loading will tell you which plug-in is the culprit.


Please please PLEASE Apple, there are so many of us with Motion plug-in loading issues, so if you could find a way to see the plug-in loading sequence would help immensely.


Thank you.

Dec 4, 2023 6:43 PM in response to rowie302

I essentially do the same thing in that if I want to create a new title, I’ll go inside of any title effect and open it instantly in Motion, save as, and then clear that title and work on my new title. Just today, I put the active ingredient of a title, an effect, a transition and a generator in the bar at the bottom since trying to go to a different kind of plug-in from an already open Motion will also stall Motion for a number of minutes.

Dec 5, 2023 5:41 PM in response to Luis Sequeira1

The issue that this thread is plugin-related. I know from testing this out that plugins are 100% what cause the slow (sometimes seeming like 10+ minutes) loading.


The launch time decreases as larger plugins are removed.


@Donsmith - You may want to take a look at some of the earlier posts. I specifically explained what I'm seeing in October. It sounds like you may be experiencing a similar effect with a different cause.



Dec 21, 2023 3:48 PM in response to donsmith

I have the same problem running a Mac Studio with an M1 Ultra. As I purchased more plug-ins from Pixel, the Motion performance got worse while FCP has been fine. I was also running Clean My Mac X and spent all day removing it and its components due to a lot of advice here saying it can be the problem and is problem software regardless. However, removing didn't seem to do much for the Motion launch, maybe just a little quicker.

Apple Motion is still SUPER SLOW to Launch on M2

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