Music Pgm plugins showing up in FCP - how to stop?

Hi,
I've got a ton of audio plugins for my Digital Audio Workstation.
They all load up in FCP X.

A lot of them are useful, but most aren't. And recently when I quit FCP it quits but gives me an error message about a plugin. (Doesn't tell me which one.) Don't know if this is damaging or I should just ignore it.

My question is this: is there a way to eliminate some of these plugins from FCP? I can't just delete them as that would delete them from my DAW. So I just want to keep FCP from opening them.

Thanks.
BTW, I'm on a Mac Pro 2010 Mojave using FCP X 10.4.6. Can't upgrade anymore with this computer.

I don't think so. Anything that loads as an AU plug-in will be available to FCP. Unfortunately FCP is not a good host for third-party audio plug-ins. Some work great. Others don't. Especially those with skeuomorphic interfaces. If your DAW can work with the VST/VST3 versions of those same plug-ins, you might consider removing just the AU versions.

Thanks.
Do you think it's doing any damage to FCP when it quits and it gives me the error message?

If it's not causing harm I'll just ignore it.

I have no idea. What does the error message say? I doubt it's harming FCP, but might corrupt your Library. But that's just a guess.

Seems it won't happen if I just open and close the file so I finally did some work in the pgm and here's the error message:

Final Cut Pro quit unexpectedly while using the WavesLib plug-in.
Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.

Neal, that message indicates that the WavesLibxxxxxxx.framework is likely causing FCP to crash. That file may be in the WAVES folder in the main Applications folder on your Mac, depending on the version installed.

Which version of WAVES do you have installed? The current and previous version of WAVES plugins (v14 and v13) are not compatible with FCP (according to WAVES support pages), though they are compatible with most DAWs.

It may be that your macOS version and version of FCP isn't compatible with the version of WAVES you have installed. Or, your WAVES installation could be corrupted. You should check with WAVES support.

As far as plugin management goes, Digital Rebellion sells the "Pro Maintenance Tools" suite of applications. One of the included applications, "Plugin Manager", can be used to group and activate/deactivate audio and visual plugins. It's very likely that not loading a bunch of audio plugins in FCP would help with performance. You might find it useful (outside of your current issue).

www.digitalrebellion.com/promaintenance/index

As a general experience, I find that FCP is a terrible host for many third-party audio plug-ins. I haven't hit one yet that crashes the app, however, quite a few with skeuomorphic interfaces do not appear or operate correctly. These same plug-ins work fine in Logic Pro and most other DAWs and NLEs on the same computer. This behavior seems to vary with FCP updates. Sometimes an update fixes these issues and other times an update breaks it again. I would say that using third-party audio plug-in in FCP is a "proceed at your own risk" situation - especially with Waves.

My Waves plugins, I believe are mainly V11. Might have one or two newer ones. Have to check.

Several things for me to try.

Thanks, all.