If you encounter a "CoreAudio driver went missing" error on your Mac device, check the troubleshooting steps in this guide that should help with removing the error.
In this article:
CoreAudio driver went missing
This error message was introduced in the SoundID Reference standalone app since version 5.7.3 to signal a failure to communicate with CoreAudio for various reasons and conditions. Our developers have included a button directly in the error message to offer a quick resolution.
What can be done to fix this?
If the error persists, there is a list of actions and workarounds that could potentially help.
- Click on the 'Restart CoreAudio' button within the error message. If you're unable to restart the engine using this button for any reason, you can initiate it via Terminal manually:
- Launch the Terminal app
- Execute the following command:
sudo launchctl kickstart -kp system/com.apple.audio.coreaudiod
IMPORTANT! Before doing this, make sure to switch off speakers/headphones (or turn down the volume completely,) and shut down any DAW or other music production software
- Restart the playback engine: SoundID Reference app > Output Panel > '…' > Device settings > Restart playback engine
- Quit and relaunch the SoundID Reference app: How to fully quit the SoundID Reference app?
- Clear the configuration data: Deleting the config file in SoundID Reference standalone app
- Update the drivers of the interface to the latest version available
- Fully uninstall SoundID Reference. Then reinstall the latest version - download here
- Uninstall other Virtual Devices active on your machine (Blackhole, GroundControl, LoopBack, etc.). There may be a clash between our Virtual Output Device and another. If it then works, it's worth adding them back one by one, to see which one is the culprit.
- Try different sample rates and buffer sizes: Buffer size setting in the SoundID Reference app
Macintosh HD/Library/Audio/Plug-Ins/HAL/driver.name.hal
Known conflicting audio devices:
- MS Teams
- Zoom
- SoundGrid
- BlackHole
- Loopback
- SoundSource
If the issue reoccurs often and heavily disrupts the workflow (present constantly or several times daily), please submit a support request below, and include the following information:
3 comments
Dewasa
On a Mac Silicon running Sonoma, I added Sonarworks to Privacy & Security under "Screen Recording and System Audio" in the subsection "System Audio Recording Only" as SoundID Reference. Only this way was I able to integrate the software with the Apollo, and only this way did it stop asking me to restart Core Audio, which wasn’t starting anyway. The conflict with Rogue Amoeba products and others would have been quite limiting, so I hope I’ve resolved the issue.
Any solutions or advise on how to work with Loopback?