Final Cut Pro hangs while validating audio units

Yes, it's boring since a lot of years that it's not able to disable AU scan in Final Cut. I personally don't need any audio plugins in FCP.

At now it hangs here :

Please fixit very soon! I can't use FC at the moment.

eliassinclair wrote:

Yes, it's boring since a lot of years that it's not able to disable AU scan in Final Cut. I personally don't need any audio plugins in FCP.

At now it hangs here :

//:0

https://discussions.apple.com/content/attachment/e651304e-8960-4d38-9165-f82b9180ae98

Please fixit very soon! I can't use FC at the moment.

We are users like you. We can't fix FCP, but the workaround that I mentioned works.

You can even see two small Automator workflows that can move the files back and forth.

Also: FCP does NOT have to check audio units every time! In my Mac, it only validates when I say so, by clicking the "Validate on Next Launch" button, otherwise it just starts without validating.

There have been some similar reports recently. Apparently some audio units cause trouble with FCP.

At the moment, the only way I know to go through this is to divide and conquer, to find which audio units are problematic, and keeping them out of the folder location when launching FCP.

You may be interested to read these other threads:

Final Cut Pro hangs on Audio Unit validat… - Apple Community

Re: Izotope plug ins stopping FCPX from working

I agree it's a workaround for FCP but only if you're not running a DAW simultaneously. Please send feedback to Apple so it percolates up their task list via Final Cut Pro>Provide Final Cut Pro Feedback...  or use this link Feedback - Final Cut Pro - Apple

Before following the below steps recommended by a Reddit user (credits to AyenneTeajay), I too had same problem on my MBP M2 Max. Even deletion of FCP preferences & re-installation of FCP didn't help. Later after moving all the Audio Components as specified in below steps, finally could launch the FCP. Later I have copied back all Components except the two that were reported as incompatible. In my case, the two plugin/components culprits were MConvulution EZ & MRecorder.

1. Go to your plug-ins folder (Macintosh HD/Library/Audio/Plug-Ins/Components
2. Copy all of the files and paste them somewhere else (you'll need to copy them back later)
3. Delete them from the plug-ins folder (the one from step 1)
4. Start Final Cut
5. If it opens, close it and start copying back the plug-ins in small bunches at once - say 10 at a time (or whatever comforting division you like), as after each paste, start Final Cut again to see if it works.
6. If Final Cut gets stuck again after some portion of the plug-ins is pasted, remove this portion and add the components one by one, as you start Final Cut after each paste so you can see which component causes the problem.
7. After isolating the wrong component, keep adding the rest of the plug-ins in bunches by 10 (or another comforting division) and keep checking them by opening Final Cut. Ideally, in the end, you will have it working with all the plug-ins pasted back into the original plug-ins folder (the one from step 1.)

Have you seen my solution just above your post?

Create a new volume on your boot drive with Disk Utility, install an earlier version of macOS on that and use it for FCP.

Once you have the installer the whole process takes less than half an hour and you will be able to use FCP and all your plugins exactly as before.

How to download macOS - Apple Support

Yes,I have same issue.

I've taken the plunge to update to Ventura (13.3) today, only to be disappointed with FCP X (10.6.5) problem hanging with validating audio units. I have over 1100 3rd party audio plugins, so it took a long time to separate invalid ones in order to get FCP X to even run without hanging. Best way is grouping alphabetically, and placing into a folder within the components folder in the Library.

Main issue now is that I have to manually keep moving plugins every time i switch between Logic Pro (10.7.7) and FCP X (10.6.5), as those plugins who do hang FCP X do not hang and validate perfectly in Logic Audio 10.7.7).

Currently FCP X does not seem to allow invalid plugins to be ignored or removed, as always there is no direct support to manage plugins as you can in Logic Pro.

I wish Apple would make FCP much more audio and audio mixing friendly. It leaves a lot to be desired.

In case anyone is interested, Digital Rebellion makes a pretty good plugin manager tool that is part of their Pro Maintenance Tools. It isn't cheap (it's only part of the bundle), but the other tools are quite good, as well (I am only a user of their SW):

https://www.digitalrebellion.com/promaintenance/

MonsieurT wrote:

Waow crap !!!

Same for me and doesn't work even I delete the components...

My FCPX is useful : don't know what to do...

Doesn't work how, exactly? If it still fails while validating audio units, probably there is still some more of them that you need to move away.

I've read that force quitting FCPX and re-opening it several times will eventually make FCPX realize that there's a problematic plugin and disable it. I've tried it and it worked for me; I had two plugins that were incompatible and I eventually received the popup window that those two plugins were disabled. I did open the program with Option+Command too; not sure if it had an impact. Maybe try that a few times before diving into the plugins folder, which contains several hundreds in my case.

At what point in the Force Quit process did you launch FCP with Command+Option? (This deletes FCP's preferences.) In other words, did you Force Quit FCP several times, then launch FCP with Command+Option to delete preferences and then FCP opened telling you it was disabling some plugins?

It was in no noteworthy order. I tried to open FCP a couple of times regularly and had to force-quit it, then I read about clicking on it with Command+Option, had to force-quit it again, then tried to open it a couple of times regularly, then maybe once again with Command+Option, force -quit it again, and at some point it opened and gave me the popup window with the incompatible plugins. Sorry I can't be more specific, and now FCP is running so I cannot reproduce the error. I wish you the best of luck!

Thank you @deepfrequency for reporting back. Starting FCP with Command+Option to delete the preferences can sometimes take a little while for it to completely launch. It also writes a diagnostic log file to the Desktop for tech support, but you can safely delete it if you haven't already.

Removing "problematic" plug-ins is not an option because the problematic plugins basically = all plug-ins.

The issue is the AU Validator Tools are complete garbage, and when it crashes on something it breaks FCP. It stops Validating (using no CPU, just persisting as is in memory) and the user is stuck looking at a splash screen.

No matter how many plug-ins I uninstall, it chooses a different vendor's plug-ins to freeze on.

Uninstall Waves, Freezes on Native Instruments.

Uninstall Native Instruments, Freezes on iZotope.

Uninstall iZotope, Freezes on Arturia.

Uninstall Arturia, Freezes on Serato.

etc.

The only way to run this software - as far as I'm concerned - is to run it on a machine that has no Audio Units installed, as that's the only way you will avoid the AU Validator Tool breaking the application.

Third party plug-ins are fine. The fact that they run fine in multiple hosts in a range of formats is pretty indicative of that. The only outlier is Apple's software, particularly the AU Validator Tool that predictably crashes during plug-in validation and leaves the software in a perpetual unusable state.

The only fix, right now, is to avoid buying or using Final Cut Pro. Use Resolve Studio or Premiere Pro instead. In particular, a DAW or NLE that uses VST3 will completely avoid the issues with AU Validation by virtue of not requiring it.

Replacing Final Cut Pro with Resolve Studio and Logic Pro with Studio One or Cubase Pro = Problem-Free machine, because I don't have to deal with Apple's AU Validator Tools and just use the VST3 plug-ins.

Honestly, I'm probably going to just resell this machine and recoup as much of my losses as possible as the software renders it not very usable for the reason I purchased it. I could have just kept using my Windows machine, which has never given me these types of issues, and ended up a happier user without having wasted thousands of dollars.

You may want to follow terryb's suggestion in another thread: temporarily rename the Components folder as something else, like Components.inactive; this will disable all components at once. It can serve as a workaround until this is fixed - hopefully in the next OS update.