No sound/no calibration effect in SoundID Reference standalone app

If there is no calibration effect or no sound present when the SoundID Reference standalone app is launched, check our suggestions below to troubleshoot and resolve the issue. 

 

In this article:

 

No sound/no calibration effect: macOS

In the majority of cases, SoundID Reference malfunctioning in regards to the lack of sound or calibration effect is a result of either an incorrect setup or software incompatibility. We have gathered a list of quick and simple resolutions for the most common issues. Please look through the following guide if you either don't hear any audio at all or can't notice the calibration effect.

 

Check Your Equipment and Software

Before you start digging deeper, check on a few simple things. Please make sure you have double-checked on the following before you start troubleshooting further.

  • Cables, connections, adapters, ON/OFF switches, etc.
  • Audio interface (virtual mixer software I/O channels and/or physical outputs)
  • Final physical output (monitor controller, speakers, headphones)
  • Audio source app (media player, browser, DAW, etc.)
  • SoundID Reference master fader and the Dry/Wet knob
  • Check if calibration in the SoundID Reference app is enabled
  • You may play a test tone from the SoundID Reference app Output settings to define whether the signal gets through to the selected output device.

 

Check your App

First, we will give you a basic idea of how the app works: SoundID Reference acts as a middleman between the audio sources on your computer and the hardware output device. The audio signal from various sources on your computer is routed to SoundID Reference, where it gets calibrated, and is then sent out to the physical output device selected in SoundID Reference.

 

2021-07-06_10_28_44-2021-07-06_09_39_40-Greenshot__1_.png


Therefore, a signal going into the SoundID Reference would be called SoundID input, as the signal going to the physical output device would be classed as SoundID output.


Thus first of all we advise you to check on your app settings paying extra attention to both input and output being set up correctly. Please follow the link for further guidance in regards to in-app activity.

 

Your Mac Preferences

Your next step would be referring to your MAC Preferences. Once you install and launch SoundID reference the special virtual device is created. Usually, SoundID reference automatically sets it up and selects once you run the software.

Go to: System Settings -> Sound -> Output

Sound_settings.pngMake sure that SoundID Reference is assigned as your audio output device correctly so you would route the sound to the SoundID Reference. Double-check with the Mute box and make sure that you haven't accidentally ticked it. The same applies to your audio interface - make sure it's not muted or on low volume. 

 

NOTE! If you don't see the driver in the list, please proceed to SoundID Reference Driver.


Audio/MIDI Settings - Muted output

Every audio device stores a profile in the Audio MIDI Setup utility. As SoundID Reference has its own driver it will be displayed as a separate virtual audio device.

Go to: Applications -> Utilities -> Audio MIDI Setup

Audio_Midi.png

Make sure that the outputs for the SoundID Reference virtual audio device and the physical outputs are at audible levels. Double-check and ensure that it is not muted for the Virtual Device, nor for the audio interface in use. Sometimes if you have encountered an error within the app, it might be a good idea to delete the profile and restart the app so it would re-create itself.


NOTE! Sometimes additional 3rd-party virtual audio devices (virtual cables, systemwide mixers, etc.) might get involved in the signal chain. That may overcomplicate or overload the signal routing. Normally they would appear as aggregate devices in the list. Therefore, if the aggregate device is not essential, we would advise removing them.

 

Privacy & Security

We don't know whether your computer feels extra cautious today. We are absolutely sure that our software is safe to use even if your computer didn't suppose so. Therefore, make sure that SoundID Reference isn't being blocked by Mac Privacy & Security Settings.

Go to: System Settings -> Privacy & Security

 

Make sure that Sonarworks software hasn't been blocked. If it shows as blocked, click on the Open Anyway button.Allow_done.png

Double-check that Microphone Access is granted for SoundID Reference. You can read more about granting Microphone Access to SoundID Reference here.

 

SoundID Reference Driver

SoundID Reference creates a virtual audio device that processes all the system audio. Sometimes, due to a corrupt installation or incorrectly set permissions, the virtual audio driver file (HAL) doesn't get created.

Go to: /Macintosh HD/Library/Audio/Plug-Ins/HAL/


Check if the SoundID Reference.driver file is there. If not, make sure that you have completed Security & Privacy step, and please re-install the software. Keep this folder in the background to check whether the file had been created.

HAL_Location_done.png

I/O Driver Update

In some rare cases, the issue might appear due to your Audio Interface driver incompatibility. Even though it seems to be working fine, it might not be fully adaptable to the OS version or hardware you are having. Thus, once you try using your Interface with SoundID Reference, it may provoke an error. 

As we may not know your interface specifications and their capabilities, we won't be able to provide you with straightforward instructions or an action plan. You would have to investigate and make sure that you have the most up-to-date drivers that fit your hardware and software specs. 

 

Adjust output device gain

When sound is lost after computer sleep, it may be worth trying to disable the Adjust output device gain feature. To do so, go to Preferences -> Adjust output device gain -> set to Off

 

Terminal Core Audio Reset

Core Audio is the main audio driver that handles all of the sound work involved. When the issues appear, especially when it comes to noise, no sound, or calibration effect, resetting the Core Audio process should solve your problem. Launch Terminal and type in the following command:

sudo killall coreaudiod

 

Terminal.png

IMPORTANT! This step is performed at your own risk. Only proceed if you are an advanced user. In some very specific cases, it may cause permanent damage to your Core Audio driver and may result in a full reinstall of your Operating System!

 

No sound/no calibration effect: Windows

The calibration effect is usually quite dramatic and cannot be missed. If you can't hear any change (or any sound at all), that indicates a fault in the audio settings. 

To give you a better idea of where the problem could be, here are the basics of how it works: SoundID Reference works as a middleman between the audio sources on your computer and the hardware output device. The audio from various sources on your computer is routed to SoundID Reference, gets calibrated, and is then sent out to the physical output device selected in SoundID Reference.


2021-07-06_10_28_44-2021-07-06_09_39_40-Greenshot__1_.png

Essentially, there is a signal going into the SoundID Reference app and a signal going out of SoundID - input, and output. To solve the problem, we must make sure that both input and output are set up correctly. 

 

General troubleshooting tips

  • Check audio signal levels at every point of the signal processing chain. At no point in the signal chain the audio is too low or muted  - check the following:
    • Audio source app;
    • SoundID Reference master fader and the Dry/Wet knob;
    • Windows sound settings and mixer;
    • Audio interface (virtual mixer software I/O channels and/or physical outputs);
    • Final physical output (monitor controller, speakers, headphones).
  • Check if the signal is successfully routed into the SoundID Reference app. If you can see that the VU meters in SoundID Reference are not reacting to the playback, the signal doesn't reach Reference and the input part of the chain should be checked. If the VU meters in SoundID Reference are reacting to the playback, but there's still no sound, the output part of the chain should be checked.
  • Calibration in the SoundID Reference app is enabled.

 

VU_meters.png

 

Driver-specific troubleshooting

Depending on which audio output driver type you selected in SoundID Reference output settings, there are different additional troubleshooting steps that you can try. You can read more about the different audio driver types here.

 

Windows audio device insert (APO)

If you select the Windows audio device insert (APO) driver as the output driver type in SoundID Reference, no additional settings are necessary for all system sound to be calibrated.  If there is no sound when playback is initiated, please ensure that:

* The correct output device is selected in Windows sound settings - it should be the same device that was chosen as the output device in SoundID Reference. Note that in some output devices, every output channel pair is seen by Windows as a separate device. 

* There are no applications that are currently using your physical output device in exclusive mode, preventing different applications from using it.

IMPORTANT! When first selecting this driver type, it can take up to 25 seconds to initialize on each device you select. During this time, some playback issues can be noticed. 

 

Virtual Windows audio driver

If you select the Virtual Windows audio driver as the output driver type in SoundID Reference, a SoundID Reference Virtual Audio Device is created and can be found in the Sound control panel and when clicking on the sound tray icon. In order for SoundID Reference to process the sound, SoundID Reference Virtual Audio Device has to be selected as the Default playback device in Windows Sound control panel. You can do so in two general ways:

  • Click on the speaker icon in the system tray (bottom right corner of the screen) and click on the ⌵ drop-down arrow to see the currently available playback devices. Select the SoundID Reference Virtual Audio Device as your playback device:

Win_sound_tray_icon_WASAPI.png

  • Go to Windows Settings > System > Sound and open the Sound Control Panel on the top right side of the window. You will then be able to set the Sonarworks Virtual Audio Device as the default System output:

    Sound_control_panel.png 

    Default_device.png

 

You can also ensure that SoundID Reference Virtual Audio Device the Default playback device as long as the SoundID Reference app is running by enabling the Keep Reference the default system output device option in Reference app preferences.

Keep_default_settings.png

In case you want the sound that is coming from your audio/video communication software to be calibrated by Reference just like the sound from other sources on your computer, please note that some 3rd-party audio and video communication applications use the output that was set as the Default communications device. Unless you want to specifically use different devices for communication and other audio playback, it is recommended to make SoundID Reference Virtual Audio Device the Default communications device as well.

Default_comm_device.png

 

In some cases, 3rd-party audio applications with extensive audio processing capabilities will attempt to take exclusive control of the Default output device. It may prevent other audio applications from using that device. If that happens unintentionally, disabling the Exclusive mode checkbox in the SoundID Reference Virtual Audio Device properties may help. To do that:

  • Go to Sound control panel
  • Right-click the SoundID Reference Virtual Audio Device and click Properties
  • Go to the Advanced tab
  • Uncheck the Allow applications to take exclusive control of this device checkbox
  • Click OK 

 

Device_advanced_properties.png

 

Virtual Windows audio to ASIO driver

The same troubleshooting steps as the ones for the Virtual Windows audio driver apply to the Virtual  Windows audio to ASIO driver. Those two output driver types are very similar. They both create a virtual output device, which should be selected as the Default output device. The only difference is that the Virtual Windows audio to ASIO driver is meant to be used with hardware output devices that support ASIO. This driver type translates the Windows WASAPI audio signal format into the ASIO signal format.

Note that this driver type doesn't create a native ASIO virtual device, but rather a call translator. Therefore, it does not feature any native ASIO benefits, such as low latency. It is recommended to use this output mode only with ASIO-exclusive devices that don't have a WASAPI driver (certain interfaces from Steinberg, Helix, etc.) as there is no alternative for systemwide calibration for these devices.

 

Virtual ASIO to ASIO driver

First and foremost, note that this driver type will not calibrate system audio. This driver type creates a virtual ASIO audio device, which can be selected as the output in DAWs or certain media players.

This driver type is pretty straightforward. In case the audio signal isn't reaching SoundID Reference (VU meters are not reacting), please ensure that the Sonarworks ASIO Driver ("physical device name") output device is available and selected as the output in your DAW/player. Sometimes, a computer restart is necessary for the Virtual ASIO to ASIO driver to be correctly seen by other software.

 

mceclip0.png

 

3rd-party Virtual Audio Device compatibility

If any additional 3td-party virtual audio devices get involved in the signal chain (virtual cables, systemwide mixers, etc.), the signal path may become too unpredictable and overcomplicated for regular troubleshooting techniques. In such cases, please send a request to the Sonarworks support team as well as the support team of the other involved application - we will review and troubleshoot such cases individually. Make sure to include as much detail about the signal path as possible.

 

Was this article helpful?

8 out of 32 found this helpful

Have more questions? Submit a request

11 comments

0

EDIT: I resolved the issue after further troubleshooting. Posting here for future users that may run into the same problem.I had previously created a virtual audio device using Loopback and routed the output of certain apps to it. Any apps routed as such will not work with SoundID no matter what you do to troubleshoot. Deleting Loopback did not delete the virtual audio device for some reason, so I had to manually delete all the related files in Library and ~Library and that did the trick after a reboot. 

---------------------------------------------

I have been having this issue with Reference 4 Systemwide and upgraded to SoundID thinking it would fix it, but it's still happening. I've followed every troubleshooting step and everything is set up exactly as it should be. Everything is also set up correctly within SoundID itself, and when I test the output, I do hear the "left, right" test voice in my headphones. I am on an M1 MacBook running Monterrey version 12.3.1 (21E258) and I'm simply plugging in my Sennheiser HD650 directly into the headphone jack. When I play audio from Spotify, Safari or any other audio really, I can hear it through my headphones, but the I/O meters in the SoundID app show no signal coming in or out and there is no calibration effect.  Please help! 

 

 

 

Zane
0

Hi Alvaro,

Thanks for reaching out!

Sorry to hear you are encountering an issue with this. Could you double-check that SoundID Reference has been granted microphone access? For details on how to check this, see here: SoundID Reference microphone access requirement in Accessibility preferences [MAC]

0

Hi Zane,

Thank you for your reply. Everything is set up per the troubleshooting steps, including microphone permissions yet it still doesn't work. 

 

0

I have a MAC M1 running Ventura 13.3.1 and Reaper v7.22.  I installed the software yesterday  but noticed that when I hit play in Reaper, nothing was coming in or out in the SoundReference window, yet the audio was affected. However, when I played back my bounced file, the system audio of the computer DID activate the input-output of the SoundReference window and the volume was lower, but also the sound was different. Reaper did not have this issue before. 

Today, the software is not affecting Reaper playback at all, and still no input-output action on the SoundREference window. Only system audio is affected by calibration, yet sounds weird…bass is reudced, and a upper mids push. 

How do I get SoundReference to ¨read¨ reaper´s audio? My soundcard (an RME FIREFACE 800) show up on the SoundReference app. everything SEEMS to be ok. Test tones work, as well.

 

What could be the problem????

0

Any chance I could talk to someone??? Willing to pay. I am only happy I haven´t purchased the software..I guess I have 19 days left to figure out the problem…PLEASE PLEASE if there is anyone out there, PLEASE HELP!!!

0

Oscar Chabebe it sounds like you still have a bit of a learning curve to tackle for the SoundID Reference DAW plugin and standalone app. I highly advise you to read through these setup guides and also see the videos in them:

Reaper is a DAW. Advanced audio applications such as DAWs have their own I/O settings (unlike the regular audio apps, which go to the operating system-assigned output by default). So if you wish for the Reaper signal to be processed by the standalone app (instead of using the DAW plugin format), you'll have to assign the standalone app driver as your Reaper output (in Reaper output settings).

I highly recommend you have a closer look at all basic features and setup content linked in the software and its tooltips. If you still need further assistance, please click on the ‘Submit a request’ button (available under any support article). Thank you!

0

I'm using MacbookPrp M1pro with Sonoma and Motu Ultralite M5. Everytime I turn on (or reboot) Motu Ultralite, sound doesn't come out until reset coreaudio in terminal app as it's guided in this page. (weather the macbook reboot or not). How do I fix this issues?

0

Heejong Yoo A support ticket has been created and we'll be in touch to investigate the issue you're facing. 

1

When SoundID stops working, is there a way to get it to work again without rebooting my Mac? The app is running, recognised by OSX and enabled, but I get no sound. If I quit the app, sound works. If I reload the app, it doesn't work and I have to restart my machine to get it to work. 

What am I doing wrong?

1

Pretty much every morning when I sit down at my computer (M1 pro MBPro, 32GB RAM, MacOS Sequoia 15.5) I don't hear any audio from anything.  Some days I can solve it by quitting Sound ID Reference and restarting it.  Some days I have to also reboot my interface (Focusrite Scarlet 16i6).  Some days I have to additionally Restart the Playback engine from Sound ID Ref.  Today none of those worked – still no sound from any app.  So now I will restart the computer and see if that works.

Why does this keep happening?  I've going through all the troubleshooting steps and everything is setup correctly and all permissions are correct.  If I quite SoundID Reference the audio works perfectly.  How to fix this?  What should I check?

0

I am running a 16in Nov 2024 Macbook Pro M4 Max, 128GB RAM, Sequoia 15.7.4, and SoundID Reference 5.13.2.  I get zero audio output from the Sound ID Reference stand alone app outputting to my external headphone jack on the macbook.  I have followed this guide to completion with no results.  I have done a deep uninstall, erasing every file and user data of sonarworks on this machine, re-downloaded the latest install packet from this website, reinstalled, and got the same results.  Yes, my audio/midi volume, sample rates, bit depths, etc. all match.. I have confirmed no fader is down below audible range.  I have allowed the app microphone access, allowed it to run in the background, etc.  I have gone to the terminal and performed a hard kill of my core audio and it changed nothing.  I can see the meters on the IN and OUT of the stand alone app but no actual audio signal hits the jack.  If I change the output in sonarworks to a different output it has the same problem.  If I immediately switch my sound output of my OS to the external headphone or built in speakers - i have instant audio.  This is clearly a driver issue on Sonarworks part.  I have found no forum with solid answers.  They all end in someone getting a support ticket and then the trail going cold. I have tried every weird trick to try to resolve potential clocking issues or audio driver handshakes.  Can Sonarworks please provide assistance??

Please sign in to leave a comment.