You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Since updating to Ventura 13.3.1 I can't launch FCPX. When it tries, it hangs up during evaluating AU plugins. Sometimes it finally crashes, sometimes it just hangs forever, requiring a force quit.
No new plugins have been added in quite some time, and everything ran fine before the 13.3.1 update.
Has anyone else seen this? Any solutions? Unlike LPX, FCPX doesn't allow you to temporarily disable AU plugins.
There have been several posts here recently about some AU plugins failing evaluation after updating. The solutions discussed have been find and remove the offending plugin manually or use something like Digital Rebellion's Pro Maintenance Tools. One user here said that some combination of Force-Quits and FCP Prefs reset got FCP to launch.
I think enabling FCP to manage AU plugins like Logic Pro is a good idea and Apple feedback worthy.
Removing the AU does not appear to be the problem. FXPX just moves onto another AU — and all AUs working fine for months/years before 13.3.1 — and locks up again.
Worse, I have removed AUs and everything associated with the AUs and FCPX still "finds" non-existent AUs to get hung up on.
Someone didn't do their homework re. 13.3.1/
I posted a longer reply to a similar post.
My only solution was to trash ALL my AUs.
Hard to believe it was AUs from Native Instruments and iZotope that could not be "verified."
NI and iZotope are hardly small fry in the audio universe...
I remain shocked.
Did you try resetting FCP preferences? Hold Cmd+Opt while launching FCP and choose Delete Preferences... in the dialog. FCP will output a zipped diagnostic log file on the Desktop and open the default Untitled library. Set your prefs back to the way you like (disable background rendering, set Import to leave files in place, etc.) then quit FCP. Move one of the AUs back into their plugin location and launch FCP again. Does it fail validation?
There have been many discussion threads here in the last 2 weeks about AU validation and the consensus while waiting for a macOS or FCP fix from Apple seems to be either rename the AU Components folder to something like Components.ignore, or determine which AU plugins are failing and temporarily remove them from the Components folder. AUs are stored in /Library/Audio/Plug-Ins/Components and possibly also in your home directory's Library/Audio/Plug-Ins/Components folder. To get to that one, click the Finder's "Go" menu and press the option key, then choose Library.
Resetting your FCP preferences, well, resets them to their defaults. There is a free version of an application called Preference Manager which allows you to save a copy of your preferences and restore them. Probably best to make the Preferences copy with fresh settings.
Are there specific AU that cannot be verified?
Unfortunately that doesn't help so no one else should do it as now I've also lost my preference settings. I suspect we have to wait for apple to fix this.
Audio Unit Evaluation Bug In Ventura 13.3.1 For Final Cut Pro X
