Hi, I recently upgraded to the most recent MacOS Sonoma 14.3.1 version. Previous to this update my SoundID Reference app issues (Core audio missing) seemed to be fixed with the SoundworksID 5.9.1 update.
However, the new MacOS update seems to reactivated the issues except this time they seem more severe because the workaround you suggested to restart core audio doesn't seem to work reliably?
I strongly recommend that users avoid the MacOS update until Sonarworks can confirm that SoundID Reference works correctly under the latest version.
Do you have any recommendations on how I can get Core Audio to stay active in the meantime?
5 comments
Hi Brian, thanks for reaching out, sorry to hear you are encountering some trouble.
We have not yet seen other reports relating to the latest macOS 14.3.1 version update specifically, so it would be great to understand a bit more about the issue.
Is the problem with the “CoreAudio driver went missing” error appearing in the app? Does this happen at anytime or perhaps after some specific actions (closing the app, connecting/disconnecting a device, after computer sleep or idle time)?
I know it may sound like a trivial suggestion, but it might be worth reinstalling SoundID Reference to see if that makes any difference. Here are the steps:
Let us know how it goes!
Hi
I reinstalled SoundID Reference as you suggested but no change.
In more detail, the issue i am experiencing is as follows.
After upgrading to MAcOS 14.3.1 my SoundID app will not reliably stay connected to Core audio when i swithc sound origination sources on my MAC.
For example: If i am playing Spotify from the spotify app and then also attempt to play a YouTube video in my browser SoundID will fail and lose connection to my audio interface. It takes a while to get the ‘restart core audio’ message from SoundID because loses connection to my sound output interface (Audient ID24) for a minute or so and seems to be trying to reconnect.
In an attempt to ensure this wasnt an Audient Issue. I connected SoundID to my Mac Studio internal speakers. All plays OK until i try to add a sound source or switch sound sopurce (as example above) and then SoundID fails in the same way described above.
One final thing. I primarily use SoundID in Ableton (as a VST3). I used it for a few hours yesterday and was careful NOT to switch any sound sources. Regardless of this I found that SoundID would lose connection to Core Audio about once an hour even if i wasnt actually doing anything on the Mac at that time.
I would appreciate some urgent focus on this. I cant imagine this is a problem exclusive to my setup
Thx
Brian
Hi Brian, thanks for your reply and for more details.
I will open up a support request on your behalf, so we can look further into this issue.
I never saw a support request> Did one get opened?
The problem still exists. I have tested extensively. SoundID Reference seems to loose access to the audio devices then refinds them seconds later, then loses them again. Makes it pretty much unuseable at this point.
I wiuld welcome some sort of response. The MacOS update has been out for a couple of weeks now. IHave you been able to recreate the issue? Any plans to fix it?
Hi Brian, thanks for your message. Yes, I have opened a support request from our end with you (request #162600) and we have also followed up on it, perhaps it has not reached you? Please check whether our message maybe has went into spam as that sometimes may occur.