Messing with the core audio stack

Does anyone know if Big Sur Mac OS11 messes with the Core audio stack?

I thought Apple stopped that a few system versions ago?

Mac mini 2018 or later

Posted on Mar 30, 2021 2:31 PM

Similar questions

M1 MacBook Pro audio glitch I cannot locate a relevant thread here, but there are reports all over the internet, including several audio forums and Apple dev. forums regarding audio glitches on M1 hardware. The audio crackling or popping can occur in any application and is frequently (perhaps always?) accompanied by a console message like the following: 3587 HALS_OverloadMessage.cpp:222 HALS_OverloadMessage: Overload due to HAL client proc exceeding io cycle budget The audio defect, and console message occur *almost every time* I use an application with audio. I am running MacOS 12.6 on a MacBookPro18,3. Internet lore on the subject suggests deleting the audio plist files in /Library/Preferences/Audio/. I have not found that to be a reliable fix for the problem. Has anyone discovered a reliable solution to this problem? Please help, Apple. [Re-Titled by Moderator]
15509 40
Final Cut Pro x app hangs on Validating audio units Can’t fire up FCPX. It starts then hangs on Validating Audio units. Stuck here. I reboot and try again, same thing. I even deleted the app and installed fresh copy. Still no go. Was working fine till I updated. Thanks for any help. Using Mac mini M1
6503 6
Logic Pro won't open after Ventura update: stalls on scanning audio unit plugins this is INSANELY frustrating. I recently got a brand new M2 MacBook Air, and made the mistake of updating to ventura when it was released. Now, i cannot open Logic Pro. Logic will spend a long time scanning audio units and then when I restart it will hang on "updating information about audio unit plugins". It will not complete in any amount of time. I have tried EVERY solution suggested online. Removing all plugins from the plugin folder allows Logic to restart, but when replacing the plugins it once again hangs on rescanning them. Deleting the plugin cache seems to get you a little farther, since you can see the actual progress and arrive at the 'Incompatible Audio Units Found' pop up. This pop up tells you that there incompatible audio units and offers two buttons: 'Continue' and 'Start Plug-In Manager'. this is the most infurating part: clicking on either of those two buttons results in ANOTHER hang. The beachball immediately appears and no amount of time will allow Logic to start. This is apple's OWN software on it's OWN update! It's so insane that with a brand new machine and the most recent OS i can't open the one program that i most use on a mac! I hate having to spend weeks googling and trying every tentative solution. If Logic identifies the incompatible units, WHY CAN'T IT DISABLE THEM AND START LOGIC PRO!!!
5089 19

2 replies

ryane77

Community Specialist

Mar 31, 2021 1:59 PM in response to Ataraxy01

Hey there Joseph,

We'd like to help answer your question regarding macOS Big Sur and Core Audio.

Upon researching this, we found two resources that may help as we're not able to provide an answer regarding any possible effects for Core Audio within macOS Big Sur:

Core Audio - Apple Developer Documentation
You can use this link to contact Apple Developer support: Support - Apple Developer

Take care.

Ataraxy01 Author

Level 2

189 points

Mar 31, 2021 5:26 PM in response to ryane77

I used the wrong term. Please remove this post. I found the answer.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Messing with the core audio stack