FCPX and Audio Units (not passing validation)

For some reason FCPX or LPX occasionally won't validate a new AU is installed, that's what the Waves AU Region Utility is for. It forces the apps to revalidate the plugin.

I had a similar situation in Logic recently when my new DBX 160 wasn't showing up.

So this should be your first response is to run that app. Second response would be to delete the .plist and try again. Reinstalls of FCPX or Logic are unnessecary, which is a very good thing.

In terms of FCP7 the plugins you are attempting to run maybe 64bit and I'm pretty sure 7 doesn't support that architecture.

Hy there

I have the same problem (due to forgetting the Licences to install) with the validation under OSX 10.10.4.

I tried this:

**Update***

After speaking with AppleCare and Waves, here is the solution:

Quit Final Cut X, if open or not responding

Go to Home > Applications > Waves > Waveshells> RUN “Waves AU Reg Utility 9.2”

Go To ~ Library > Preferences > move this file to the trash: com.apple.audio.infoHelper.plist
(Click GO from the Finder Menu Bar and hold OPTION to reveal the Library)

Restart the computer

Empty The Trash

Re-Launch Final Cut X
(make sure if you have an external authorization key for the plugins that it is plugged in)

But I could not find the file:com.apple.audio.infoHelper.plist

Any ideas how to solve the problem?
Thx

Ronny,

I can not thank you enough for posting this. It resolved my issue and got me back on track to work!

I know this is a late response but I hope it may help you or any others that have may not have found a solution yet.

Steps:
1. Create a new folder on your Desktop and call it FCPX AU Plugins.
1. Open Library Folder.
2. Open Audio Folder.
3. Open Plugins Folder.
4. Open Components Folder. Highlight and Drag the problematic Plugins to the Desktop Folder we created in Step 1 "FCPX AU Plugins".

Start FCPX and you should no longer get the error message prompt.

When you need to use the components with other DAWS such as LOGIC PRO X just drag the plugins back to the components folder from which they came.

FCPX is reading the Components folder upon start up. This is why removing the problematic components stops the problem.

I solved the problem. You should to delete the old version from AU folder. When i saw the old version of WavesShell in Au i tried to delete it and after my FCPX was run!

Oh yeah. There are some versions of the Waveshell that are incompatible with others. This only happens when there is a large change to the underlying code base.

I've learned a lot from experience and the odd conversation with Waves Tech Support.

Version 8 - 9.2 shells will run alongside each other. 9.2 - 9.6 and 9.7+, I think. Can't say for version 10 though as it is not released yet.

It's always safer to download a fresh Waves Central to install your software as it usually handles much of these incompatiblity issues. When installing new plugins, it's always good to update the old as this is where a large part of the incompatibility problems stem from.

You don't need to have WUP to keep your plugins up to date. However if you're jumping from an older version to a newer version you will. Like jumping from Version 8 to 9 as an example.

Waves is constantly updating their plugins, so it's good to keep an eye on it for changes that effect you. However the newer version of Waves Central should inform you of plugins that need updating too.

www.waves.com/downloads/release-notes

Can't find an AUDIO UNIT MANAGER for OS X Catalina. Any suggestions?