Final Cut Pro STUCK VALIDATING AUDIO UNITS

Ok, so you're telling me I should have multiple boot on my machine and devote internal disk space for this.

Or lower security settings to boot from external drive, plus ensuring the relevant data is accessible for both systems, so maybe create another volume on my disk for data in case I would have to share data.

Do you really think this is a practical way of working? And a relevant way of using (costly) SSD space?

I know you're trying to help, but the "you just need" is not appropriate for everyone.

And by the way we are on Macs, so "it just works" should be the rule.

Anyway, I will try the alternate user, which is a far simpler approach (fingers crossed). And will let you know.

Well if you follow the developer guidelines for AudioUnits, they should work if installed in the user library instead of the system library.

Anyway, the trick I indicated works for NI and Izotope AudioUnit plugins, which apparently are the most frequent ones stunning FCPro.

If some people have no luck, please report it here, it will help the community.

Tom Wolsky wrote:

You no longer need to reduce security to use an external boot drive.

Sorry but this is simply not true. I just checked, and on my Intel-based Mac with a T2 chip, it is required to go to T2 Security Settings (boot with Command-R) and then lower the security by authorizing boot from external drives.

Tom Wolsky wrote:

A separate user doesn’t help as most plugins are using the system Library.

This is misleading.

Most plugins are NOT using the system Library, they are simply installed there, and moving them to the user Library SHOULD work if the developer is following Apple Guidelines.

If there are AudioUnits which are not working anymore when moved to the user Library, then let's list them instead of saying "it won't work in most cases".

I'm sorry Tom, we are here to help each-others, not throwing out un-documented advices.

This is why I have to correct you, for everyone to try getting tricks working (and test-able) in 2 minutes instead of having to install a whole system!

Hope you'll understand I'm not here to blame, just trying to help.

Cheers!

I'm glad you found a workable solution at last. I suggested using a second user soon after the problem arose more than a month ago, but was told by those having the issue that the a second user wouldn't work because the plugins were using the system library. We've had at least a month of endless messages, multiple times a day, with the same problem. Perhaps next week an OS solution might fix it.

The dual boot stuff is hilarious, TBH.

And so is the length of time this has allowed to persist. I can't even be mad, frustrated... anything... anymore. It's evolved into a cackle-inducing situation.

Can anyone confirm. Also, does this update break anything else. I’m no longer willing to blindly trust Apple's updates. I’m pretty sure reports are that the screen flickering and blanking issues aren’t fixed by 13.4, so I’m not very tempted to take this dive.

Well, I do not have any of those audio plug-ins so I could not say. I intend to install the update tonight.

I have read a few comments to the effect that it did solve both of the issues, but maybe not for everyone.

As Ian suggested, you could try installing 13.4 temporarily in a separate APFS container to see how it goes, before commiting to it for you day to day system.

You don’t need different computers. You just heed a different boot drive or volume.

You no longer need to reduce security to use an external boot drive.

A separate user doesn’t help as most plugins are using the system Library.

You moved the components. That’s an excellent idea, though others has said the moved components wouldn’t work properly. Perhaps that’s only for some elements.

I'm typing this in Big Sur on an external SSD using a 2019 MBP whose internal system is the current version of Ventura set to Full Security.

No play on words! Default security is boot from external drive being disabled, and for a good reason.

I can post the URL from Apple Support if you like.

The full security requirement was true for some time, but I believe Apple changed it some time last year, perhaps with a version of Ventura.

Even simpler than moving the components indeed.

Nice trick!

Automator will ask for admin rights but that’s very acceptable.

Thanks!