In this short video, our friends at Indy Acoustic Research demonstrate how they use SoundCheck to automate wake word detection and output the results to a report. Note how looping within the test sequence enables an entire batch of measurements to be made in one go, and the data is output to a nicely formatted report.
Indy Acoustic Research offers a range of acoustic consultancy services and has many years of expert-level SoundCheck experience across a broad range of applications.
https://www.listeninc.com/wp/media/2025/05/wake_word_detection_video.png9821636Zarinahttps://www.listeninc.com/wp/media/logo.pngZarina2025-05-07 16:40:192025-05-07 16:41:07Automatic Wake Word Detection
Need to run custom equations in your test sequences? In this video, we show you how to implement complex formulas directly into your sequences using SoundCheck’s Equation Editor.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: Using the Equation Editor in SoundCheck
In this video I’ll show you how to use the equation editor in SoundCheck. This optional module lets you add any custom equation as a post-processing step so you can use it within a sequence. For example, you might want to apply a complex formula from a technical paper or a specific standard to your data.
Let’s look at how it works. I have a simple example here on my right side. I have three input variables: A = 1, B = 2 and C = 3, and I have three equations to solve for X, Y and Z. And here I’ve calculated the values of X, Y and Z.
If you were to calculate this in a sequence without using the user equation editor, it would take almost 10 steps just to solve for X, Y and Z.
Let’s now implement this using the user equation editor.
I’ll create a new sequence, and insert three operator numeric steps, A, B and C.
I’ll initialize the values of A as 1, B = 2 and C = 3. Next I’ll add a user equation post-processing step. This opens up in two separate windows, one where we define the input and output values, and the second where we write the equation. You can always access context help while you’re doing this by hovering over a particular field.
I’ll start with the operand on my left side here. I’m using A, B and C as my input operands. These will be referred to as A0, A1, and A2 when I’m writing the equation. Next I’m going to write the actual equation in this post-processing window here
X equal to A0 to the power of 2, plus 2 A0 A1 followed by a semicolon.
You can see this automatically creates the output value of X.
Now let’s write the second equation
Y equals X log X plus A2, followed by semicolon
Now for the third equation…
Z equals the square root of XY, again followed by a semicolon.
If you need any help writing equations, appendix 9 in the manual shows all the available functions and how to use them inside the equation editor.
Since our input values are contained in the y-axis we don’t really need to show the x-axis in the outputs, and we know the units are linear so I’ll change that in my output and that’s it.
Now let’s run the sequence. I have a= 1 b= 2 c = 3 and I get the values for x y and z, and we can display these on a table.
So, as you can see, it’s easy to implement complex mathematical functions and formulae into your SoundCheck test sequences. This lets you do all the calculations you want on your data automatically, without leaving SoundCheck.
https://www.listeninc.com/wp/media/2025/04/User-Equations-Editor-Blog-TN-1.png10801080Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-04-29 11:11:292026-08-27 14:21:41Using the Equation Editor in SoundCheck
Shorter test sweeps make your tests faster, but longer averaging time improves noise rejection leading to more accurate and repeatable measurements. When optimizing audio tests, how do you adjust your test signal to get fast results without sacrificing accuracy? There are 5 parameters you can tweak.
Frequency range: Only sweep over the frequency range that you actually need to. It’s not always essential to sweep from 20Hz to 20kHz. In many cases, 100Hz to 10kHz is sufficient because the device under test has significantly rolled off above and below these frequencies. This can offer considerable time savings especially at low frequencies where the wavelengths and averaging times are long and background noise is high.
Resolution: Decreasing the resolution, for example from R40 (1/12th Oct.) to R10 (1/3rd Oct.), will make the sweep time shorter. Bear in mind that the trade off is that you will have fewer data points so might miss some audio artefacts that would be detected at higher resolution. Often you can use lower resolution at lower frequencies where the measurement curve is smooth, and higher resolution at higher frequencies where the measurement curve is more variable. This way you get the best of both worlds, faster at low frequencies and more resolution at high frequencies with little time trade off.
Number of Cycles: Likewise, decreasing the number of cycles at each step will shorten the stimulus length but reduce accuracy.
SNR: A better signal-to-noise ratio improves measurement accuracy so consider increasing your stimulus level. You can also increase signal to noise on an acquisition step by increasing the input gain on your audio interface. Use the Max FSD function in SoundCheck to ensure that you are operating at maximum dynamic range.
Background noise: reducing background noise increases your measurement confidence, Consider soundproofing your test station to improve your test accuracy and repeatability.
SoundCheck’s HarmonicTrak analysis algorithm includes confidence limits, standard error, and noise tools to help you balance speed versus accuracy. These features evaluate the effect of any changes in stimulus on both test time and the measurement confidence so that you can optimize your test time while maintaining confidence that your accuracy is still within acceptable limits.
https://www.listeninc.com/wp/media/2025/04/Confidence-Limits-1.png10791920Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-04-28 14:10:422026-08-27 14:01:545 Tips for Optimizing Audio Tests for Speed and Accuracy
Take your pass/fail criteria to the next level with advanced limit settings in SoundCheck. In this video, we explore precision tools like floating X-axis limits, failed point curves, and detailed interpolation controls to help you fine-tune your measurement accuracy.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: Advanced Limit Settings in SoundCheck
Today we’re going to look at some advanced limit setting options available in SoundCheck.
Let’s open up the limits editor. This is where you set Pass / Fail limits for your measurements.
The Data tab is where you enter your upper and lower limits and the specific data that the limits are to be applied to. In the Parameters tab you can set your method for aligning limits, you can read about all these options in the manual so I’m not going to review that now. Instead, I’m going to focus on the advanced parameter options, there’s some really useful functionality in there.
We’ll just click on this ‘Advanced View’ checkbox here… and we get some additional useful controls.
The “Absolute Comparison Precision” field lets us set the number of decimal places for the limits, which affects the pass/fail margins. For example, say I have a curve with a limit of 80 deeBee set at 13.2kHz. If my data precision is set to 2, it sees my measurement to 2 decimal places and we can see it’s 80.18 deeBee which exceeds my 80 deeBee limit and it fails. If I now change that data precision to 0, that’s no decimal places, my 80.18 deeBee reading is now rounded down to 80 deeBee which is right on the limit so it passes. This gives you very tight control over your pass and fail limits.
The Mapping section controls linear versus log, as well as floating limits in X. This setting determines the interpolation of the data to the limit curves if it is linearly or log spaced.
In this example, I have a curve with an upper limit on. I expect the result to pass but it does not. Let us find out why…
We’ll use a neat feature called “Output Failed Point Curves”. When you enable this, it generates additional curves showing exactly the points that failed in comparison to the upper and lower limits. You can also view these failed points in a table to see precise numerical values, and we see that the failed point was at 125Hz.
Looking back in the limit step, we see that 125Hz has a value of 1.370%, and if we use simple linear math, the upper limit at 125Hz is 1.375%. So why didn’t the limit step pass? This is because we are making linear calculations of the upper limit, but the limit interpolates on a logarithmic scale as the x-axis displays the frequency domain, which is normally shown logarithmically. If we switch the mapping option to linear, the data is below the upper limit, and it passes. Let’s just zoom in and take a closer look…
Float limits in X allows limits to float back and forth along the X-axis for the best fit. This is useful if you’re applying limits to curves with sharp peaks and dips due to reflections for example. You also have control of the step size increments, and the maximum and minimum percentages that the limits can float.
For example, I have a curve with a peak and I’d like the shape of the limit curve to match the shape of this peak, but apply it at the frequency where my new peak is. I’ll switch to my new curve, and when I apply the floating limit, it shifts to best fit the new curve peak. Notice that only the X-axis has changed and the Y-axis remains the same.
I hope you found this demo of advanced limit setting features useful. Please check the SoundCheck manual for further details.
https://www.listeninc.com/wp/media/2025/04/Advanced-Limit-Settings-Blog-TN.png10801080Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-04-15 08:00:132026-08-27 14:09:54Advanced Limit Settings in SoundCheck
From its origins in 2002 as a new, smaller connector for HDTV, High-Definition Multimedia Interface (HDMI) evolved continuously over the years to become one of the most widely adopted interfaces. This article provides practical answers on how to perform HDMI audio measurements, dealing with the interface’s multiple options and configurations.
How do you measure HDMI audio? This is a question we often hear as HDMI soundbars become more commonplace and the rapid adoption of surround sound and spatial audio systems with televisions continues. While some manufacturers offer expensive custom interfaces to test HDMI devices, there is a much more cost-effective method. Some software-based audio measurement systems can be used with a $100 off-the-shelf interface that enables test signals to be sent via HDMI to a soundbar or surround sound system for measurement. In this article, we discuss how the HDMI protocol handles audio and demonstrate acoustic measurements on a soundbar using Listen SoundCheck software with a commercially available HDMI audio extractor. This method can be extended to a wide range of HDMI connected devices including multichannel surround sound systems.
HDMI Audio
Modern HDMI systems offer Audio Return Channel (ARC) functionality. This allows a single HDMI connection to be used as both an audio input and an output, providing a two-way flow of audio, in addition to video, between devices. This eliminates the need for a dedicated audio cable to connect a soundbar or AV receiver to the television, simplifying configuration and reducing cost and cabling. ARC supports up to six-channel compressed audio and has a maximum bandwidth of 1Mb/second. It supports various audio formats including PCM (2 channel), Dolby Digital (up to 5.1 channel), and DTS Digital Surround (up to 5.1 channel).
A newer version, Enhanced Audio Return Channel (eARC) improves upon ARC with a significant boost in bandwidth and speed, enabling transmission of higher quality audio from a TV to a soundbar or AV receiver. It carries up to 32-channel audio, including eight channels of 24-bit/192kHz uncompressed audio, and supports modern advanced audio formats such as DTS-HD Master Audio, DTS:X, Dolby TrueHD, and Dolby Atmos.
Many audio devices that are used with audiovisual systems, such as soundbars, speakers, gaming headsets, and so forth, are unable to accept an HDMI input with video directly. A small device called an HDMI extractor is commonly used to split the audio and visual HDMI signals so that the audio signal can be played directly on a soundbar or surround sound system. Audio extractors typically cost around $100 and can be purchased online or from electronics or AV stores.
These widely available devices also enable HDMI audio devices to be measured using a software-based audio analyzer. To measure audio, a test stimulus must be sent from the computer to the device under test (DUT). Although soundbars usually feature an HDMI port, as do most computers, typically the device’s audio channels will not be accessible if they are directly connected via an HDMI cable.
Unlock hidden secrets in your SoundCheck display! In this video, we’ll show you how to customize graph types, tweak axis settings, and save display templates to optimize your workflow.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: SoundCheck Display Secrets
There are many ways you can customize SoundCheck displays, and you can save your preferences as defaults. Let’s take a look.
Here, I have a new display tab called “Display One.” If I double-click on my curve in the memory list, it opens on my default XY graph. There are different ways you can open up graphs. If I right-click on the background, I can choose any graph type to add to this display. It opens up my default display, then I can drag data onto it as well.
If you want to configure your own displays rather than use ours, there are a couple of places you can change the defaults so that you don’t have to make edits multiple times.
In Edit > Preferences, we have a Display tab, and this lets us choose the default colors for our graphs. You can see this matches up with our graphs here—the background is white, the major X-axis grid is white and the minor gridlines are set to T for transparent. We have our cursor colors… and colors 1 through 8 are the colors of the items we add to the graph in order. So, the first curve is blue, the second is orange, etc.
Changing the defaults here changes the settings of every new XY or waveform graph. For example, if you like to see the minor gridlines, you can enable that here, and every new graph will inherit this setting. You can save these settings as a preset, which makes it easy to share across stations, or go back to the default if we don’t like our changes. Now if I add a new XY Graph, you can see that the minor grid lines are set.
You can also change the appearance on a specific graph.
I can edit the size of the display.
I can right-click to Auto Scale and change the Format or Precision of the X and Y axes.
For example, I might want more precision in my X-axis and want to switch the mapping between linear or log.
There are more configuration options in the right-click Preferences menu. Here I can
switch where the legend is—move it to the right or disable it.
change the position and color of the logo.
And change the background and cursors.
There are also settings for:
X and Y axes
Grid lines
Scale
Range
So I can change these on each individual graph. Creating a new graph will always revert to the default. However, if you want to create a new graph based on a configuration you’ve just perfected, there’s a ‘duplicate’ option in the the Memory List under the Display tab. This copies all of the settings of that display to a new one. This is useful if you want to display multiple curves across similar-looking displays.
I can even go one step further and save an entire display layout as a template. I just right-click on the Display Tab and choose Save as Display Template. Now, in my Sequence Editor, every time I drop in this new display template, it contains all these graphs and their configurations.
Another very useful option from this Display dropdown is Display> Save as Default. This will over-write your existing default settings with the configuration of the active graph. I find this really useful as it’s much easier to perfect a graph once you have real data on it rather than through the settings options.
Now, whenever I open an XY graph (for example, double-clicking on a memory list item), all of these settings are inherited by my new graph.
I can customize my configuration for each of the graph types so I have different defaults for xy graphs, tables, waveform graphs and polar plots. Then, whenever I open a graph, it’s going to use those settings and display it exactly how I want it, without needing to edit the displays.
For more details on customizing your displays, check out the information in our user manual.
How do you measure a microphone? In this short video, we demonstrate how to accurately measure a microphone’s frequency response using SoundCheck. You’ll see how to ensure an accurate microphone measurement by using two different techniques that separate the microphone’s response from the source speaker’s influence. We cover two key methods: the Equalized Speaker Method, which calibrates the speaker using a reference microphone for a flat response, and the Substitution Method, which compares the test microphone to a reference microphone to remove speaker effects.
Watch this Video Demo of Microphone Measurement Techniques
Learn More about How to Perform Microphone Measurements
The challenge with measuring the frequency response of microphones is that usually, the microphone’s frequency response is better than the source speaker used to play the test signal to measure it. This means you need to use measurement techniques that ensure you’re measuring the microphone and not the speaker. SoundCheck offers two great ways to do this.
The first is what we call the Equalized Speaker Method. First we measure the source speaker with a calibrated reference omnidirectional microphone that has a flat frequency response. We apply the reciprocal as a equalization curve for the speaker at a constant sound pressure level, then measure the microphone under test or DUT in the same position as the reference mic.
The second method is the substitution method. Here, we first measure the source speaker with a reference microphone, then the source speaker with the microphone under test in the same location. Then we subtract the microphone under test result from the reference microphone to show just the characteristics of our DUT. Unlike the Equalized Speaker Method, the substitution method is not performed at a constant SPL which can result in a poor signal to noise ratio where the source speaker response rolls off at low and high frequencies significantly.
Let’s take a look at these measurements
Pre-written sequences for both of these methods come with the SoundCheck installation, so we’re going to use those today.
I’ll start with the equalized speaker method. I’m using an SCM measurement microphone as my reference microphone, and I’m using the AmpConnect 621 audio interface because as well as microphone inputs, it has an integrated amplifier to power my source speaker – a single driver, wide-bandwidth, Cambridge Audio Minx. This makes it easier to repeatedly position the microphones by pointing them at the center of the speaker.
First we need to equalize the speaker. We’re going to use SoundCheck’s built-in calibration sequence to do this.
It plays our stepped sine signal, measures the frequency response… we have a few reflections here. We take the reciprocal of the response and equalize the output of the signal generator and measure again. You can hear its boosting the low frequencies instead of it being + or – 20 db its + or -1 db or less…. Because the speaker’s non-linearity it will be slightly different at different levels so we can equalize the equalization to further refine the EQ curve.
Here’s our speaker and we can see the EQ curve and the residual correction after EQ… and you can also see the phase here.
Now we’re all calibrated, let’s make a measurement. We use the same stepped sine sweep played through the speaker, capture the frequency response, calculate the sensitivity at 1kHz, and display our results on a graph.
We also have a couple of arbitrary limit steps here – you’d want to customize them based on your device. Here we go…
Here you see the frequency response and phase— as you can see, it is fairly flat. And down here, we have our frequency response aligned to zero dB at 1 kHz, which is the standard way of displaying microphone response, and we can see our measured sensitivity is about -5.5dBv/Pa.
Now, let’s look at our alternative method—the Microphone Substitution Method.
In this method, rather than using an equalized speaker we first play our stepped sine sweep and measure with a calibrated reference microphone. We then substitute our microphone under test and measure again. Next we subtract out the measurement of the reference microphone to get the raw response of our microphone under test. This removes the effect of the speaker’s response on the measurement.
We need to make sure we have the test microphone and the reference microphone in exactly the same position to minimize variance in the measurement.
If we look at our test sequence, we can see that we have two acquisition steps, one for the reference mic and one for the mic under test, and a curve division step using the division operation in linear mode.
Let’s run the sequence.
It reminds me to make sure my reference mic is calibrated, which it is, and it prompts me to put it in front of the mouth simulator… let’s do that. We’re using a source speaker instead, but you can use a mouth simulator if you prefer, they both fulfil the same function.
It’s acquired the data, and now it’s asking me to put the microphone under test in its place… I’ll try to get it as close to the same spot as possible.
Let’s continue. And it’s acquired the data, performed the division, and here is our response.
This lower graph here shows the responses of the two microphones – the blue line is the reference mic and the orange line is our mic under test. And this top graph here shows the normalized frequency response including phase after the division.
You can see the sensitivity at 1 kHz is -6 dB V/ Pa, which aligns well with our first measurement using the equalized speaker measurement.
So there you have it – two simple methods for measuring microphones that ensure any non-linearities in your speaker don’t affect the measurement. And of course these are some of the most basic microphone measurements that you can do in SoundCheck. We can also measure directional response, acoustic overload point, intermodulation distortion, signal-to-noise ratio, embedded mics, MEMS mics and more. If you have any questions, or would like to see more microphone measurements, please get in touch with us – we’d be happy to demonstrate!
Learn how to combine live curves and static curves in SoundCheck for real-time analysis and comparison! This video covers everything from visualizing live FFT data to performing mathematical operations on live curves and static curves, like subtraction and averaging.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: Live Curves and Static Curves in SoundCheck
In this video, I’m going to show you some options for plotting different types of curves in SoundCheck. Specifically, I’m going to show you how to combine static and live curves on the same graphs. This is useful for example, for tuning applications or comparing a live curve to a target curve.
Many of the curves we encounter, for example, the fundamental curve, are static.
However, SoundCheck’s multi-instrument spectrum analyzer and the RTA allow us to visualize live curves which change with time.
You can see here, for example, if I play a sine tone on my signal generator, I can capture it with my microphone and you can see the live FFT curve here. This green dot next to it here in the memory list indicates that it’s a live curve.
You can plot live and static curves separately, or together.
For example, if I want to add the static curve to this graph here with the live curve, all I need to do is drag and drop the fundamental curve from the memory list onto the graph.
Similarly, I can also drag and drop live curves on an existing or a new display.
You can also do calculations involving both static and live curves, including subtraction, addition, and power average, and you can also find maximums and minimums. Here, I’m going to add a new calculation module that subtracts two curves to find the difference between a live measurement and a target curve.
On the RTA, I’ll add a subtraction function, then I’ll select my live curve… and my static curve. Now you can see my graph is showing the original RTA and the memory list static curve. And we also display a new calculated curve which is the difference of the RTA and the static curve.
There are other mathematical operations that can be implemented on static and live curves, for example addition and power average, and these can even be used in test sequences. Check out the SoundCheck manual for more information.
https://www.listeninc.com/wp/media/2025/03/Live-and-Static-Curves-Blog-TN.png10801080Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-03-18 05:00:152026-08-27 14:24:20Live Curves and Static Curves in SoundCheck
Easily measure vibration with accelerometers in SoundCheck! In this quick tip video, we’ll show you how to set up and calibrate an accelerometer for precise vibration measurements.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: Using Accelerometers with SoundCheck
In this short quick tip video I’ll demonstrate how to use an accelerometer with SoundCheck. This is useful when measuring vibration, not just an acoustic input.
First you need to set your input signal path to accelerometer in the calibration menu and calibrate your input. Accelerometer calibration sequences are built into SoundCheck so it’s simple – just click the calibrate button and it will automatically calibrate your input. I have a B&K 4294 calibrator with a 4534-B-001 accelerometer, which I can select here and then calibrate.
Now let’s take a look at our accelerometer readings. I still have my accelerometer on the calibrator, so it should show me 10 meters per second squared.
You can also integrate the input to view velocity rather than acceleration. We just need to check this ‘integrate’ box here, and now it calculates the velocity in meters per second. This is useful if you want to correlate measurements to velocity rather than acceleration, for example, if you are measuring fan noise at different speeds or as a device ramps up.This calibrator outputs 10 milimeters per second, so if I enable this checkbox that’s what we’ll see.
You can even plot these measurements on a strip chart to see how the velocity is changing over time.
https://www.listeninc.com/wp/media/2025/03/Accelerometers-Blog-TN.png10801080Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-03-04 05:00:522026-08-27 14:08:00Using Accelerometers with SoundCheck
Easily analyze test data without re-running sequences! In this video, we’ll show you how to replace acquisition steps with recall steps in SoundCheck, allowing you to troubleshoot remotely and refine test parameters using saved waveforms.
Additional Resources for SoundCheck
Detailed explanations of how to use SoundCheck can be found in the SoundCheck manual.
Video Transcript: Recalling Saved Data in SoundCheck
It’s often useful to bring test data back into SoundCheck for additional analysis. This is useful for troubleshooting problems remotely, for example helping a contract manufacturer figure out some questionable results or if you want to re-analyze your own data without re-running the sequence.
While you can always bring this data into the memory list manually, replacing an acquisition step in a sequence with a recall step automates this process to save time.
Let’s look at an example.
Here, I have the factory test sequence that my CM is using.
In the past, they have sent me data that I needed to open up manually in SoundCheck, but now I have the actual test sequence. It’s also important to get the waveforms, saved as WFM or TDMS files, included with the sequence – these are the formats that contain the metadata that SoundCheck needs.
I’m going to make a copy of this sequence, and append ‘recalled data’ to the sequence name. Next, I’m going to replace the stimulus and acquisition steps in the sequence . These are the steps that define the test signal, play it on the device under test, and record the response.
I’ll replace these steps with a recall step… I’ll drag it in here. It’s important when adding this step to the sequence you place it right after the acquisition step but before any other step in the sequence uses these waveforms. …. You need to select the appropriate TDMS or waveform format depending on the file format of your date. In this case I’ll use TDMS.
Now here we have two options. We can have the sequence prompt the user to pick a file. If you choose this option, it’ll prompt the user to select the file each time the sequence is run. This is useful if you have multiple files or data sets you want to select from.
Alternatively, we can specify a file path. This is what I’m going to use in this case, and I’ll specify a path to the factory test data that they sent me.
It’s important that the names of the waveforms match the exact names used in the sequence, as we’re replacing them with the recalled data.
I also recommend saving the stimulus, just in case there’s any sample rate differences between stations.
If all the necessary data is contained in one file, you can use a single recall step. Alternatively, you can create multiple recall steps for the stimulus and as many response waveforms as you have in your sequence.
My recommendation is to use one TDMSfile that contains all the waveforms, so a single recall step, whether specified or prompted, replaces the acquisition and stimulus steps.
Once our recall step is in place, click OK
Since these are the exact same names as the output, we need to configure this step to overwrite data.
It already is, so all I need to do is remove these stimulus and acquisition steps.
Now, I don’t need to actually have any hardware on my station. When I press start, the sequence will run, recalling the data. All the remaining steps, the analysis, post-processing, and displays will execute as if the data were acquired in real-time.
And we can see, when I press start, it outputs all my data here.
Now we can troubleshoot in many different ways. For example, we can go in and change some sequence parameters, say if we want to look at the resonance over a different range, and re-run the sequence.
Or maybe I want to add some additional distortion analyses and examine more harmonics to find the cause of some audible artifact. I can just add these in, and now when I run this I’m able to capture all of this data and analyze it from those same exact waveforms.
https://www.listeninc.com/wp/media/2025/02/Recalling-Saved-Data-Blog-TN.png10801080Julius Wijonohttps://www.listeninc.com/wp/media/logo.pngJulius Wijono2025-02-18 11:57:232026-08-27 14:20:42Recall Saved Data in SoundCheck