100 Things #27: Recall Saved Data While Running A Sequence

SoundCheck can recall saved data such as EQ/Weighting  curves, limits, or prior measurements while running a test sequence, and use it within that test sequence. This feature is useful for measurement comparison to golden units, for comparison to repeated test measurements, and much more.

Recalling Saved Data in SoundCheck

Learn How to Recall Saved Data in SoundCheck

Check out our Recall Data Tutorial (section 9).

More information is also available in the  SoundCheck Manual.

 

Video Script: Recall Saved Data while Running a Sequence

Like every other program, SoundCheck allows you to open up previously saved data and run some sort of offline analysis with it. But, have you ever wondered if it is possible to bring in previously saved data into SoundCheck on the fly while running a sequence?

SoundCheck’s sequence editor comes with a ‘Recall’ step that allows you to import any kind of data – Curves, Values, Results, Waveforms, WAV file or even Text files into the memory list while running a sequence and use the imported data in any subsequent steps in the sequence. This is useful for test engineers in a lot of different ways.

Firstly, if you have previously saved data  like EQ/Weighting  curves, limit values of waveforms that you would like to use, you can bring these into a sequence automatically using the ‘Recall step’. The recalled data  will get populated in the memory list when the sequence is run and can be used in any subsequent steps in the sequence. The recall step can be configured to use an absolute path to the recall data, use a relative path using  automatic template naming option or prompt the operator to select the data for recall.

When exporting a sequence that uses a recall step with an absolute path, Soundcheck will automatically copy the recall data to the export folder and convert the recall path from absolute to relative

The recall step can also be useful to reference a previously saved measurement when you are making repeated test runs. Just to give you an example, if you are measuring passive noise cancellation with different headsets, you could measure the unoccluded ear response only once and in the next run, choose to recall the same unoccluded response curve to analyze with a different headset response. On a production line you might want to compare the speaker under test to a recalled reference or “golden unit” for limit comparison

Personally, I find this to be a very useful tool in troubleshooting sequences. When I do not have the hardware connected to take actual measurements, I use the recall step to simulate acquisition and bring in previously-recorded waveforms so that I can debug subsequent analysis or post processing steps in the sequence.

Overall, the ‘Recall’ Step serves as a multi-purpose utility to bring in previously saved data specific to a sequence, facilitate easy sharing of sequences,  save time when dealing with sequences that take repeated measurements and also help with troubleshooting sequences.