Registration required

The content you have requested is available only to registered visitors. Please complete the short form below (all fields are required).

  • 简体中文 简体中文 Chinese (Simplified) zh-hans
  • English English English en
Listen, Inc.
  • Products
    • AUDIO MEASUREMENT
    • System Overview
      • What Soundcheck Measures
      • SoundCheck for R&D
      • SoundCheck for Production
      • Innovation
    • SoundCheck Software
      • Making Measurements
      • Algorithm Highlights
      • Integration
      • What’s New?
      • Packages, Modules & Pricing
      • Support Contracts
    • Audio Measurement Interfaces
      • AudioConnect 2 (2 channel))
      • AmpConnect 621 (6/2 channels)
      • AudioConnect 8×8 (8 channel)
      • AudioConnect 6×2 (6/2 channel)
      • AmpConnect ISC (2 channel)
      • 3rd Party Audio Interfaces
    • Audio Testing Hardware
      • Microphones & Amplifiers
        • Measurement Microphones
        • Microphone Power
        • Audio Test Amplifier
      • Specialist Test Interfaces
        • Bluetooth Audio Measurement Interfaces
        • MEMS microphone Interfaces
        • DC Connect
      • Audio Test Accessories
        • Turntables
        • Halo Automotive 6-Mic Array
        • Automotive Audio Test Kit
        • The SCC-1 Ear Coupler
        • Other Measurement Transducers
        • Impedance Box
        • Calibrators
    • NOISE & VIBRATION MEASUREMENT
    • System Overview
    • NoiseCheck Software
    • Noise & Vibration Interfaces
    • Noise and Vibration Testing Hardware
  • Applications
    • Headphones & Headsets
    • Loudspeakers & Microspeakers
    • Microphones
    • Automotive
    • Communications
    • Smart Devices
    • Hearing Aids
    • Audio Electronics
  • Support
    • Get Support
    • User Documentation
    • Knowledgebase
    • Training
    • Sequences & Resources
    • Drivers
    • Register Product
    • Report a Bug / Request a Feature
  • Resources
    • ‘Sound Matters’ Blog: Audio Measurement Expertise
    • Test Sequences
    • Article Reprints
    • Published Papers
    • Technical Notes
    • Measurement Services
    • Useful References
  • News & Events
    • News
    • Events
  • About Listen
    • Listen, Inc.
    • Contact
    • Distributors & Reps
    • Careers
    • Privacy Policy
  • Menu Menu

Display on Blog Page. This is a secondary category. Should usually also be in a primary category unless it is just intended as a blog post

The Value of Normalized Distortion

December 12, 2025/in Blog, Uncategorized/by Julius Wijono

Normalized Distortion, or Frequency Normalized Distortion, is a distortion measurement algorithm first proposed by Listen’s president, Steve Temme (then at Bruel and Kjaer) in a 1993 AES paper. Although it’s been available in SoundCheck since 1996, it’s only recently gained traction. This is likely due to a renewed interest in correlating measurements to audibility – something that we’ve always considered important at Listen – and also because it is the only way of accurately measuring some new types of microspeakers. Let’s take a look at how it differs from conventional distortion measurement and why it is valuable for identifying the cause of distortion.

A typical speaker response, shown in Fig. 1, isn’t flat. There are typically amplitude irregularities due to reflections and resonances, and high and low-frequency roll-offs due to the passband nature of the transducer. This introduces some interesting artifacts when we look at harmonic distortion.

 

Fig. 1. Typical loudspeaker response

Fig. 1. Typical loudspeaker response

 

Fig. 2 shows the fundamental, second and third harmonic of a speaker. If we’re measuring harmonic distortion by sweeping from 20 hertz to 20 kHz, to measure the second harmonic, our filter tracks at twice the stimulus frequency and goes out to 40 kHz. Let’s assume that the second harmonic is 20 dB below the fundamental, i.e. 10% distortion. The third harmonic starts at three times the fundamental frequency and goes to 60 kHz, and let’s assume that this harmonic is 40 dB down below the fundamental, or 1% distortion. You can see the bumps and dips in the response align with the fundamental as the harmonics are filtered by the same linear frequency response.

 

Fig. 2. Loudspeaker response with second and third harmonics at their measured frequencies

Fig. 2. Loudspeaker response with second and third harmonics at their measured frequencies

 

The problem with conventional THD is that we always plot the harmonics at the stimulus frequency and then we compare the harmonic level to the stimulus level at the stimulus frequency as shown in Fig. 3.

 

Fig. 3. Loudspeaker response with second and third harmonics shifted to stimulus frequency

Fig. 3. Loudspeaker response with second and third harmonics shifted to stimulus frequency

 

You can see that the responses are shifted along the x-axis to start at 20 Hz, like the stimulus frequency. This change in alignment between the harmonics and the stimulus causes the irregularities to be offset, and the high and low-pass roll-offs look entirely different.

 

Fig. 4. The effects of aligning harmonics with the stimulus before calculating THD

Fig. 4. The effects of aligning harmonics with the stimulus before calculating THD

 

When we now calculate THD, (Fig. 4) we get some interesting results. Even though we showed earlier that the second harmonic was uniformly 20 dB down, when we calculate it this way, the distortion appears much higher at low frequencies because the fundamental rolls off sooner. Instead of being -20 dB (or 10%) at 20 Hz, it’s actually only -3 dB, which is equal to 71% distortion.

We see the opposite effect at high frequencies; the distortion rolls off prematurely compared to the stimulus frequency. This means it’s calculated to be -30 dB, or 3.1%, rather than -20 dB (10%).
In the pass-band region, the distortion could be under, or over-estimated, particularly around the resonances and reflections, where the calculation differences are more pronounced. This isn’t limited to the second harmonic; it’s the same for the 3rd and any subsequent harmonics so all these differences stack up.

If you look at a typical THD measurement of a loudspeaker, you’ll notice it’s always high at the lowest frequencies and rolls off at high frequencies. This is because conventional distortion measurement methods tend to over-estimate distortion at low frequencies, and under-estimate it at high frequencies.

So why does this matter? If you want to truly understand what’s causing your distortion, you need to separate the linear from the nonlinear. The good news is that this isn’t difficult – it’s just a small change in the order of operation when the THD is calculated.

What we proposed back in 1993, and I am still a strong advocate for today, is calculating it as follows: Instead of plotting the harmonics at the stimulus frequency and comparing it to the fundamental at the stimulus frequency, reverse the order. Plot the harmonics at the actual measured frequencies, compare it to the fundamental at the harmonic measured frequency, calculate the percent distortion, and then plot it at the stimulus frequency (Fig. 5). This is what we call Frequency Normalized Distortion.

 

Fig. 5. THD measurement when THD is calculated before aligning harmonics with the stimulus

Fig. 5. THD measurement when THD is calculated before aligning harmonics with the stimulus

 

If you’re wondering why this looks familiar, it’s because the graphs and distortion calculations exactly match the actual distortions shown in Fig 2.

As well as removing the influence of the linear frequency response on the calculated distortion, this method also minimizes the influence of room reflections. This enables you to measure the free field harmonic distortion in a regular untreated room with reflections – a particularly useful technique if you’re measuring somewhere like a car, which is full of reflections. 

Now we’ve covered the theory, let’s examine some real-world examples: a conventional speaker and a piezo-MEMS speaker.

Fig. 6 shows the measured harmonics for a dynamic speaker driver. The fundamental starts at 50 Hz and the 2nd and 3rd harmonics are plotted at their measured frequencies, starting at 100 Hz and 150 Hz respectively. The roll-offs are clearly similar at the low frequencies, as expected. At frequencies above around 8 kHz, the shape of the third harmonic is particularly similar to the fundamental, clearly demonstrating its linear filtering effect. Even the second harmonic shows some similar characteristics.

 

Fig. 6. Measured harmonics for a dynamic speaker driver.

 

Fig. 7. Conventional and Frequency Normalized THD

 

Fig. 7 shows the THD plotted both the conventional way (purple line) and the normalized way (green line). The conventional plot indicates around 10% distortion in the lower frequencies, and a bump around 200 Hz – which could potentially be a problem. The reality, however, is that it’s just the linear response boosting the low frequencies. The conventional plot also has a little bump around 1 kHz, but this is caused by the slight bump in the fundamental curve at higher frequencies. If we now look at the frequency normalized curve, it’s clear that we don’t have a low-frequency issue, although we do have a little bump at resonance around 300 Hz – and that is indeed a nonlinearity. This is much more valuable information if you need to know precisely where the distortion is coming from so that you can design around it.

The differences between conventional and frequency normalized distortion are even more significant with piezo-MEMS transducers. Piezo-MEMS transducers are an interesting new class of miniature transducers that use semiconductor fabrication processes to create actuators with piezoelectric materials that drive a membrane, rather than traditional mechanical components. They behave very linearly in the lower frequencies – you typically don’t see any increase in distortion at all – but often have a little high-frequency resonance. Due to these characteristics, a major vendor of these devices advises their customers that Frequency Normalized Distortion measurements are a critical part of accurately assessing distortion. 

Fig 8. shows the measured fundamental and harmonics of a piezo-MEMS speaker plotted at their measured frequency, and Fig. 9 shows the same harmonics plotted at the stimulus frequency.

 

Fig. 8. Harmonics plotted at measured frequency for a Piezo-MEMS speaker

Fig. 8. Harmonics plotted at measured frequency for a Piezo-MEMS speaker

 

Fig 9. Harmonics plotted at stimulus frequency for a Piezo-MEMS speaker

Fig 9. Harmonics plotted at stimulus frequency for a Piezo-MEMS speaker

In Fig. 8, the shape of the third harmonic again clearly mirrors the fundamental, and the second harmonic has something going on – maybe a resonance – close to 10 kHz. In Fig. 9 where the harmonics are plotted at the stimulus frequency, the low-frequency distortion, as before, appears a lot more significant than in Fig. 8 where it is plotted at the measured frequency.

 

Fig. 10. Conventional and Frequency Normalized THD for a piezo-MEMS speaker

Fig. 10. Conventional and Frequency Normalized THD for a piezo-MEMS speaker

 

This is clear in Fig. 10, where we compare the conventional and Frequency Normalized THD. Plotted the conventional way, the distortion is calculated at around 20% at 100 Hz, which is quite high. However, when calculated the frequency normalized way, it’s down at 6-7% . It’s also quite flat throughout the 100 to 10 kHz range, which is typical of these drivers. They’re simpler – there are fewer components to cause distortion, and they’re not acting in a nonlinear magnetic field. As with the traditional driver, relying only on conventional THD measurements could lead to a lot of wasted time trying to design around problems that don’t exist.

Whenever I explain this distortion measurement method, most engineers immediately recognize its benefits, and wonder how the conventional method became the norm. I suspect the reason traces back to early measurement practices: in the 1980s, Bruel & Kjaer pioneered the tracking-filter method, and plotting harmonics at their actual measured frequencies simply wasn’t possible with the chart recorders that were in widespread use. That constraint shaped the convention we still use today, even though the technological limitations that created it no longer exist. Perhaps the demands of modern transducer technologies may finally drive the industry to adopt it.

Summary

Conventional and Frequency Normalized distortion measurement methods are compared in Fig. 11. Conventional THD isn’t wrong. If you listen to sine waves it is what you hear. However, we don’t generally listen to sine waves, and Frequency Normalized Distortion correlates better with listener perception of broadband signals such as speech and music. 

More significantly, to correctly identify distortion mechanisms, and design products that address these, it’s essential to separate the linear response from the nonlinear distortion, and this requires Frequency Normalized Distortion.

 

Fig. 11. Comparison of conventional and Frequency Normalized distortion

Fig. 11. Comparison of conventional and Frequency Normalized distortion

 

Further reading:  How to Graph Distortion Measurements, Steve Temme. Presented at the 94th AES Convention, Berlin, March 16-19, 1993.

Missed our seminar?

Check out the recording below to learn more on Frequency Normalized Distortion: Why THD Isn’t Enough:

https://www.listeninc.com/wp/media/2025/12/Fig-2_LR.png 437 630 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-12-12 15:16:362026-08-12 12:51:59The Value of Normalized Distortion

Measuring Time Delay in a Mic Array

December 9, 2025/in Blog, SoundCheck Tips Videos/by Julius Wijono

Measure time delay in microphone arrays with SoundCheck! In this video, we’ll show you how to calculate both absolute and relative record delays across multiple microphones for more accurate, time-aligned measurements.

Additional Resources for SoundCheck

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

Video Transcript: Measuring Time Delay in a Mic Array

When we make an audio measurement, there is always a time delay between the stimulus playback and the recording. We call this “record delay”. In a mic array, each microphone has its own record delay and sometimes you need to know the absolute delay between each mic and the stimulus, or the relative delay between each mic using one of them as a reference.

Here is a simple sequence to calculate the absolute delay. 

I play a sweep through my speaker. There’s a play and record acquisition step which records simultaneously on three calibrated microphones in my array, mic one, mic two, and mic three, so I get three recorded time waveforms from this step.

Let’s run the sequence up to this break-point here…

Now you can see we have our three three recorded time waveforms in the memory list. I’ve grouped these and labelled them RTWs. 

Next we use an analysis step to calculate the delay or the record delay between these microphones. Any of these analysis algorithms can be used as they all output the delay value for the waveforms.

To find the absolute delay for these microphones, we’ll use the stimulus itself as the stimulus waveform and the group of three RTWs as the response. When I click apply, I get record delay values for the three microphones. 

Now I’ll remove this break point and run the entire sequence one more time. We hear the stimulus; it’s recorded simultaneously on the three microphones, and the display shows the fundamental response for each microphone along with the record delay values. These record delay values can be represented as time in seconds, or in inches or samples. 

Now let’s calculate relative delay. We’ll use mic 1 as the reference mic, and calculate the relative delay of mic 2 and mic 3 compared to mic 1. 

To do this, let’s use the recorded time waveform for mic 1, since it’s my reference, as the stimulus in the analysis step. And we’ll use other recorded time waveforms as the response. Let’s run the sequence. 

Now you see that I get the record delay values compared to the first mic. Mic 1 is showing a delay of zero as that’s the new reference point.  Mic two has a time delay of 90.7 microseconds, compared to mic one, and mic three has a record delay of 68 microseconds.

This concept of using a non-stimulus waveform as the reference in the analysis step is a valuable technique with many other applications in audio test, for example, dual channel impedance measurements.

https://www.listeninc.com/wp/media/2025/12/Measuring-Time-Delay-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-12-09 12:18:182026-08-27 13:51:15Measuring Time Delay in a Mic Array

Importing Correction Curves for Calibration

November 25, 2025/in Blog, SoundCheck Tips Videos, Uncategorized/by Julius Wijono

Easily calibrate your measurement chain by importing correction curves directly into SoundCheck. In this video, we’ll show you how to load external data, apply it to a signal path, invert response curves when needed, and ensure your corrections are properly applied during analysis for accurate test results.

Additional Resources for SoundCheck

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

Video Transcript: Importing Correction Curves for Calibration

It’s simple to calibrate signal paths in SoundCheck using either imported data or measurements you’ve made. This is useful, for example, if you need a frequency and phase correction curve for an input transducer, or a DRP to ERP correction.

To apply a calibration curve, the calibration data first needs to be in the memory list. If your data is in an external file, for example if you have a microphone frequency response curve from a calibration lab, you just select “open data” from the data menu of the memory list… and you can see now it shows up in the list. SoundCheck supports a wide range of formats from our own .dat format to txt and csv files.

Alternatively, you can use a recall step to bring your measured data into the memory list.

Now we have our correction curve loaded into the Memory List, we can use this curve to overwrite the calibrated device. Let’s open up the calibration window, and we’ll select the ‘copy from memory list’ button and choose our source curve. You can either apply the curve as it is, or invert it using this “invert curve” checkbox. You would use this, for example, if you want to remove the frequency response curve of the microphone from your measurement.

So, let’s check that box, and we’ll hit “apply” to save it, and OK.

Now we’ve added the appropriate correction curve to the signal path, the final step is to apply this new correction to our input response by enabling the checkbox “Apply Correction In” in the analysis step. It’s important to make sure this is selected otherwise, the correction will not be applied.

https://www.listeninc.com/wp/media/2025/11/Correction-Curves-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-11-25 05:00:562026-08-27 14:03:06Importing Correction Curves for Calibration

Calculating Intersection Times with SoundCheck

November 11, 2025/in Blog, SoundCheck Tips Videos/by Julius Wijono

Find the start and stop times of any recorded signal with SoundCheck’s intersection post-processing step. In this video, we’ll show you how to define a threshold, locate where your waveform crosses it, and calculate timing for applications like wake-word latency or response detection.

Additional Resources for SoundCheck

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

Video Transcript: Calculating Intersection Times with SoundCheck

In this video, I’ll show you how to find the start time of a recording. 

Here I have a sequence which recalls a wave file. I’m using the ITU real speech wave file which is provided with SoundCheck as an example. 

I’ll apply the recall step, and now we have the waveform in the memory list. 

Let’s say I want to find the start time of this waveform, which is around 0.5 seconds. 

We can do this with an intersection post-processing step, but first I need to define a signal level or a threshold. 

We need to select a value that is above the noise floor but within the signal of the recording you’re using. Most of the signal in this waveform lies above 30 m FS, so I’ll use 30 mFS. This means SoundCheck will find the point where the waveform crosses the 30 mFs value. 

Once this value is defined, I use an intersection post-processing step. I select the wave file or the recording as my operand A and the signal level that I have defined as operand B. 

We’ll use the “search up”  option, which starts at the beginning of operand A, which is the recording, and finds the point where it intersects with the signal level. 

“Search down” would do it the other way, and “return all intersection points” will identify all points at which the waveform corresponds to the signal level. 

Now let’s run the sequence, and we get the start time as a value, which is 492 milliseconds, approximately 0.5 seconds as we saw in the waveform graph. 

This is a simple example of how to calculate the start time.  This could be used, for example, for measuring the latency of a response to a wake word. If you wanted to find the stop time, you could use the “search down” function in the intersection step, and you could even calculate waveform duration by subtracting the start time from the stop time.

https://www.listeninc.com/wp/media/2025/11/Intersection-Times-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-11-11 05:00:252026-08-27 14:04:49Calculating Intersection Times with SoundCheck

ANC Headphones Audio Measurement

November 4, 2025/in Audio Measurement Videos, Blog, Headphone & Headset Videos/by Julius Wijono

How do you measure ANC headphones? In this video, we show how to measure active noise cancellation (ANC) performance using SoundCheck. You’ll learn how to test unoccluded, passive, and active responses with a head and torso simulator (HATS), an AmpConnect 621 audio interface, a SoundConnect 2 power supply, and pink noise source to calculate total noise attenuation. This simple setup can also be expanded for real-time ANC analysis or used to measure THD and distortion caused by ANC circuits.

Watch this Video Demo of Measuring ANC Headphones

Learn More about ANC Sequences

    • Noise-Cancelling Headphones Test Sequence: https://www.listeninc.com/products/test-sequences/free/noise-cancelling-headphones-test-sequence/

Video Transcript: How to Measure ANC Headphones

Today I’m going to show you how to measure active noise cancellation performance, or ANC, of headphones.

The set-up is simple. I’m using SoundCheck to generate the test signals and analyze the results. I have a head and torso simulator to capture the ear’s response. I’m using an AmpConnect 621 audio interface which also provides amplification for the speaker… and I have a SoundConnect 2 microphone power supply to power the mics in the head and torso simulator. If I was using a newer HATS with IEPE mics, I wouldn’t need this – I could power it directly from the AmpConnect. I’ve got a basic speaker here to generate the pink noise that we’ll use to measure the noise cancellation, and I have a nice pair of noise-canceling headphones.

We’ll play pink noise from this speaker. First we’ll measure the unoccluded ear response, then the passive response. That’s with the headphones on the ear but not turned on. Then we’ll turn on the ANC and measure the total attenuation – the full effect of the active and passive isolation.

Let’s run our test sequence. First we’ll take the unoccluded measurement without headphones. You’ll hear the pink noise playing, and we’ll see our measurement on the graph.

There we go…

Now the sequence pauses while we put the headphones on.

Next we’ll play the pink noise. I’m going to adjust the headphones to establish a good seal. Typically you would make this measurement 5 times and average it to account for variation in fit, but I’m just going to do it once in this demo.

Now let’s continue.  [pink noise plays]

So now we have the occluded measurement – that’s telling us how much sound the headphones are passively attenuating just from their materials and geometry.

Now we’re going to turn on the ANC and let the sequence continue….

Here we have the measurement with ANC turned on.

And you can see on the top graph here, we show the sound pressure level for the unoccluded measurement, the occluded measurement, and the measurement with ANC turned on. And this bottom graph here uses a simple calculation to show the passive, active, and total noise attenuation of the headphone.

That’s the test in its simplest form. You can get more fancy with your speaker setup. For example, instead of using just one source speaker, you could use multiple equalized source speakers to create a more realistic spatial background noise environment. You could also measure both ears at the same time. If you do this, you can use SoundChecks multichannel RTA to check for fit – you just measure the two channels simultaneously and make sure the left and right are showing similar responses. This saves time as you don’t need to make multiple measurements.

You could also use the multichannel RTA to look at how noise attenuation changes in real time. You’d need an external reference measurement microphone positioned here, outside the headphone, and you could play complex signals, like real recorded background noise from an airplane and watch in real time how the noise attenuation changes. This gives a more realistic representation of how the ANC circuit responds to dynamic signals.  

This set up is good for much more than just measuring active noise cancellations. We’ve done a lot of research on audio distortion caused by active noise cancellation. With the same setup, but different test sequences, you can measure THD, intermodulation distortion, time-variant distortion and more. Check out the technical papers on our website to learn more.

https://www.listeninc.com/wp/media/2025/11/ANC-Headphones-TN-scaled.png 1440 2560 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-11-04 05:00:072026-08-27 15:09:51ANC Headphones Audio Measurement

Detecting Air Leaks with SoundCheck

October 28, 2025/in Blog, SoundCheck Tips Videos/by Julius Wijono

Detect loudspeaker air leaks automatically with SoundCheck’s advanced analysis tools! In this video, we’ll show you how to use THD, Rub & Buzz, ePRB, eLP, and Crest Factor measurements to identify air leaks and port noise – no human listening required.

Additional Resources for SoundCheck

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

Video Transcript: Detecting Air Leaks with SoundCheck

Traditionally, loudspeaker enclosure air leaks are detected by human listeners during the final test process. SoundCheck’s algorithms can detect air leaks and characterize port noise automatically. Let’s take a look.

I’ve made recordings of a closed box speaker system with and without an audible air leak using a 60 Hz sinewave.  Let’s listen to them. First without the leak <play wav file> and then with the leak <play wav file>.  Looking at these two recordings in real time on a spectrum analyzer, we can see the spectrum of the speaker with the air leak has significantly higher harmonic content than the one without, particularly the odd order harmonics.

Now, let’s take a look at the SoundCheck algorithms that can detect the air leak. For these demos, I’ll recall previously saved waveforms for analysis. 

First, we’ll establish a baseline using a speaker without a leak.  We’re going to look at  THD, Rub & Buzz, enhanced Perceptual Rub & Buzz or ePRB, Enhanced Loose Particle detection or eLP and Crest Factor.

This display shows us these results, displayed on different graphs. As you would expect for a good speaker, THD, Rub & Buzz and Crest Factor are low, ePRB is below audible levels and there are no eLP events detected.

Now let’s analyze a recording where I’ve introduced an air leak by loosening the screws that secure the front baffle to the rear enclosure. THD and Rub & Buzz are significantly higher, ePRB is well above the audibility threshold of 12 phons and hundreds of eLP events have been detected.

These measurements were made with a microphone pointing at the side of the enclosure, the actual location of the airleak.  If we next analyze the results of the same sweep captured by an on-axis microphone, we’ll see that there is a much smaller delta between the leak and no leak data. 

Configuring pass/fail limits for any of these metrics is much easier using the side mic data so you can see that microphone location is critical for leak detection. If leaks are commonly coming from the front baffle, then a single, on-axis mic should detect them but if the leaks are coming from the back or sides of the enclosure, two or more microphones should be deployed. The good news is if you are doing this on a production line, although you need an extra microphone, the measurement can be made simultaneously with your other QC measurements.

It should be noted that this method may also pick up defects from other causes, but if you’re using it to reject faulty speakers, then that doesn’t really matter. 

These techniques can also be used in R&D for the characterization of port noise, allowing you to compare the results using ports of different shapes and sizes. 

Some of these methods may work better than others on your specific design so I’d recommend that you evaluate all of them with your own products, and focus on those that yield the most reliable results. 

https://www.listeninc.com/wp/media/2025/10/Air-Leak-Blog-TN-1.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-10-28 05:00:552026-08-27 13:47:51Detecting Air Leaks with SoundCheck

Using SoundCheck’s Multi-Instrument FFT/RTA/Oscilloscope

October 14, 2025/in Blog, SoundCheck Tips Videos/by Julius Wijono

Visualize your measurements in real time with SoundCheck’s Multi-Instrument feature! In this video, we’ll show you how to use the integrated FFT analyzer, RTA, and oscilloscope to view synchronized time and frequency data, perform live calculations, and save custom instrument setups for quick recall.

Additional Resources for SoundCheck

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

Video Transcript: Using SoundCheck’s Multi-Instrument FFT/RTA/Oscilloscope

SoundCheck features a multi-channel Real Time spectrum analyzer, FFT Spectrum analyzer and Oscilloscope integrated into a single “multi-instrument”. This lets you view any number of live waveforms simultaneously, and results can be time-synchronized across the three instruments to simultaneously display parameters in both the time and frequency domain. Let’s check it out.

All three instruments can be opened from the instrument menu or with keyboard shortcuts which opens them with their default settings. Let’s open the FFT Spectrum analyzer. 

On the left is the control panel and next to it is the graph where the live curves are displayed. Live curves are also shown in the Memory List and identified with a green dot. The multi instrument graph is identified by its white shading around the plot area but otherwise, it has the same functions as the standard graphs used in SoundCheck display steps.

The acquisition controls are at the top of the control panel. The Record and Stop buttons are used to start and stop measurements, and when the instrument is in linear mode, the Continue button resumes the previous linear measurement and continues until the Start button is next used. The Add button lets us add new instruments, calculations, graphs and triggers to the multi instrument.

Let’s first open up the FFT Spectrum Analyzer and look at some of the analysis options for stationary signals such as sinewaves.

I’m outputting a 1 kHz tone at 2 Vrms from the signal generator. On the Multi-instrument graph, we can clearly see the fundamental and the 2nd and 3rd harmonics. Let’s drop a cursor on the fundamental using the snap to max function, enable the harmonic cursor and by exposing the advanced graph controls, we can get a real time readout of the cursor frequency, level and the THD of the fundamental. 

Now, let’s add a calculation, in this case a real-time masking curve which will show us how our dominant fundamental tone is masking other stationary signals. The masking curve suggests that all of the harmonics are below the threshold of hearing but as we increase the signal level, they get closer to being audible.  

By adding a second signal generator, we can view intermodulation products. One generator is set to 340 Hz and the other to  7 kHz with a 4:1 amplitude ratio between the two signals. With these settings, we can clearly see the intermodulation products around the 7 kHz tone.

I can save any virtual instrument configuration for later recall from the instruments menu. Let’s just ‘close all’ to close all my windows. And now I can re-open it without having to reopen and configure all of the individual instruments again. 

Let’s switch over to a saved configuration with the RTA and signal generator and look at some of the other calculation options. The Multi-Instrument graph supports both live curves from the RTA and static curves from the memory list, and can use them both in a calculation. 

Here, I’m sending a Pink Noise stimulus to the device under test and I want to compare its RTA spectrum to a target response curve, which is already in the Memory List.  I can  just drag the target curve over from the Memory List to display it on the live graph. Now, I add a calculation for dB subtraction where the live RTA curve is Operand A and the Target Curve from the Memory List is Operand B. This generates a real time difference curve on my live graph and I can name it something more descriptive. 

Another useful RTA calculation is Power Averaging.  Let’s add a couple of RTA’s to the current configuration and assign each a unique microphone signal path.  Notice how, when I add RTAs, they inherit the properties of the original RTA so all I have to do is update the Signal Path assignment. Now I can add the Power Average calculation, select all three microphones and we have the Power Average of the three microphones. Live curves can always be saved to the Memory List by clicking the Save to Memory button. Once there, they can be displayed on other graphs or saved to disc. Other available calculations include Maximum, Minimum and dB addition.

Let’s take a look at the oscilloscope. I’ll open a saved virtual instrument that is configured with two oscilloscopes, monitoring two different input signal paths. The oscilloscope control panel lets us set the data name, signal path selection, time base and measurement mode.  The measuring indicator is bright green when the instrument is active and dark green when stopped.

Now let’s pause the signal generators and add a trigger.  Our trigger level is set relative to the signal’s peak level using either linear or logarithmic scaling. Slope selection lets the user decide whether the scope will trigger on the first positive or negative portion of the incoming signal and offset allows you to define the amount of time that the Acquired Signal is shifted, relative to the point at which it is triggered.

The trigger level is set to 300 millivolts on Direct Input 5 so let’s start the signal generators and increase the signal level, and once we exceed the trigger threshold we can see how the scope starts running and when the signal goes below the trigger threshold it stops.

I hope you’ve learned a few things about the multi-instrument from this quick tip. Try it out for yourself, and don’t forget to check the user manual for more details.

https://www.listeninc.com/wp/media/2025/10/Multi-Instruments-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-10-14 06:00:452026-08-27 14:08:37Using SoundCheck’s Multi-Instrument FFT/RTA/Oscilloscope

Trigger Options for Open Loop Testing

September 30, 2025/in Blog/by Julius Wijono

Improve open loop audio testing with SoundCheck’s trigger options. In this video, we’ll show you how to configure level, frequency, and cross-correlation triggers to ensure accurate playback and recording in asynchronous test setups.

Additional Resources for SoundCheck

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

Video Transcript: Trigger Options for Open Loop Testing

Open-loop testing is used when the device under test, such as a microspeaker in a phone or tablet, cannot be physically connected to the test system, so playback and recording are asynchronous. 

Typically, we load the stimulus signal onto the device under test, and play it back during the sequence run, capturing it with a record only acquisition step.

We need to incorporate a trigger into the acquisition step  so that SoundCheck knows when to start recording.

SoundCheck has three different trigger options – let’s take a look at how to use them.

Whichever trigger you use, first you need to create your test stimulus and save it as a wav file. In this case, we’ll take our stepped sine sweep from 20 kHz to 100 Hz and save it to a wav file. You could even add an autosave step to your sequence to perform this function.

Now let’s add a trigger. There are three trigger options available in the Record Only acquisition step – a level trigger, a level and frequency trigger and a level and cross-correlation trigger.

The level trigger step is our oldest and simplest method. SoundCheck just waits until the trigger level is exceeded on the selected input signal path, then records for the duration entered into the time field, which should be set to slightly longer than the stimulus duration. A small offset value can be applied to shift the recorded time waveform relative to the trigger time. In this case we add 100 ms to the start of the recorded time waveform prior to the trigger time. The timeout value is the amount of time that the step will wait for a trigger event before stopping.

Let’s run this.

Now that we have the Recorded Time Waveform in the Memory List, we can continue with analysis, post processing and other steps the same way as with a typical closed loop sequence.

If no trigger occurs before the Timeout value, the step produces a failed verdict in the sequence editor. We can configure the step to Halt on Fail, or to jump to an Operator Message prompting the operator to test again 

Simple level triggers are susceptible to false triggering – background noise, rather than the trigger tone might start the recording. Let me show you. I’ll run the sequence again while creating some noise, and you can see here, I triggered the recording with my clapping and we haven’t captured meaningful data.

Our second trigger option was designed to overcome such situations. The level and frequency trigger requires not only a level threshold to be exceeded but also a sine wave to be detected. This is more robust and less susceptible to errors due to background noise than the simple level trigger.

For this trigger, we create a compound stimulus. Here, our stimulus is a stepped sine sweep and we’ve configured the trigger tone as a 250ms 1 kHz sinewave. I’ve placed 100 ms of silence between the two components – that’s not a requirement. We set both the trigger tone and the silence to “Do not analyze” so we’re only analyzing the sweep portion of the recorded time waveform. 

Let’s run it. You can hear the trigger tone at the start, and you can see it on the recorded waveform here. And you can see, it’s analyzed just the sweep part of the stimulus to give us our results.

Although the level and frequency trigger is adequate for most purposes, it can occasionally register false triggers in noisy production applications where a neighboring line might be playing a similar trigger or sweeping through the trigger frequency. The cross-correlation trigger overcomes this by using a log sweep, or chirp, instead of a fixed tone trigger. You need the Time Selective Response module enabled on your SoundCheck license to use this option.  

(action: Help > Optional Modules and close then open STI editor)

In the cross correlation trigger, our fixed trigger tone is replaced by  a log sweep or “chirp”. The chirp should have a duration of 50 to 200 ms and have a frequency range of at least one octave, occurring within the passband of the device under test.

Now let’s select the Trigger type and the compound stimulus from the dropdown list in the acquisition step.

Let’s run it. You can see our log chirp here, and our stimulus, and of course our results.

That’s a quick demonstration of how to configure SoundCheck’s trigger options. You can find more detailed instructions in the user manual.

https://www.listeninc.com/wp/media/2025/09/Open-Loop-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-09-30 11:15:352026-08-27 13:50:30Trigger Options for Open Loop Testing

Why Headphone Target Curves and THD Don’t Tell the Whole Story

September 29, 2025/in Audio Measurement Musings, Blog/by Julius Wijono

Introduction

After weeks of measuring, presenting, and debating headphones at events including the AES International Conference on Headphone Technology and xMEMS Live Asia, one thing is clear: headphone specifications rarely tell the whole story. Despite endless measurements, a lack of standards means there’s little consistency in the way frequency response, sensitivity, and THD are measured between manufacturers, making results nearly impossible to compare.

 

Why Frequency Response Specs Mislead

Frequency response measurements are hard to compare as most include the unique response of the ear simulator, yet it is rarely specified what simulator was used. Similarly, test level, corresponding sound pressure level, and the number of times the headphones were repositioned on the ear simulator and averaged is rarely stated. A clearer picture would come from showing frequency responses from several measurements to demonstrate how strongly the responses shift due to ear seal leaks and high frequency directional characteristics when the headphone is repositioned.

There would also be value in sharing individual harmonic curves so it’s clear how much of the THD is even versus odd order harmonics. This information reveals a lot about the type of distortion, cause and audibility. Specifications should also state whether measurements were made with ANC on or off, and wired or via Bluetooth connection.

 

The Problem with Target Curves

There was a lot of talk about target response curves at the AES Headphone Conference – unsurprising since Dr. Sean Olive was a keynote speaker. The legendary Harman Target Curve gained widespread recognition as the first widely-shared target curve based on listener preference using many subjects. It is understandable why this is a preferential design target over a diffuse field correction curve, which it is often compared to. That said, the diffuse field correction curve was designed as a reference curve, not a design target, so it’s not really comparing like-for-like. 

Target curves also have other limitations. Since a target curve is simply an ideal targeted frequency response, as with headphone frequency responses, information is rarely provided on the specific ear simulator used to develop the curve, making it challenging to reliably compare your own device to the target. The original Harman target curve was measured on a modified GRAS 43AG ear simulator with a custom pinna. This makes any comparison imperfect, since any other coupler will introduce its own signature. 

Target curves differ for in-ear and over-the-ear headphones, and although they are based on large amounts of empirical data, they are by definition, an average, and not specifically attuned to any one particular person. Furthermore, a specific target curve is not universally aspirational. For example, the gaming industry places more emphasis on factors such as spatial cues, bass, or clarity for voice than the frequency response that is ideal for listening to music.

Target curves are also one-dimensional, ignoring factors such as phase matching, distortion, time variance due to signal processing (such as that found in ANC), and other factors that contribute to listener perception.

The onboard DSP now available for headphones means that the natural progression of a target curve based on many people is a customized target curve. There were several papers at the conference, such as those by Nielsen and Hamasaki that addressed the evolution of customized target curves based on auditory models. This allows frequency response to be customized based on the listener’s ears,  but how then is that presented in a headphone specification? How does an independent reviewer even describe the sound quality, when each person will configure it differently?

 

ANC Headphones: Quieter but not always better

Active noise cancellation is another area where specifications do not fully represent listener experience. Manufacturers boast about noise reduction levels but rarely disclose how it is measured and how ANC affects the sound quality. Conventional measurements such as THD usually demonstrate that ANC reduces distortion, yet most audiophiles claim the opposite. In my paper “Active Noise Cancellation Distortion in Headphones” at the AES conference, I demonstrated that although THD is indeed reduced when ANC is activated, this measurement alone is an incomplete picture. Time domain analysis reveals time and phase variance showing where perhaps the experience of poorer sound quality comes from. Surprisingly, the best correlation to listener perception was found with the POLQA algorithm – a communications quality algorithm that is certainly not designed for measuring headphone performance! Clearly more work is needed to arrive at a similar measurement method that truly captures the effects of active noise cancellation in a way that correlates well with human hearing.

Ironically, although R&D engineers struggle with producing headphone specs that correlate to listener experience, we’ve made significant headway with perceptual production line test methods that align well with human hearing to identify manufacturing defects such as perceptual rub & buzz and perceptual transient distortion detection. 

 

Why Conventional THD fails for headphone measurements

A couple of weeks later, I presented at xMEMS Asia live events in Taipei and Shenzhen, where I talked about small drivers being used in headphones and wearables such as smart glasses and smart watches. This time I was addressing a specific issue with the way many people measure loudspeaker THD. 

Conventionally, harmonic distortion is compared to the fundamental at the stimulus frequency. This is not totally accurate as linear distortion is superimposed on the non-linear distortion. This often goes un-noticed in conventional speakers where the highest distortion is usually at low frequencies near resonance, and the fundamental response is typically fairly flat since it is not measured with an ear simulator. The target response for headphones, however, is not flat and their fundamental response influences their harmonic responses. 

Conventional THD measurements are also a poor choice for piezo-MEMS speakers. These tend to be very linear at low frequencies, exhibiting distortion peaks at higher frequencies above 5kHz. For such devices, distortion that lies outside the audible range can be misrepresented as audible when referenced to the fundamental at the stimulus frequency, creating a misleading picture that doesn’t match perception.

Since 1993 I have been promoting the use of frequency normalized distortion measurements. With frequency normalized distortion, the harmonic distortion is plotted at its measured frequency and compared to the fundamental response at the same frequency before plotting difference at the stimulus frequency which separates non-linear distortion from linear distortion. When piezo-MEMS speakers are measured using this method, it becomes clear that the higher distortion is just a consequence of their linear response or rising sensitivity versus frequency which is equalized to be flatter as part of the product design. It also makes resonances far clearer, allowing their effects to be mitigated, for example, by damping.

With the explosion in the use of MEMS speakers for headphones, hearing aids and wearables, I suspect that normalized distortion will at last become more widely accepted as the best way to measure THD. After all, accurate measurements are the key to good product design.

 

Closing the Gap Between Specs and Perception

So where does this leave us with headphone and headphone component measurements? 

If we want to be able to tell what a headphone sounds like from its specifications, the industry needs well-documented standardized tests such as IEC 60268-7 and measurement methods that go far beyond frequency response and THD. As these devices become more feature-rich with onboard DSP, ANC, custom response profiles and more, the industry must develop and standardize new measurement methods that correlate with human perception. 

Until then, we’ll just have to rely on the subjective opinion of the many reviewers out there, together with the objective measurements that they have made. At least when review sites make objective measurements, they use consistent equipment, making results comparable, even if they don’t align with manufacturer specifications.

 

  1. Temme, S. 1993 March 16-19. How to Graph Distortion Measurements. 94th AES Conference, Berlin, Germany.
  2. Temme, S. 2025 Aug 27-19. Active Noise Cancellation Distortion in Headphones. AES International Conference on Headphone Technology. Espoo, Finland.
https://www.listeninc.com/wp/media/2025/09/Steve_pres_cropped.jpg 814 582 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-09-29 17:02:062025-11-21 11:36:22Why Headphone Target Curves and THD Don’t Tell the Whole Story

SoundCheck Sequence Editor Secrets

September 16, 2025/in Blog, SoundCheck Tips Videos/by Julius Wijono

Speed up your SoundCheck sequence development with hidden Sequence Editor features. In this video, we’ll show you secret tips for editing, debugging, and reusing steps to streamline sequence development.

Additional Resources for SoundCheck

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

Video Transcript: SoundCheck Sequence Editor Secrets

In this short video, I’m going to show you how to speed up your sequence development with some of the hidden features in SoundCheck’s powerful sequence editor. 

The sequence editor can be opened from the Setup menu or with the Ctrl + Q keyboard shortcut.

On the left side is our template library. You can drag the divider to re-size it, or click the divider to show or hide elements.

Step templates are grouped by category, and you can click on the expansion buttons to expand or contract them. You can right click on the category name to create new templates or import them from other versions of SoundCheck. Existing templates can also be edited, renamed or deleted. All sequences located in the folder of the active sequence are listed in the sequence template group.

The right side of the editor contains the active sequence.  The configuration menu at the top is where you set the default behavior for when the sequence opens, starts and runs, and set the path to any instruction files. There’s also a comment field where you can enter notes about the sequence.

The Sequence Parameters table is used to create Memory List placeholders which can be filled via external control using the MemoryList.set TCP/IP command. 

Lastly, the Metadata table is used to configure the sequence’s Metadata parameters.

Expanding a step shows you what data is coming in and out of the step. Steps are added to a sequence by dragging from the template library and dropping at the desired location. They can be configured as desired. A step or groups of steps can be moved within a sequence using drag and drop.

Now let’s take a look at the features in the right click menu.

Right clicking > Configure Step lets you configure step logic such as looping and jumping, as well as adding breakpoints and comment lines.

The configure Script option is only active for custom steps, where the script configuration window offers access to the LabView and Python options as well as the custom step editor

Commenting lets you enter descriptive text to help others understand what’s going on, step by step, and it’s a very useful feature, especially where your sequences are long or complex. In this sequence we’ve used comment steps to describe individual step functions and comment lines to explain where different river measurements take place for a 3-way loudspeaker.

Insert and Replace step are self explanatory. Insert is an alternative to drag and drop, and ‘replace’ replaces an existing step with a new step from the template library.

Copy and paste is a new feature we introduced in SC23. You can either use the right click menu or control+C control+V keyboard shortcuts.

Remove – as the same suggests, it removes or deletes the step 

Rename – lets you change the default name to something more descriptive

Undo – lets you undo the last several actions including inserting, removing and editing steps

Expand/Collapse all is a global command that expands and collapses all steps in the sequence. and is useful for determining where certain inputs and outputs are happening during the sequence run.

We also have some powerful tools for sequence debugging and editing.

Breakpoints are really useful when you’re working on long or complex sequences. You can define points in the sequence where it breaks from running, then use the toolbar buttons to either advance to the next step or the end of the section. This lets you isolate and run  small parts of the sequence without having to run the entire sequence. Here I’ll add 4 breakpoints. Now I can run the sequence just up to the first break by clicking start on the toolbar. And I can use this button to step through the sequence one line at a time, this button to run to the next breakpoint or hit the abort button to end the sequence.

Another useful debugging feature we recently introduced is Enable Disable step. This is much like commenting out a line of code in a program – when the sequence runs, the disabled step will be skipped over until it is enabled again. You might, for example, disable an autosave step to avoid collecting data, or operator message steps to save time, when developing a sequence.

Run from here allows you to start the sequence from any point, and when you use this in combination with breakpoints, it can make your sequence development a lot faster. 

Apply is the last menu item. This simply allows you to apply the step function without having to open the step editor to click the editor’s apply button.

The last feature I want to show you is back over in the Template Library in the Sequence group.  I  can highlight a step or any number of steps from another sequence and drag them right into my active sequence. This is a big time saver whenever you want to repurpose part of an existing sequence. You can even go one step further and drag the entire sequence into your existing sequence, instantly creating a subsequence.

That concludes our sequence editor tips and tricks. Hopefully you learned something new, and don’t forget to check out the user manual for more details.

https://www.listeninc.com/wp/media/2025/09/Sequence-Editor-Secrets-Blog-TN.png 1080 1080 Julius Wijono https://www.listeninc.com/wp/media/logo.png Julius Wijono2025-09-16 10:49:232026-08-27 14:10:59SoundCheck Sequence Editor Secrets
Page 3 of 26‹12345›»

Audio Measurement Expertise


How Changing Industry Needs are Shaping Audio Test and Measurement

Smarter SoundCheck Sequences with Loops and Logic

Audio Basics: Polarity

How to Measure: Haptics

The Value of Big Data

Audio Basics: Phase Response

view all

Latest News


2026 End Of Year Promotions

Celebrating 30 years: Listening – The Secret Of Our Success

Automotive Test Sequence Including BSR, Max SPL and Frequency Response

Listen Introduces AudioConnect 2, a New Portable Dual-Channel Audio Interface

SoundCheck 21 Brings Enhanced Loose Particle Detection, Multichannel FFT, Metadata, Sequence Protection and more


Audio Measurement Expertise – Delivered Monthly

 

ABOUT LISTEN INC

Listen is a global leader in audio measurement and analysis, with over 30 years’ experience developing innovative test methods and algorithms. SoundCheck, our powerful software-based audio analyzer, pairs with our test interfaces, precision microphones, and accessories to offer a complete solution for testing loudspeakers, headphones, microphones, smart devices, communication systems, hearing aids, automotive audio, and more. Trusted by engineers worldwide, Listen delivers the accuracy and flexibility essential for modern audio testing, from the R&D lab to the production line.

PRODUCTS
APPLICATIONS
SUPPORT
RESOURCES
NEWS & EVENTS
ABOUT

CONNECT

YouTube
LinkedIn
LinkedIn
Share
Instagram

Copyright © Listen, Inc.   |   Privacy Policy   |   AI Disclosure
  • Instagram
  • LinkedIn
  • Youtube
  • Mail
Scroll to top