Hi, recently I updated Sound Id and had a problem with it. I'm working with the external headphones output of my Macbook Pro M2 (Ventura), and when starting the computer I cannot use Sound Id because it's not recognized by the computer. I mean it doesn't appear in the sound settings.
I haven't had this kind of problem when connected to an interface (apollo twin and SSL 2) but this problem is constantly using the headphone output.
Please help since I need to use systemwide application to mix in dolby atmos binaural.
Thank You
37 comments
Hi all,
We have released a new SoundID Reference update (v5.9.1.3) today, Jan 24, 2024, which includes a fix for the SoundID Reference missing from sound output settings on macOS issue. With this update, the SoundID Reference audio device should be available in Mac Sound settings and Audio MIDI when the SoundID Reference app is running. For those encountering this issue with the previous versions, we recommend updating to the latest version.
To install this update, download the SoundID Reference installer from our download center here and proceed with the installation.
If there is an issue remaining after installing the update, please check the tips mentioned here: [MAC] No sound / no calibration effect
Thank you for your patience while we were working on resolving this issue. Let us know how it is working for you!
Edit: removed redundant support article link of a resolved issue, updated links
You are not alone buddy. After shutdown and then restart, it has now disappeared from the audio device options in the Audio Midi Setup app.
This update sucks. :(
same here! Broken and can't find the last versions to re-install
We've been receiving similar reports from other users and our team is aware of this problem.
If SoundID Reference is not appearing as an audio output option on your macOS machine after the 5.7.3.17 update, please consider performing a clean uninstall of the software and then reinstall it. Follow the steps below:
Let us know how this goes and if after a reinstall the problem still is present. Thank you!
Believe me - I've tried reverting back to 5.6.1 - don't allow it... preset switch failed
I've actually had to revert back to version 4!
This really is unbelievable... there's no way to get the last version which, although the Pro Tools plugin failed verification, at least system wide worked!
The version released yesterday you can't even play YouTube videos because of the audio issue with SoundID.. HOW WAS THIS EVER RELEASED!!
Please provide a link to 5.7.1.5 and remove the 'latest update' IMMEDIATELY
sonarworks - sorry about that! The "Preset Switch Failed" error is a known issue and the 5.7.3 update which includes a major macOS driver rework actually aims to address this error, as well as other issues on macOS.
Can you let me know whether fully uninstalling SoundID Reference following our guide and then reinstalling the latest version made any difference?
Just in case, we have some workarounds mentioned for the "Preset Switch Failed" error if someone has reverted and is encountering this error as well, see here: "Preset switch failed" error message
I am having the same issue. Please fix this as soon as possible and send an E-Mail to notify us. I depend on your software
This really is ‘Apple Maps’ bad…
Same issue at my studio as well. Just did the entire uninstall/reinstall and even before restarting my computer there was no sound out of YouTube or Spotify after the install was complete... But at least SoundID was showing up in the sound preferences menu. I thought, "maybe I needed to restart the computer like we do with some other software out there" and the moment after doing so, SoundID disappeared from the output options again.
Not only that, but yesterday (and three times before over the past year) I log into my computer in the morning and SoundID has logged me out and independently deleted my speaker profiles (I back them up) for no reason after working fine the night before, and takes me through the entire setup process again. YOU GUYS!!??... c'mon.
Like many of us, I GREATLY depend on your software... this is sad and unfortunate for everyone. There's no way this tested perfectly at development and then ruined your customers after 24 hours. I never understand why companies put things out before being perfectly certain these major issues will not happen. Very reminiscent of "Apple" I agree.
Can you give us a timeline on the fix please?
Thx
wow... just went through all that... installed the pervious version you suggested and am now getting the "preset switch failed" error in this version which ive never seen before.
so to anser this ahead of time: "Can you let me know whether fully uninstalling SoundID Reference following our guide and then reinstalling the latest version made any difference? "
Yes, i followed the guide and now both the new version and the suggested 5.6 fix are both not options.
I had the same pain.. can you go back to ref 4?
Is that an option for you? Only fix I could get working as a ‘for now’ option…
I guess I get to retune my room with ref 4 tomorrow. I would really appreciate some sort of glimmer of a timeline to get back to 5.1 mixes though.
Do we know if the "stereo" calibration done with SoundID will register as a profile for ref 4? I put it in the folder but it wont accept it as an option. Was hoping that wasn't the case.
I luckily saved off my profiles to a Dropbox folder so didn’t lose them as everyone else seems to have.
Not that that’s much help to you… but after you retune, might be a good idea to save the profile ‘out of the Sonarworks’ folder system for safety
Yes. The profile from 5 worked with 4 for me
I manually selected the profile from my DropBox folder and ref 4 accepted it… this was from within the ref 4 software … when it took me thru getting started. Instead of calibrating, I chose the v5 profile and saved as a new name/profile
So essentially, you need to open Ref 4 and load the v5 profile and resave it.. then it’ll be recognised by v4. Hope that helps
Did the same thing and tried with the v5 file in different locations too. When I click on it from that pop up to claim it as the calibration profile it just closes the window and continues to wait for me to choose a file. I'll just retune tomorrow this is insane. What a mess.. really don't like feeling like my job is in the hands of this software.
(meaning it wont allow me to even tell it to accept the file as an option... very much appreciate the clarification and help though)
Rather than trying to load directly into the system wide app/plugin… open the calibration software and there’s an option to load profile there (can’t remember the exact process now as spent all day getting this to work)… then it says ‘give this profile a name’ and you can then load it into system wide.
4.20am here. I’ll try do a screen grab tomorrow if you’re struggling
Yep... did that as well and it crashes it. Thanks again though!
Can you chose ‘open profile’ from the bottom of the page? Or is that when it crashes?
Think I managed to get mine to open it then resave… (sorry if I’m asking you to do what you’ve already tried)
I hope you’ll be able to recalibrate without it crashing as this was the only work around I managed to get working after a day trying to fix this mess. Good luck 🤞🏻
No worries - Yep that's when it crashes after trying the open profile option. No clue how you got it to work. No matter which profile I chose, if they're on my drive or if I place them in the proper sonarworks folder doesn't seem like it's my luck this time. At least ref 4 doesn't take as long to measure.. Best to you as well- thanks so much
Keep me posted. Hope you can sort it… let’s hope there’s a fix ASAP for the actual ‘real’ software
Hi guys,
Thanks for your replies here!
We should have a support article regarding the missing SoundID Reference driver available very soon today (I will update this post once we have it live). I'm afraid we currently don't have an ETA on the fix, but we are looking at this as a priority. I've created support tickets on your behalf (if you hadn't yet submitted a ticket), so our team can address each of your reports individually as well.
Hi all,
An update from our side for anyone encountering the issue with SoundID Reference audio device not showing up after the 5.7.3.17. version update: the issue may be caused by the driver not updating/installing properly during the install process.
Please note that the fix workaround for this is to clean uninstall SoundID Reference and run the installer again. It is imperative that you remove the files, especially the HAL driver, mentioned in the uninstallation guide and then run the installer again.
Update: issue is resolved in the 5.9.1 update of SoundID Reference; download here.
Of course, let us know how this goes and if you observe any other issues with the latest 5.7.3.17 update, thank you!
I’ve just received the email with how to get around things ‘a clean install’. I’ve done that. Several times. Still no joy.
My suggestion would be you include a de-installer as part of the install update. Removing everything except profiles. Having to make everyone go through their system to remove ‘shards’ isn’t ideal
Hi all,
Another update from our side for anyone encountering the issue with SoundID Reference audio device not showing up after the 5.7.3.17. version update: the issue may be caused by the HAL driver not updating/installing properly during the install process.
Update: issue is resolved in the 5.9.1 update of SoundID Reference; download here.
Let us know if you encounter any issues.
Hi sonarworks - sorry for the issue persisting and thanks for your feedback! We updated the workaround steps in the support guide: Missing driver after updating to 5.7.3 [MAC], if you have the chance to give that a try, let us know how it goes!
doesn't work for me.. did this work for anyone else? guys, if the HAL driver was the thing that caused the program not to work, WHY would it make sense to just reinstall the same one in a different way. I dont know much about development I admit.. so i'm just going off of common sense here, but wouldnt you need to put out a NEW driver instead of having us perform the crazy runaround stuff to just have the same HAL driver in place again?
It doesn't work