Installed plugin not working on Macbook Air

I have the excellent free plugin called Alex4D Smooth Move and was using it on a project on my Mac Mini. I took the same project to work on while away, on my MacBook Air, but when I load the project, the clips show the missing plugin display.


The plugin appears in the clip inspector, but it no longer displays any of the controls. I have the same plugin installed on both Macs in the exact same folder in the movies folder in Motion Templates.

The plugin is available in the Effects panel on the MacBook, but I need to drag it onto the clip and then I can use the plugin, but the problem is, I have already applied the plugin on numerous clips with all the move settings, so this means I would have to redo them all again, which is a big hassle.


Why is the plugin used in the project on the Mac mini not connecting properly with the installed plugin on the MacBook? Any idea how to fix this? Thanks.

Posted on Sep 17, 2022 7:59 PM

Reply
Question marked as Top-ranking reply

Posted on Sep 18, 2022 9:10 PM

Okay -- if I understand what you're saying: you have two machines; you copied over all your FCPX projects from one machine to another. You copied your third party effects -- which **work** in new projects you create on the Air but NOT on the older projects you moved over.


Try this:

On the mini, open your project, find the Smooth Move effects and for each (that aren't working on the other machine) Save Effects Preset (just save the Smooth Moves). Give them each a specific name (SMove-ProjAbbrev-ClipLoc). Save them to a specific category (Alex4D EPs). [If you use time for ClipLoc, do not use colons or periods (unix thing) - use dashes or just format the time in HHMMSSFF.]


Copy the Effects Preset files to:

Users/<username>/Library/Application Support/ProApps/Effects Presets

on the Air.


Find the instance not working on the Air and go into the Alex4D EPs category and drop the corresponding effects preset (you can simply turn off the original until you're ready to delete it). If it works, the EP will load a working copy of Smooth Move on the Air with the saved parameter settings (as well as any keyframing you've done) you had on the older setup. You can then delete the older instance of Smooth Move that isn't working from clip in the Effects inspector.


Normally, you could just add a new working version of Smooth Move to replace the old one, but this Effects Preset method is a way to save and copy/duplicate your parameter settings from the older project versions. If everything is installed correctly, this should work to restore your settings. If your Smooth Move template is exactly where FCPX expects to find it, FCPX will load it and set the parameters by itself. If it fails, then you need to recheck all the installation steps (maybe you have duplicate or *trailing* spaces added to the file path parts that you may not be able to see right off.)


If the Effects Presets trick works, you can simply go back and delete them (then restart FCPX).


If you have any questions, get back... I have a feeling that if you clear up one instance of this problem, then all the rest of them will work out "by themselves".



Similar questions

27 replies
Question marked as Top-ranking reply

Sep 18, 2022 9:10 PM in response to Cartoonguy

Okay -- if I understand what you're saying: you have two machines; you copied over all your FCPX projects from one machine to another. You copied your third party effects -- which **work** in new projects you create on the Air but NOT on the older projects you moved over.


Try this:

On the mini, open your project, find the Smooth Move effects and for each (that aren't working on the other machine) Save Effects Preset (just save the Smooth Moves). Give them each a specific name (SMove-ProjAbbrev-ClipLoc). Save them to a specific category (Alex4D EPs). [If you use time for ClipLoc, do not use colons or periods (unix thing) - use dashes or just format the time in HHMMSSFF.]


Copy the Effects Preset files to:

Users/<username>/Library/Application Support/ProApps/Effects Presets

on the Air.


Find the instance not working on the Air and go into the Alex4D EPs category and drop the corresponding effects preset (you can simply turn off the original until you're ready to delete it). If it works, the EP will load a working copy of Smooth Move on the Air with the saved parameter settings (as well as any keyframing you've done) you had on the older setup. You can then delete the older instance of Smooth Move that isn't working from clip in the Effects inspector.


Normally, you could just add a new working version of Smooth Move to replace the old one, but this Effects Preset method is a way to save and copy/duplicate your parameter settings from the older project versions. If everything is installed correctly, this should work to restore your settings. If your Smooth Move template is exactly where FCPX expects to find it, FCPX will load it and set the parameters by itself. If it fails, then you need to recheck all the installation steps (maybe you have duplicate or *trailing* spaces added to the file path parts that you may not be able to see right off.)


If the Effects Presets trick works, you can simply go back and delete them (then restart FCPX).


If you have any questions, get back... I have a feeling that if you clear up one instance of this problem, then all the rest of them will work out "by themselves".



Sep 17, 2022 8:42 PM in response to Cartoonguy

If you had to create the folders: Motion Templates and Effects, you need to make sure they are:

Motion Templates.localized and Effects.localized (as soon as you enter the names, the '.localized' usually disappears [they are hidden]).


You can right click on the folders and "Get Info". Check the Name & Extension field - you can add the .localized there.


I'm pretty sure Alex4D does not require a specialized installer.

Sep 18, 2022 5:09 PM in response to Cartoonguy

The path looks correct so long as the contents of "Alex4D" IS Alex4D Smooth Move (folder) containing: Alex4D Smooth Move.moef, Media (folder), large.png and small.png. [In most cases, the actual Motion template effect will not show the .moef extension but will have the Motion Effect icon.]


You might have to open System Preferences > Security & Privacy, select the Privacy pane and then select Full Disk Access. Make sure that Final Cut Pro is added the collection.


You might want to start with Motion Templates and work down and for each folder, check in Get Info that the folders have Read & Write permissions.


Repairing the XML references is a **last resort** and would only be done if your user folder names were different (case sensitive).


I checked out the template. Even though it is very old, there doesn't appear to be anything in the template that has been "abandoned" by Final Cut which would keep it from working in newer versions of FCPX.

Sep 19, 2022 6:46 PM in response to Cartoonguy

Okay - I thought the two macs were nearby.


I was just looking at the original files for the template download. The Privileges for staff and everyone are set to Read Only -- they should be Read & Write (all of the permissions for templates I've made myself show R&W for all the templates.)


There is one other installation option -- install the template in:

Macintosh HD > Library > Application Support > Final Cut Pro > Templates > Effects.

Create the Alex4D folder, install the Alex4D Smooth Move folder inside.


The permissions change might solve this... The template itself is only about 6 weeks "younger" than Final Cut Pro X itself. Things were different then.



Sep 18, 2022 9:15 AM in response to Cartoonguy

Make sure the installation is *exactly* the same as it is on your other machine -- that includes Catogory folders and/or Theme folders.


If you're still having issues, then you may need to check to see if your User folders are named the same. FCPX stores the plugin referencess you use in project "database" along with the path used and the User folder is part of the path. If this is the case, there is a way to "repair" the references... but check out the other stuff first.

Sep 18, 2022 2:28 PM in response to Tom Wolsky

Tom Wolsky wrote:

Do you have the Alex4D category in the Effects browser? Is the effect in there on the MBA?

If you can take the drive back to the mini and copy the effect into the library there.


Yes, it is in the effects browser, but the effect already installed is not working on the clip. I can drop the same effect onto the clip, but then I have a new effect I have to set up again. Both copies appear to be on the clip, but one of them has controls and one does not. I can take the drive back to the mini when I get home, but not home, so need to fix this here.


Just to confirm, if I save the plugin into the project, then the plugin does not need to be installed on the computer at all, is that right? It's a small but crucial bit of advice that I never realized, so if that's the case, big thanks!!

Sep 19, 2022 6:06 PM in response to fox_m

Not exactly as you describe. It's explained earlier in the thread, but essentially, I am away from the Mac mini and took the external HD with the project library. I have the plugin installed on the MacBook, but I can't go back to the mini until I return home. That's the problem.


Tom informed me that all I have to do is save the plugin within the project itself and then it will run when I move that library elsewhere. That is, it won't look in the external places, but it will just be embedded in the library. That is something I did not know, so it will solve the problem in the future, I guess. I was hoping I could relink this effect to the effect on this MacBook, the way one can with missing footage or stills, but I guess I can't.

Sep 18, 2022 5:14 AM in response to fox_m

Yup, made sure the folders had the .localized extension. In fact, downloaded the empty folder structure from Alex4D. So the plugin works on the MacBook as a new plugin, but won't work as the existing Smooth Move plugin which are on the clips already. That's the issue. The plugin is recognized, but it's not taking the place of the existing plugins on the clips and so I have to redo all the moves from scratch and I'm also worried that when I get back to the Mac Mini, the work I have done on my MacBook will not show up on the Mac mini.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Installed plugin not working on Macbook Air

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