Posts

100 Things #50: Soundcheck Supports Multiple Interfaces for Ultimate Flexibility

SoundCheck is built on flexibility, and it’s hardware compatibility is no exception. SoundCheck supports multiple audio interfaces and devices, all simultaneously. Freely combine and measure with analog and digital interfaces together. Use a Listen interface like AmpConnect 621, and pair it with an A2B, I2S, or Bluetooth interface for highly customizable tests.

Audio Interface Options in SoundCheck

Learn more about SoundCheck’s Interface & Device Options

Listen’s Audio Interfaces.

Why did we design our own hardware: A look into why our in-house designed and manufactured audio interfaces offer advantages over off-the-shelf products.

Audio over IP with Dante interfaces.

Testing Automotive Audio Via A2B Interfaces.

Testing MEMS Devices with a MEMS Interface.

Using Bluetooth Interfaces with SoundCheck.

 

Video Script: Soundcheck Supports Multiple Interfaces for Ultimate Flexibility

Since 1995, SoundCheck has supported the use of external sound cards and audio interfaces. But did you know that SoundCheck can support multiple audio interfaces and other audio devices simultaneously giving you ultimate flexibility for a wide range of audio test applications?

Here are some examples of test applications that take advantage of this flexibility:

Add additional audio interfaces to expand your channel input and output count, for up to 64 channels of input and output

For example, add Bluetooth, Digital MEMS, I2S, A2B interfaces and even Dante to test these devices

Directly connect a USB audio device like a USB headset, microphone or speaker to test these devices

On Windows OS, SoundCheck supports a wide range of audio drivers including WDM/MME, ASIO, WASAPI, NiDAQ (if using National Instruments hardware) and even Dante. On MacOS, SoundCheck supports CoreAudio. As long as your audio device has an input or output path through a compatible audio driver in SoundCheck, it can be used as an audio source or destination for testing in SoundCheck. Furthermore, SoundCheck can easily support mixed analog and digital signals simultaneously as well as  hardware with different sampling rates.

Let’s look at a hardware setup window in SoundCheck fully exploiting this capability. In my hardware setup you can see a Listen multi channel AmpConnect 621, a BQC-4149 Bluetooth interface, an A2B interface and a USB headset all peacefully coexisting. Note: these devices use different audio drivers, mixed analog and digital signals and even different sampling rates.

With SoundCheck’s auto-delay algorithm, we can even account for latency differences outputting from one hardware device and inputting from another. For example, delays from transmitting a test stimulus to a Bluetooth device like a speaker or headphone.

SoundCheck also has resample and frequency shift post-processing steps to correct for sample rate mismatch and/or hardware clock phase differences as a result of inputting and outputting from different hardware interfaces. This means we can resample and phase align the test stimulus and response prior to analysis to assure accurate measurements.

If you’d like to verify if your device can be used with SoundCheck,  please give us a shout and we’ll check it out!

 

Practical Measurement of Bluetooth and Lightning Headphones

Picture of Bluetooth Headphone Testing Article reprint

Bluetooth Headphone Testing Article

Author: Daniel Knighten.  Reprinted from the July 2017 issue of Voice Coil.

In this article, Dan Knighten discusses Bluetooth headphone testing and Lightning headphone testing, specifically how to overcome the challenges of measuring headphones with wireless and digital interfaces such as Bluetooth, Lightning and USB-C to make the same measurements as on conventional wired headphones.

Full Article

 

 

 

Article Text

Practical Measurement of Bluetooth and Lightning Headphones

For decades, headphones have been passive devices with a direct, analog interface. Today, we are seeing a proliferation of headphones with wireless Bluetooth interfaces and various kinds of new and often proprietary digital interfaces. These new interfaces include Apple’s Lightning port and USB-C. In all cases these headphones present unique challenges to measurement because they cannot be directly connected to traditional test and measurement systems. In this article, we will explore how to overcome these interface challenges in order to make standard measurements on devices with nonstandard audio interfaces.

Closed Loop and Open Loop Testing
To begin, let’s define what we mean by open and closed loop testing. The test configuration for conventional headphone measurements, as seen in Figure 1, is what we term a “closed loop measurement.” This traditional type of audio measurement has been done for years with
all types of transducers (e.g., loudspeakers, headphones, microphones, etc.), and audio measurement systems can make these measurements without problems. The test signal passes from the audio interface through the speaker/headphone where it is converted to sound
pressure. Then, it goes through the microphone where it is converted back to voltage for analysis. The entire path from input to output is on the same interface, usually in the same domain (analog), and most critically, the analysis system’s input and output sample rate are
perfectly synchronous. The entire measurement from signal generation to capture of the device response simultaneously occurs with just a small amount of input to output delay added by the speed of sound.

In headphones with Bluetooth, Lightning, or other unconventional digital audio interfaces, this loop is broken. The input and output are on two different physical devices, which do not share a sample clock, and the signal goes through one or more analog to digital conversion stages. The delay from input to output of the device is likely quite long, compared to classic analog headphones. In fact, the delay might effectively be infinite. In the case of Lightning-connected headphones, there is currently no third-party solution available for injecting a test stimulus into a Lightning port. In Bluetooth systems, the connection is intrinsically non-synchronous. Bluetooth does not provide a synchronous sample clock across the wireless connection and instead relies on asynchronous sample rate conversion and various other techniques to maintain a glitch-free audio stream. This is what we mean by “open loop.” A closed loop system has a closed loop, synchronous signal chain.

An open loop system does not have a continuous or synchronous signal chain. However, SoundCheck makes it possible to measure all conventional parameters of a device, even when those devices are open loop devices, with a variety of tools including:
• Triggered acquisition—support for capturing measurements on playback devices
• File analysis—the ability to analyze signals captured by recording devices
• Resampling—conventional asynchronous sample rate conversion
• Frequency shift—the capability to align signals between non-synchronous systems

Let’s explore how these tools are applied in some typical test scenarios.

Bluetooth Testing
Figure 2 shows a typical Bluetooth setup. Since we are testing the Bluetooth headset using a Bluetooth interface, it is nominally a closed loop scenario. The audio signal comes out of the analog interface and is transmitted via the Bluetooth interface to the headset. It is then played
by the headset and picked up by the ear couplers where it is returned to the analog interface and computer for analysis. However, what makes this an open loop test is that Bluetooth does not transmit a sample clock and, therefore, the receiver and transmitter are asynchronous.

In this case, we will use frequency shift to align or synchronize the stimulus and response waveforms. Frequency shift uses a stationary reference tone to precisely find the difference in sample rate between two waveforms. Once the exact difference in sample rate is found, one waveform is then resampled with reference to the other. Frequency shift enables precise, conventional measurements to be made on Bluetooth devices despite their asynchronous nature.

When compared to a conventional test, only two changes need to be made. First, a short, stationary tone is pre-pended to the stimulus signal (see the Sidebar article). Typically 1 kHz for as little as 250 ms, this signal provides the frequency reference that the frequency shift step needs to align the stimulus and response signals in an asynchronous test scenario. Second, a
post-processing, frequency shift step is inserted into the test sequence between the acquisition and analysis step.

The rest of the sequence is identical to a conventional headphone test sequence and all normal parameters including frequency response, THD, polarity, rub and buzz, and so forth can be measured.

Lightning Headphone Testing
Any device that does not provide an analog or digital input and output is intrinsically an “open loop” device from a test perspective. Headphones that use the Apple Lightning port for connection are considered open loop because Apple does not provide Lightning audio
output adapters. The only device that can currently play audio into a Lightning headset is an iPhone. Measuring Lightning headphones requires an iPhone or similar Apple device to be used to store and play back the test signal (see Figure 3). This creates several open loop testing
challenges. To test a Lightning connected headphone, we will use three specific tools: triggered acquisition, resampling, and frequency shift.

Again, our test sequence will use a short 1 kHz tone, pre-pended to the normal test stimulus but this time it serves two purposes. First, it triggers a record-only acquisition, so that the test is automatically triggered when playback of the test signal begins. It is also used as the reference tone for frequency shift. Also, if our playback device, the iPhone, is using a different sample rate to the audio interface, we may need to use a resampling step. Finally, frequency shift will again be used to synchronize the stimulus and response waveforms. After the response waveform is captured via a triggered acquisition step and has been resampled and frequency corrected, calculation of the desired measurement parameters can proceed as with any conventional headphone.

Pre-written test sequences for both Bluetooth and Lightning headphones are available at no charge from Listen’s website, www.listeninc.com.

Lightning Headphone Microphone Measurements
Since most headphones now also include a microphone, it is worth mentioning how the microphone on a Lightning- connected headset is tested. The test sequence and method
for this is a little more complex, although ultimately it is really just the converse of testing the earphones. Figure 4 shows a typical test configuration. The preparation of the test signal and the use of resampling and frequency shift steps are identical to testing the earphones of a Lightning connected headset.

The difference is that instead of playing back the stimulus through the earphones and using a triggered, record-only acquisition, the stimulus is instead generated using a calibrated speaker or mouth simulator and recorded on an iPhone. The recorded signal is then transferred back
to the computer hosting SoundCheck and analyzed using a recall step to import the waveform into memory from storage on the iPhone.

Conclusions
Bluetooth and Lightning interfaces add an additional level of complexity to testing that is not there with their analog counterparts. However, because the SoundCheck test system is completely agnostic about where the stimulus and the response waveform are generated and
captured, these tests can be carried out with relatively simple modifications to existing test sequences. In fact, it pretty much comes down to a simple modification to the stimulus signal and some additional post-processing steps prior to analysis—all of which are easily automated.
This enables easy characterization and measurement of Bluetooth, Lightning, USB-C, and future devices with advanced digital audio interfaces.

 

Preparation of the Stimulus Signal (sidebar)
In SoundCheck’s frequency-shift algorithm, a Fast Fourier Transform (FFT) is used to extremely accurately calculate the centroid of a stationary tone. The result of this calculation can then be used to align or synchronize two signals even if they are sampled at different rates. A short, stationary signal is necessary for the frequency shift algorithm to lock on to. This is easily achieved by pre-pending a 1 kHz, 250 ms sine wave to the stimulus signal. Since SoundCheck enables the creation of compound stimuli, this short, single-tone burst can be followed with absolutely any test signal (e.g., a Farina log sweep, noise, speech, or other non-sinusoidal
waveforms).
The short sine wave also serves as the trigger tone for triggered record, as is necessary for testing Lightning headphones. The trigger tone clearly identifies the start of the signal. Care must be taken to set an appropriate trigger level. If it is too low, ambient noise can cause false
triggering; too high and it will never trigger. The trigger level should be set so that it is above the ambient noise and below DUT output level. The Multimeter virtual instrument is an ideal tool for finding the optimal trigger threshold.

A typical stimulus signal for open loop headphone test is shown in Figure 1. This compound stimulus works for both Bluetooth headphones where the sine wave is used for frequency alignment and for Lightning headphones where it additionally serves as a trigger and reference for frequency shift.

 

Additional Headphone Test Resources

More about Bluetooth headphone testing

Headphone Testing main page