SoundID Reference speaker measurement troubleshooting guide

Kārlis Stenders

Various tips and troubleshooting steps to successfully set up and measure your speaker setup with the SoundID Reference Measure app.

 

In this article:

 

Extended setup checklist

Before troubleshooting specific stages or error messages, this extended setup checklist will resolve most speaker measurement issues:

  • Disable direct monitoring. The microphone signal should not be routed directly to speakers (you shouldn't hear anything if you tap on the mic).
  • Use a single audio interface for input and output.  
  • Only your audio interface is in the signal path; no other devices (should be present (secondary interfaces and converters, monitor controllers, etc.). Disconnect them completely. You can reconnect everything after the measurement stage; it will not affect the results.
  • +48V Phantom Power is ON to power the microphone.
  • Try at least one XLR to XLR replacement cable in case of a microphone input signal/gain issue.
  • Don't use TRS to XLR or other custom cable solutions for connecting the microphone.
  • Too much input gain can cause trouble. Lower the microphone input gain slightly and raise the output volume for a healthier balance.
  • Check if your audio interface or speakers support any kind of active DSP. There should be no EQ/effects plugins loaded on the microphone input channel, and no room correction features enabled: active DSP features should be fully bypassed, or turned off completely.
  • Set the microphone input channel to mono.
  • No other music production software is open that could hijack the channels you're working with or otherwise interfere. Leave them running only if it's necessary for routing/sample rate/phantom power purposes. Otherwise, quit DAW audio
  • Quit DAWs and other audio apps, shut down any third-party routing/screen recording software (including virtual audio devices). Leave them running only if it's necessary for routing/sample rate/phantom power purposes.
  • Don't use DAW for subwoofer crossover configuration. For stereo setups with subwoofers, quit DAW and follow the instructions here instead: Measuring a 2.0 stereo setup with subwoofer.
  • Use the Test Tones to check your stereo field, make sure they are coming from the correct/intended speaker channels.
  • Stay up to date. Update your interface control software/drivers, and install the latest SoundID Reference update (download here).
  • Inspect your audio interface for physical switches of possibly disruptive settings.
  • Try moving your computer screen monitor/display forward or backward slightly, if the display is directly obscuring the line between the speakers and the microphone.
  • If you see signs of electrical noise on the mic input meter (like a 50 Hz hum), try flipping the power plug for your gear in the socket (where possible) or run your laptop on battery with a USB-powered audio interface. Also, plug your computer and audio gear into the same power outlet or power strip to help prevent ground loops and electrical interference.
  • Try using a different supported sample rate in the Measure app: 44.1 kHz, 48 kHz, 88.2 kHz, 96 kHz, or 192 kHz. Switching sample rates can sometimes resolve unusual sample drift issues.
  • [MAC] Microphone Access is granted for Measure and Systemwide apps in System Settings > Security & Privacy > Accessibility > Microphone.
  • [MAC] In your Mac’s menu bar, click the orange microphone icon and set the microphone mode to “Standard” — do not use “Voice Isolation”.
  • [MAC] 'Play stereo audio as mono' setting is turned OFF in System Settings > Accessibility > Audio.
  • If you are using an integrated device, remove any previously applied calibration profiles (clear all settings/use default settings). For some integrated devices, there might also be a dedicated integrated measurement mode to use; following its dedicated setup instructions: Applying calibration on integrated devices (profile export)

 

 

Hardware Setup

 

Simplifying the setup

Most issues stem from having too many hardware devices in your signal path, like analog consoles, summing boxes, multiple interface setups, PCI units with complex routing, advanced clocking devices, etc. These can cause sample drift or panning discrepancies that make it harder for the software to detect your mic’s location accurately. 

It’s often faster to simplify your setup instead of troubleshooting every component. Remove any extra gear for the measurement stage. You can also use a simple secondary audio interface to replace the entire signal chain (if you have one available), or even use a different computer altogether for the measurements, and reconnect your full setup once you’re done (transfer the created profile). 

This also applies to devices that aren't primarily associated with audio. Even external webcams or other USB devices can appear as audio inputs and interfere with I/O settings. Disconnect or shut down anything you don’t need for measurements, such as secondary displays, monitoring controllers, DAWs, or other audio apps and third-party routing software (Loopback, SoundSource), especially if virtual audio devices are involved.

 

Using a measurement microphone

You will also have to load the SoundID Reference Measurement Microphone calibration profile by entering the profile ID, which is printed on each mic (Sonarworks measurement microphones are calibrated individually for accurate measurements). USB microphones are not supported (such as UMIK-1); only mics with standard audio connectors will work.

While it's technically possible to run the process with a regular vocal or instrument mic, they are designed with intentional frequency response coloring and are not flat. This will result in measurement failure or inaccurate results. Even if a mic has omnidirectional capability, vocal and instrument mics will not work.

 

Note: Measurement microphones require a lot of input gain, sometimes as much as 75% (or even higher) of the available input gain, seemingly hitting the "red" input peaks in the audio interface. This is normal and expected for most measurement mics (incl. third-party mics), and will not cause any measurement problems. 

 

[MAC] Microphone-related settings and permissions

Microphone access permission is required to be granted on macOS for the Measure app to receive the microphone input signal. This should already be allowed and taken care of during the installation or the first launch of the Measure app, but various macOS updates can cause the permission settings to clear. 

If the microphone is clearly providing a healthy audio signal when tested for input in a DAW audio track, but there is no input signal in Measure, check the permission in System Settings > Privacy & Security > Microphone.

Additionally, when performing the measurements, the Microphone mode must be set to "Standard" (not "Voice isolation") from the macOS Menu bar to avoid various issues.

 

[MSR] Mic permission on macOS.png
[MSR] Mic mode - Standard.png

 

[WIN] No input channels available in the Measure app

If no inputs show up within the Measure app in Windows (empty dropdown menu when selecting the input device/channels), it could be due to an automaically blacklisteted ASIO device driver resulting from a previously detected error or a silent crash. 

The blocked ASIO driver has to be removed from the blacklist entry. This can be done either by deleting the blacklist file from the location shown below, or manually removing the driver from the blacklist file; fillow the directions here: [WIN] Blacklisting ASIO drivers in the Measure app.

 

Note: The Library\AppData directory on Windows is hidden by default. To show hidden files, follow the directions here: How to show hidden files Mac and Windows?

 

C:\Users\your username\AppData\Local\Sonarworks\SoundID Reference\Measure\audiodeviceblacklist.config

 

Using an XLR to XLR cable

Using a proper XLR to XLR cable is essential to supply reliable +48 V phantom power to your measurement microphone. From experience, users sometimes try multiple cables before finding one that transmits phantom power correctly.

Don't use custom TRS (jack) to XLR cables; they often aren’t wired to carry phantom power and may lack the required inner connections. This can result in no signal or an unstable signal. Use a standard XLR to XLR cable only.

 

Note: Testing faulty cable/phantom power issues with another mic only works if you use a condenser mic, since dynamic mics do not require phantom power. Even if a secondary condenser mic works, its power requirements may differ, so a partial phantom power problem could still be hidden. Always test with a known-good XLR to XLR cable - replacing the cable is the best way to rule out hidden faults.

 

Subwoofer routing

If you are measuring a stereo speaker setup with a subwoofer with the SoundID Reference for Speakers and Headphones license (also known as "stereo" license), ensure you have it routed accordingly (L and R channels daisy-chained through the sub). Follow the directions here: Measuring a 2.0 stereo setup with subwoofer.

Similarly, if you are measuring a multichannel setup (2.1-9.1.6) with a SoundID Reference for Multichannel license, make sure the subwoofer is connected to its own discrete channel. 

 

Workstation layout

To ensure accurate measurements, clear your desk area - remove any objects between the speakers that could block or reflect sound, such as lamps or other decor. A display monitor is usually fine, but if it's positioned directly between the front L and R speakers, it may interfere with the Listening Spot stage (specifically, during the up-close distance measurements). Similarly, if the monitor obstructs the path between the speakers and the microphone, it can cause issues during the Room Response stage, especially with the front-area measurement points.

In most setups, the software handles a variety of workstation layouts well. If moving your monitor is inconvenient, leave it as is for now and only adjust it if you encounter the issues mentioned above. Shifting the monitor slightly forward or backward is often enough to resolve positioning problems. For a more advanced solution, speaker stands can help improve flexibility during measurement and may enhance your overall frequency response as well.

Your chair doesn’t need to be removed unless it has a high headrest that could obstruct the mic during the Listening Spot or Room Response stages.

 

Using analog gear

Hardware with a lot of analog circuitry — like vintage preamps, analog mixers, or consoles — can add unwanted color to your microphone signal during measurements. To ensure accurate results, it’s best to bypass or remove such gear and use a basic, transparent audio interface if possible.

Modern preamps are typically designed to be flat and do not color the sound noticeably, so even the very basic and budget interfaces are perfectly fine to use. But vintage or analog gear often adds intentional coloration, which can distort the measurement results. Remember, the goal is to capture your speaker and room response exactly as they are. You can always use a basic audio interface for the task, and reconnect your full setup once the measurements are complete.

 

Note: If you’re using a mixer as your audio interface for measurements, watch out for panning and stereo image issues. Double-check all panning knobs, mono/stereo buttons, and any features that might affect channel balance or summing — small settings of this nature can easily cause measurement errors. Use the output test tones in the Measure app to check for any problems as you go.

 

Bypassing active DSP on your hardware

Check if your audio interface or speakers support any kind of active DSP (Digital Signal Processing), especially built-in room correction or sound enhancement features. For example, some speakers come with built-in DSP presets, such as “RoomAdapt” or “SmartEQ” on Genelec SAM series monitors, or “Boundary EQ” on JBL 305P MkII. Audio interfaces can also include DSP-based processing: Universal Audio Apollo interfaces, for instance, can host UAD plugins directly on input channels, and Antelope Audio interfaces feature real-time effects and routing via their control software.

All of these DSP features - whether built into speakers or interfaces - can interfere with the SoundID Reference microphone locating mechanism, resulting in errors, failed measurements, or inaccurate results. To ensure a clean and accurate measurement process, disable any room correction, speaker EQ presets, or sound enhancement modes in your speaker’s control panel or app. Ensure no EQ, reverb, or other effects plugins are loaded on the microphone input channel in your audio interface’s software mixer or DAW. Bypass or turn off all DSP processing completely during the speaker measurement process.

 

Note: If you’re unsure whether DSP is active, consult your speaker or interface user manual, or look for any control software that might be applying hidden processing in the background.

 

Using integrated devices

If you’re using a SoundID Reference-integrated device, make sure to clear any previously applied calibration profiles and reset the device to default settings before starting a new measurement. Similarly to the potential DSP issues described above, previously applied channel delay and other calibration aspects can interfere with the microphone locating and distance measurement mechanisms. 

Some of the integration devices require remeasuring your speakers using an integrated measurement flow, which might differ slightly from the regular Measure app flow - be sure to follow the specific setup instructions for your integrated hardware: Applying calibration on integrated devices (profile export).

 

WASAPI Mode

SoundID Reference Measure runs in ASIO Mode by default, using your system’s ASIO drivers and devices. ASIO mode is generally the most compatible for speaker measurements. However, if you run into problems with I/O setup (like missing device channels or unusual channel names) or issues with mic positioning or distance detection, it could be a driver compatibility issue.

To try an alternative, type “wasapi” in the Windows search bar to launch Measure in WASAPI Mode. In some cases, this resolves I/O or detection problems instantly.

 

Note: WASAPI mode works for stereo measurements only - multichannel layouts are not supported in this mode.

 

_SIDR__Measure_-_WASAPI.png 

 

Listening Spot

Most problems are prevented with proper preparation during the Hardware Setup stage. However, if there are any underlying issues, they will often show up during the Listening Spot stage instead, when the advanced speaker distance measurement and microphone locating mechanisms are introduced - any missed setup faults will become obvious here. 

These issues can cause incorrect distance measurements, failed or unusually long measurements, or the mic position not being located at all. You may see warnings or errors that seem like they’re blocking you for no clear reason. It’s important to understand that these checks are in place to prevent problems from escalating and eventually halting the process during further stages.

For example, if the measured distance between speakers is far off from the actual distance, it doesn’t mean the app is broken or that you should just override it. It means a fundamental setup problem is present and interfering (like sample drift or a routing issue), and trying to work around it will eventually result in failure. The best fix is to pause, go back to the Hardware Setup suggestions above, and resolve the root cause.

 

[SIDR] Listening Spot stage in Measure app.png

 

Once that’s done, use the additional tips and nuances listed below to complete the Listening Spot stage successfully:

  • Don’t ignore distance errors: If the measured distances are much smaller or larger than expected, it means sample drift is likely present and interfering - revisit the Hardware Setup.
  • Check your midrange drivers: If you’re unsure which drivers to use for up-close measurements, follow this guide: Speaker distance measurements: midrange drivers.
  • Workstation layout: Go back to Hardware Setup above and review the Workstation layout.
  • Follow the visual instructions carefully. The exact microphone positioning and aim angles are clearly shown in the on-screen visuals in the Measure app.

  • Try alternative locating signals: In the Measure app Preferences, switch to B or C locating signals if the default A signal (1 kHz) doesn’t work well - this can help in untreated rooms with resonance issues. 

 

Room Response

In this stage, Measure will take 37 measurements to capture the frequency response of your speakers and room. It uses the listening spot you just set as the center point, with a measurement area up to 45 cm around it. The process is straightforward: the software locates the mic, shows its position on screen, and guides you to each new spot. When you’re in the right place, it locks the mic position and runs a quick sine sweep from each speaker. 

No need for a mic stand here - this step is designed for you to hold the mic by hand (unless a multichannel speaker system is being measured, which requires a microphone stand). 

 

Note: In multichannel measurements, the on-screen microphone position is shown as a small dot or circle. This reflects the use of a mic stand with the microphone pointing straight up (90° angle), which is required for multichannel setups. In stereo measurements, the icon looks different, as the mic is intended to be held by hand.

 

Screenshot_2022-03-08_at_14.29.43-111.png

 

If a fundamental setup issue (like sample drift, routing, or stereo image problems) was missed earlier and bypassed during the Listening Spot stage, it will likely become a blocker here. Symptoms include the mic position “jumping” on screen or failed measurements. In that case, return to Hardware Setup and resolve the root cause before continuing.

Otherwise, here are key tips to complete the Room Response stage successfully:

  • Automatic volume adjustments are normal: The Measure app may automatically adjust output volume during this stage based on the levels it detects - this is expected behavior. However, if the volume suddenly increases to uncomfortably loud levels, it may be a sign that the microphone gain is too low. In that case, return to the Hardware Setup stage and raise the mic input gain slightly to achieve a healthier input/output balance.
  • Start close and move gradually: The second measurement point is closer to the first than you might expect. If you move too far too quickly, the software might lose track of the mic. Begin by moving slowly from the center and watch the on-screen mic position to get a feel for the system. Once you're used to it, you can move faster.
  • Follow visual instructions closely: Pay attention to how you're holding the mic and the angle shown on screen. These details affect accuracy.
  • Don’t reposition after locking: Once a measurement point is confirmed, avoid moving the mic. Even if it wasn’t perfectly centered, the software has high spatial accuracy and will calculate the actual mic position precisely. There’s no need to redo points unless something clearly went wrong.
  • Make sure you have enough space: The measurement radius is up to 75 cm (30”) from the listening spot (the first center measurement). If you can’t reach a measurement point due to obstacles (e.g., screen monitor, wall), go back to the Listening Spot stage and reposition your sweet spot slightly to create more space.
  • Monitor-related issues: If you're having trouble locating the mic at front points only (e.g., closest to your screen), your display might be blocking the speaker-to-mic path. Adjust your monitor’s position as explained in the Workstation layout section.
  • Still having mic tracking issues? If the mic keeps jumping or won’t lock onto a point even after reviewing the Hardware Setup, try switching to locating signal B or C in the Measure app Preferences. These alternatives can improve detection in certain rooms.

 

Note: In multichannel measurements, a microphone stand is required (mic secured on the stand at a 90° upright angle). In this case, the on-screen mic icon appears as a dot/small circle. For stereo measurements, the mic is hand-held, and the icon differs accordingly (a microphone icon is displayed).

 

Results

Once the measurement process is complete, the final calibration profile will be generated and displayed. This stage is usually straightforward, but here are a few things to be aware of:

  • Be patient: Saving the .swproj file (speaker profile) may take some time. Avoid closing the app prematurely - let it finish. 

  • Profile save not completing? This spinning wheel on the save button can sometimes be caused by special characters in the file path, especially in your computer username, which is part of where the profile is saved. Usernames with non-English letters or symbols (e.g., á, ø, č, @, #) can trigger silent file-saving issues on some systems. Try creating a temporary user account with only standard English letters (A–Z) and run the measurement there. If the save works, the issue was likely due to character encoding in the file path.

  • Using an integrated device? If you’re working with an integrated device like DAD or Avid MTRX and encounter a device-specific error not listed in the Warnings & error messages section below, refer to the device-specific guide instead: Applying calibration on integrated devices (profile export). 

  • High-frequency roll-off above 15 kHz: If your speaker measurement results show an abruptly dropping curve above the 15-18 kHz range (measurement top end is "cut off" as shown in the screesnhot below), this may be caused by built-in DSP processing in your speakers or other hardware. Check if any EQ, filtering, or processing is active and disable it temporarily. Return to the Bypassing active DSP on your hardware section above for guidance. 

[MSR] Measurement top end is cut off.png

 

Warnings & error messages

Almost all of the potential warnings and error messages in the Measure app will lead you back to the Hardware Setup and point to a potential setup fault there:

 

“Mono signal detected” warning

Also known as "Routing issue detected", this warning means the software has detected identical or overlapping signals in both channels (even subtle inaudible channel bleed can cause this). It’s often caused by incorrect panning, misconfigured interface control software, or physical routing issues. Look out for hidden interface control software settings like “Enhanced Stereo,” “Channel Grouping,” or “Spatial Mode” that may force stereo into mono internally. Check your output routing, test your XLR cables, and confirm your subwoofer isn’t introducing a crossover or routing fault when measuring a subwoofer setup. Even if playback sounds correct, the measurement system needs truly independent left/right signals.

Return the Extended setup checklist and Hardware Setup sections for detailed solutions.

 

“No signal detected” error during input/output setup

Caused by missing input - common causes include a disconnected mic, phantom power off, incorrect input selected, bad cable, interference from routing software, or microphone/input permissions in macOS Security & Privacy settings. Double-check the channel selection, confirm +48 V phantom is on, test the mic and cable in the OS meter, and disable any routing apps or DAWs.

Return the Extended setup checklist and Hardware Setup sections for detailed solutions.

 

“High noise levels detected” warning

Signifies excessive background noise or feedback, or unhealthy input gain/output volume balance. Edge-case scenarios are possible, such as the "Voice isolation" microphone mode enabled in macOS settings (switch to "Standard" mode from the menu bar); some edge cases might be unknown. Prevent this by muting direct-monitoring channels, increasing speaker output volume (not mic gain), and lowering the mic input level. Ensure the room is quiet and gain staging is balanced.

Return the Extended setup checklist and Hardware Setup sections for detailed solutions.

 

“It is taking too long to finish this step” error

Usually occurs during the mic input gain calibration in the Listening Spot stage. This can be primarily triggered by sample drift, multiple interfaces active, routing conflicts, or software interference, although gain structure and phantom power causes are also possible. Carefully review the I/O chain, simplify and reduce as much as possible; consider using an alternative/secondary audio interface for the measurements.

Return the Extended setup checklist and Hardware Setup sections for detailed solutions. 

 

“The distance between the speakers is less than 50 cm” error

This pops up if the measured speaker distance is less than the minimum distance required. If the actual distance is significantly bigger, the main cause is sample drift, routing, and clocking issues. Simplify your signal chain to pin down the problem; consider using an alternative/secondary audio interface for the measurements.

Return the Extended setup checklist and Hardware Setup sections for detailed solutions. 

 

“Unable to measure distance from the Right/Left speaker” error

This can occur during the Listening Spot stage when the Left speaker is measured successfully, but the Right speaker either stalls (or the initial L speaker up-close measurement fails with the equivalent error). Common causes include stereo panning imbalances, excessive input gain, sample drift, physical obstructions between speakers, or L/R outputs being swapped. Also, check for incorrect mic mode on macOS ("Voice Isolation" used instead of "Standard"), and ensure you’re measuring the correct midrange driver. 

Return the Extended setup checklist and Hardware Setup sections for detailed solutions. 

 

“Multiple audio devices selected” error

This occurs when two different devices are used for input and output. The Measure app requires a single audio interface for both input and output. Multiple devices cause sample drift and clocking issues, interfering with the distance measurements and the mic locating mechanism. Use a single device for your I/O.

Return the Hardware Setup, and the Simplifying the setup section for detailed solutions. 

 

"Microphone calibration profile download error" 304

Depending on various factors, the microphone calibration profile, which is downloaded and stored locally after entering the profile ID in the Measure app, might get corrupted. To resolve this, delete the locally stored file to initiate a fresh download:

  1. Quit the Measure app, and navigate to the following directory:
    • macOS: HD/Users/your username/Library/Application Support/Sonarworks/SoundID Reference/Measure/micprofiles
    • Windows: C:\Users\your username\AppData\Local\Sonarworks\SoundID Reference\Measure\micprofiles
  2. Delete the locally stored mic profiles from the 'micprofiles' folder.
  3. Relaunch Measure and proceed to the mic profile ID input field again - it should now load successfully.

 

Note: The User/Library and user\AppData folders on macOS and Windows are hidden by default. To enable showing hidden files and folders, follow the instructions here: How to show hidden files on macOS and Windows?

 

Screenshot 2022-06-27 at 13.42.23.png

 

2023-12-13_13-42-30.png

 

“:( Oh dear, Measure has crashed” error

Measure app crashes may occur on launch or during the measurement process due to sample rate mismatches, unstable ASIO drivers, or a faulty installation. If the issue persists on Windows (most common case), it will likely be resolved by pinning down a problematic ASIO driver and blacklisting it: [WIN] Blacklisting ASIO drivers in the Measure app.

A fully clean reinstall can also be tried for a solution: 

 

123.JPG

 

[WIN] Mic profile download error - 316 / UTF-8

A message may appear for Windows users when entering the Mic ID in Measure, which mentions:(json.exception.type_error.316) invalid UTF-8 byte at index XX: XxXX. This is a Unicode issue and can be resolved by enabling the Beta UTF-8 feature in Windows settings. 

  1. Use the Win+R key command to open Run.
  2. In Run, type intl.cpl, and click OK. 
  3. Go to the Administrative tab of Region settings and click Change system locale...
  4. Enable the "Beta: Use Unicode UTF-8..." box > OK. 

A reboot might be required.

 

image (38).png

 

Advanced troubleshooting

If the issue persists after going through the steps above, SoundID Reference includes logging and debug tools that can help identify the root cause. These are especially useful when contacting the Support Team, who may request the following:

  • Software log files: SoundID Reference automatically generates logs (including the Measure app) that can reveal configuration or device issues. You can find the log file location here: Locating SoundID Reference log files.
  • Debug Mode: Enable Debug Mode in the Measure app Preferences to generate more detailed logs and save raw audio files from the measurement process. This is particularly helpful for investigating persistent or unusual measurement issues.

 

mceclip1__1_.png

 

Frequently asked questions

 

Why am I getting feedback noise when trying to calibrate speakers?

If the microphone signal is coming out of the speakers directly (direct monitoring), this will result in an unwanted feedback loop. The microphone signal should be feeding into the Measure app and should be present in the Measure app visually only (signal showing visually in the input meter). You should not hear the microphone signal from the speakers if you tap on the microphone or talk into it. 

Ensure that direct monitoring is disabled (your microphone input is not routed directly to your audio interface outputs) by muting the microphone input channel in the interface control software, or turning down the input channel fader.

 

Note: Some interfaces have a dedicated button or switch to toggle direct monitoring, or a rotary knob to blend direct and software signals: set it fully to software/USB.

 

mceclip2.png

 

mceclip0.png

 

mceclip1.png

 

 

[WIN] Why is the "Next" button invisible (unable to proceed)?

In rare cases on Windows, the Measure app may display scaling issues, causing buttons and other elements to fall outside the window (the "Next" button becomes invisible as it is outside of the app window borders). See here how to fix it: [WIN] SoundID Reference app scaling issue - content out of borders. 

Related to

Was this article helpful?

18 out of 26 found this helpful

Have more questions? Submit a request

Related articles

1 comment

Gabriel Mounsey
0

Not so sure that I should be bypassing the DSP on my Ex Machina Ganymede's as that aligns the phase response of the speakers- they measure differently with or without it on. Would like a little more updated info on this sort of DSP and if its ok to keep enabled.

Please sign in to leave a comment.