-
-
Save felipecsl/5177790 to your computer and use it in GitHub Desktop.
| sudo kill `ps -ax | grep 'coreaudiod' | grep 'sbin' |awk '{print $1}'` | |
| # or... | |
| sudo killall coreaudiod |
I was loosing the audio but this happened after upgrading from Catalina, so I moved to Catalina tested around for 2 months and did not faced any issue, but as soon as I upgraded to the latest version of mac OS, started facing the same issue again.
Had to use this after installing Microsoft Teams. I couldn't change the volume anymore.
Sadly no longer working on Sonoma 14.4:
Could not kickstart service "com.apple.audio.coreaudiod": 1: Operation not permitted
update 4/24/24: Apple says "Nope, that's the way we want it." 👎
Following. I'm seeing the same as @luckman212. I'm stuck trying to uninstall blackhole-2ch.
@luckman212 , @crunk1
There is a reference in the macOS Release Notes about this, seems like it is no longer possible to kickstart coreaudiod.
https://developer.apple.com/documentation/macos-release-notes/macos-14_4-release-notes#Core-Audio
If you are unable to uninstall blackhole-2ch because the uninstall_postflight fails you could try changing the postflight command in the following file <homebrew prefix>/Caskroom/blackhole-2ch/.metadata/<version>/<timestamp>/Casks/blackhole-2ch.rb to use a different command or no command at all. Since version 0.6.0 the new behavior is reflected in blackhole-2ch homebrew package.
👍
After losing my core audio completely (corauaudid didn't even start with the system), I tried all the tricks in the (Internet-)Book to solve this problem. Multiple re-starts with different buttons pressed and all the code lines that are recommended in the terminal. All that didn't work.
Even the Apple support could help me. There idea was: reset the whole system (with timemaschiine) (what probably wouldn't had helped..as I know now) OR Start from scratch and reinstall everything.
But the solution was way easier.
There was a driver in the /System/Library/Extensions/ that was left there after the deinstallation of a program I wanted to check out. In this case Voicemod.
After deleting VoicemodAudioDevice.driver the Audio Problem was solved the core driver was back everything was fine again. After a Restart!
So if you test a software and after that something doesn't work anymore, take a deep look into the system and find every file that came along with it and delete it. (I know...)
Additional I would like to point out that I use macOs 10.14 (what still works with 32-bit plugins...so i can not upgrade easily) the App Voicemod wanted an macOs 10.15 upwards, which it shows with the first start after the installation. I think that is the reason for all the trouble.
I hope I could help some desperate people with the same problem.