Moving plug-in's?

I have the latest version of FCPX installed on my work computer and just installed it on my home system. What might be the best practice for having the same plug-ins on both system? Is it just make a note of what is on the main system (the work one) and manually downloading and installing the plug-ins on the secondary system (the home one)?

Can one just copy the folders with the plug-ins form one system to the other? Of course I'm speaking of the ones that are not the default plug-ins that come with the main install?

Thanks!

Hmmm . . . so I suppose using Andreas Kiel's great little app X to FX Handler would be one way to do it on a Library by Library basis, yes?

Is there a way to do that on a global basis looking at all plug-ins installed on a system?

The problem with plugins is
1) the kind - plain vanilla Motion vs. 3rd party fxplugs
2) the installation path

Forr fxplug ones more than the "simple" motion interface is needed.
For the pue Motion ones it is confusing - you may end up in kind of mess cause plugins are. Installed both in user and system.

Regarding the question whether it is possible to list all plugins the answer is: Yes

Hmmm - ok, I will bite. How might one list all the plug-ins?

I sense that you have a nifty little trick up your sleeve as you often do.

BTW - my German language skill is non-existent but I kept clicking around on your website untill I found the proper route to your Paypal account. Thanks again for all the cool tools you develop.

how am I doubting your expertise, Andreas, but …

'plain vanilla', Motion-made plugins are in user's Movies/Motion Templates. Done. (??)
Copy that folder/files to any other machine => works.
(… doing that frequently with my/schools Mac)

Hurdles to go:
• if on target machine is no Motion Templates folder, add it and don't forget the suffix '.localised'
• both, Motion and FinalCut have to be of same 'generation', Motion5.3 plugin doesn't work in FCPX10.2 (if I remember correctly, F.Mahoney published some txt-edit-voodoo to 'correct' that… hmmm, where did I save THAT??)
• does not work with commercial plugins based upon SDK or distributed via fxfactory …

Karsten Schlüter wrote: how am I doubting your expertise, Andreas, but …

'plain vanilla', Motion-made plugins are in user's Movies/Motion Templates. Done. (??)

'plain vanilla' means that it is a plugin which is a Motion file which doesn't reference any external code (code doesn't mean media).
You can store them in either of the below shown paths.

The other plugins do store additional code somewhere in /Library/Application Support.

Karsten Schlüter wrote: Copy that folder/files to any other machine => works.
(… doing that frequently with my/schools Mac)

Works for you and many others - for another group of users it won't work.
Legal paths are:
1)
~Movies/Motion Templates.localized/ and subfolders
Compositions.localized
Transitions.localized
Effects.localized
Generators.localized
Titles.localized

2)
/Library/Application Support/Final Cut Pro/Templates.localized/ and subfolders
Compositions.localized
Transitions.localized
Effects.localized
Generators.localized
Titles.localized

1) is for 'your eyes only'.
2) is for 'public viewing'

Karsten Schlüter wrote: Hurdles to go:
• if on target machine is no Motion Templates folder, add it and don't forget the suffix '.localised'

True. See the above.

Karsten Schlüter wrote: • both, Motion and FinalCut have to be of same 'generation', Motion5.3 plugin doesn't work in FCPX10.2 (if I remember correctly, F.Mahoney published some txt-edit-voodoo to 'correct' that… hmmm, where did I save THAT??)

They are upward compatible. If you're sure plugin features have been available in older version change the version in the plugin's text.

Karsten Schlüter wrote: • does not work with commercial plugins based upon SDK or distributed via fxfactory …

That's what I meant. Free plugins even if installed via fxFactory old be 'plain vanillaa'. See also fxFactory help to confirm more or less what I said above.
But also other plugins like CoreMelt, Digital Heaven can't be copied just the way you described.

The 'mess' I mentioned is related to 10.3.x. When plugins stored in system "/Library/..." with 10.3.x they could be transported to user Motion Templates on a machine with the effect not installed. When it it goes back to the original machine the plugin is not found.