validating audio units

There are many threads here about the AU validation problem that was introduced with the 13.3.1 Security Update (and apparently still present in 13.4). The easiest workaround is to rename the /Library/Audio/Plug-Ins/Components folder to something like Components.ignore before you launch FCP. When you want to use a DAW, rename it back.

Send Apple your feedback: Final Cut Pro>Provide Final Cut Pro Feedback...  or use this link Feedback - Final Cut Pro - Apple

The more people that do will hopefully move the fix up in Apple's queue.

There were several people reporting that this was fixed for them in 13.4. If you have not updated yet, it’s worth a try.

It's 2023 and this AU validation problem persists today. iZotope (Native Instruments) Ozone 10 has validation issues with both Audio Unit components and VST3 versions. Sometimes I get them to work in specific apps only, e.g. there is no AU validation in FCP but it validates in Logic, or the VST3 seems to pass validation in Reason but freezes the host app if utilized. If I ever do get them working, if I then move the plugins temporarily, they often fail to validate when moved back to the active Audio/Plug-ins/Components folder. Reinstalling rarely helps. Recently, I finally got Ozone 10 to validate, but after a recent update via the Product Portal, it failed to validate in all apps again. Logic reveals that it crashes validation early in the validation tests as reported by Apple's auvatool. It's very frustrating with seemingly no end in sight, even after working with plugin vendor tech support. Checking the interwebs reveals many similar reports.

It happens with Apple's own Audio Unit plugins. It's an Apple bug, and they don't seem in any hurry to fix it.

Thanks for the heads up on this Luis. I somehow missed those posts. I'd only read people saying 13.4 did not solve their AU validation problem. Good to know it works for some.

Does the FCP 10.6.6 update fix the AU validation problem? Nothing in the release notes about this.