Troubleshooting Hardware with Self-Test Sequences

Additional Resources for SoundCheck

Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.

Video Transcript: Troubleshooting Hardware with Self-Test Sequences

The first thing you should do if you’re getting unexpected audio measurement results, is run a self test sequence to make sure the audio interface is correctly configured. These sequences send a test signal through the output and compare it with the signal received in the looped back input. If the frequency response, sensitivity, and latency are as-expected, it is configured correctly.

You can find hardware self-test sequences in SoundCheck’s Sequences > calibration folder.

For each type of Listen hardware, there is a specific sequence that automatically routes the signal back from output to input. If you are using third party hardware, you can use the generic self test sequence. This one requires you to physically loop back inputs and outputs.

Let’s take a look at the AmpConnect 621 Self Test sequence. It includes a PDF that explains how the sequence runs and what expected results are.

You can see here I have the AmpConnect 621 connected and configured in my Listen hardware editor. SoundCheck automatically reads the Vp values and calculates the latencies for Listen Hardware.

If you’re using third party hardware, it is possible for these values to be set incorrectly, so the voltage going out is not what is accounted for or the latencies might be incorrect.

Let’s run the self-test sequence. It is going to give me some instructions.

It’s automatically switching the signal paths, testing all of my inputs and outputs. And the end result gives me a pass or fail to confirm if my interface is working correctly or not, as well as all the test results.

Here we see that the frequency response looks good, my latencies are correct (just off maybe a little), and my noise spectrum and the amplifier response also look good.

If my self-test had failed, for example the sensitivities or latency were wrong, I’d need to recalibrate the hardware input, import in the calibrated hardware files, and do some additional troubleshooting.

If you’re using a WDM driver for your interface, it’s also important to check the Windows volume mixer is set to 100%.

This can also be checked in the Playback and Recording tab of the sound settings. Make sure the levels are set to 100%, and any Audio Enhancements and Spatial Audio are disabled. Note that this is only applicable for WDM or WASAPI devices, as ASIO devices don’t go through the Windows mixer.

Once you’ve confirmed your audio interface is correctly configured, you can move on and troubleshoot the rest of your signal chain – the cables, speakers, microphone etc.