Final Cut Pro hangs while validating audio units

Removing the problematic audio units appears to be the only solution for now. Spent half a day deleting the offending AUs just to get FCP to launch. Hope Apple addresses this soon... highly annoying.

This person has removed third party plugins and was back in business in 10 minutes.

Final Cut Pro - doesnt start - Audiounits… - Apple Community

13.4 came out a few days ago.

Did you update to 13.4? Several people reported that it fixed it for them (but apparently not for everyone).

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.

If you can't wait for a fix the only solution is to 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.

You can try rebooting your system. It worked for me when I encountered this exact issue.

@NateWalker - be sure to send Apple feedback about your use case. Final Cut Pro>Provide Final Cut Pro Feedback...  or use this link Feedback - Final Cut Pro - Apple

I agree, my AU hanging issue only happened when i updated MacOS to Ventura 13.3. Before that FCPX worked fine.

A lot of is because Apple update their pro apps far less frequently than they do OS system updates. Of course 3rd party apps also need to be in line with the newer OS, but my AUs work fine in Logic Audio on Ventura. So, i think FCPX and Ventura are out of tandem and why it’s buggy.

i still do think FCPX leaves a lot to be desired with how it works with audio, generally speaking, but that’s another topic. 🤓

It's almost like people refuse to actually read the thread before giving redundant solutions that don't work.

It is not an issue with AU Compatibility. The AUs work fine. You can validate them and use them in Logic Pro, Studio One, Resolve and other software and they function as expected.

The issue is FCP-specific and has to do with the way it validates Audio Units.

Wasting hours of your time moving all of your hundreds of Components out and then restarting the app over and over to see if anything fails validation (which is common even in Logic Pro, for various reasons - you simply to go to the manager and rescan them and they pass) is wasteful.

What Apple needs to do is move AU Validation to a background process, separate from the rest of the software, and allow the software to start up even if the AU Validator fails. If there is an issue, then issue an error message if anything goes on. That way, even if the AUs don't get scanned/validated, people aren't left unable to do actual work when they turn around and break the software - only to leave it broken for months at a time.

13.3 released in January. The software has been broken THAT long. Is this supposed to be a Pro App, or is it just an expensive PowerDirector alternative requiring an expensive hardware dongle for ... rich hobbyists?

This isn't just a case of the software crashing here and there. It's LITERALLY UNUSABLE, and unfortunately I need my Audio Plug-ins and I'm not going to be moving things back and forth every time I need to switch applications. Sorry, but no. That isn't even a workaround.

I think the simpler solution is to switch to a separate FCP user without the Audio Units or at least without the problem ones.

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/

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!

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

Until this is resolved, you may want to use an Automator Quick Action to facilitate the moving of these audio units, as I exemplified in one of the threads I linked to above.

I happens with AU plugins randomly, it's the AU analysis system that is at fault. AU plugins that were no problem before are now a problem since Ventura 31.3.1. Removing them won't do any good.