Final Cut Pro hangs while validating audio units
When starting Final Cut Pro, it hangs while validating audio units. Logic Pro validates them OK. Reinstalled FCP and MacOS. What next ?
MacBook Pro (2017 – 2020)
When starting Final Cut Pro, it hangs while validating audio units. Logic Pro validates them OK. Reinstalled FCP and MacOS. What next ?
MacBook Pro (2017 – 2020)
Found the solution. I had recently installed Screens 4. Uninstalled it, then uninstalled FCPX totally, reinstalled, and everything is now fine.
But yes, there is an AU Validation issue. Mine hung up on various different AudioUnits, including Apple's own SoundIsolation AU.
I really don't think it's specific AUs, it's something buggy in Ventura 13.3.1 AU Valitator system. FYI; Logic Pro X nor any other app I have that uses AUs has any issues at all. FCPX seems to just get more buggy with every macOS update.
Again, removing AU plugins often doesn't work, as in my case. It's the analyzer, not the plugins.
Try fcp.co.
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.
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.
The renaming of the components folder isn't a workaround when using Logic. Logic btw. has no probs when rescanning the AUs.
A checkroutine should return with a message and should not stay in the nirvana.
I've sold my MBP. I'm shipping it out Monday. I will use Resolve on my ASUS, and I can't be bothered to give feedback if they can't be bothered to test the product for such blatantly obvious breakages.
This is not an attempt to excuse Apple but whenever anything new comes out there will usually be unexpected consequences.
To minimise this tech companies give their products to hundreds (thousands?) of users for testing prior to release.
However, no two users will have the same apps, folders, files and other gubbins on their computers so the tech companies cannot be 100% certain there will not be some people who fall through the safety testing net.
I would think they tested FCP with the new system but forgot that some users (a minority) use third party plugins or assumed they would work the same as the built-in ones.
These comments are a bit late but may help some people in the future.
The regulars on this forum know that new releases can be problematic so they generally have "automatic updates" switched off and don't update for a week or so until any flaws have been discovered.
My technique with updates to the operating system is to download the update, create a new volume on the Hard Drive/SSD with Disk Utility and use my critical apps on that volume.
After thoroughly checking everything is OK, I can delete the new volume and install the updated OS as per usual.
Ian R. Brown wrote:
This is not an attempt to excuse Apple but whenever anything new comes out there will usually be unexpected consequences.
To minimise this tech companies give their products to hundreds (thousands?) of users for testing prior to release.
However, no two users will have the same apps, folders, files and other gubbins on their computers so the tech companies cannot be 100% certain there will not be some people who fall through the safety testing net.
I would think they tested FCP with the new system but forgot that some users (a minority) use third party plugins or assumed they would work the same as the built-in ones.
It's literally freezing validating Apple's own System AUs for people. Lol. Again, this has nothing to do with third party Audio Units. I'm not sure how many times this has to be stated before people get it.
I don't understand how anyone could think Disabling all of your AUs in a Video Editor is a workaround. That seems a bit uber-casual and out of touch. I am not trying to take out the frustration I have with apple on the forum, but I don't even understand how someone could think that is a reliable workaround... except to people who do nothing but chop out clips for TikTok or their Facebook Timeline.
Without those plug-ins, the software itself is of no use. It's the reason why I have the plug-ins. If they weren't useful, I'd have deleted them all and moved on - why even waste GBs of storage on my machine for them, if I don't *actually* need them. I don't even really use Logic Pro on that machine... ever. It was purchased for Final Cut Pro.
Video is an Audio-Visual medium. We can't just be expected to disable all of our plug-ins, plug-ins that were purchased and/or installed specifically for use in the software. Until Final Cut Pro offers the equivalent of - at least - RX Standard, then that is 100% a no-go. Not for the type of footage I have to work with (due to the facilities/environments in which it is recorded, not because it was "badly recorded").
If Video Plug-ins couldn't be scanned and were freezing FCP the way AUs are, I wonder how people would react to others telling them to just disable all of them and wait for Apple to remember that they completely broke their own software. It's been at least a full month since they broke this, and they haven't even attempted to fix it.
All of this for... correct Skin Tones on Pushing Hands emoji?
The problem for me is I'm a Pro Tools editor and have hundreds of plug ins.. they all brick FCPX
And quite often I'm bouncing between FCPX and Pro tools, so removing them or making a new user just doesn't work.. Upgrading to Ventura has been a absolute dud for me ..
But the Automator may be a kind of workaround sure .. id be happy for FCPX to not even use the AU components .. But they share a common folder and that's not possible right?
Thanks Ian .. Id just updated to Ventura so yes definitely that's a option to go back but I think I'm going to use Pro Tools with AAX plug ins and avoid using any AU plug ins or other apps that use them for the time being, I was just about to start on Logic but ill wait .. that will keep me running till there is a fix. Id forgotten Pro Tools no longer uses AU on the version I have.. so that's something
When I use FCP I use the Adobe suite ProTools and a plethora of other programs simultaneously.. with a variety of plug ins .. a few with licence keys with apps as well .. this isn’t just a few minute job .. far easier for me to ditch the AU plug Ins as I don’t process audio at all in FCP or make a Automator script.. thanks for trying though :)
I have hundreds of plugins, I need them to use in Logic Pro, I don't use them in FC, I can't remove them. Every time I open Final Cut it spends a lot of time validating them, it's absurd not being able to turn this validation off, you can't even turn it off in the Final Settings menu Cut. Absurd and Apple does nothing MONTHS later?
Final Cut Pro hangs while validating audio units