Version 1.02 has a very subtle minor modification that is a great time-saver. I have changed the definition of Calculate Frequency Response (the Calculate menu for datasets, the Frequency Response option).

With 1.02 the reference dataset is now treated just like with acoustic tests. If you use a gate in this dialog the start gate time for the reference is set to zero (just like acoustic testing where the dataset is delayed but the reference is not). What this lets you do is take a single time (pulse) response from a loudspeaker and then play with it later to try all sorts of different gate values without having to actually run a pulse through the loudspeaker repeatedly.

The technique for setting up datasets for this is a little awkward (and will probably get easier) but for now...

[1] Open a driver

[2] Perform a "Pulse Response" test

[3] Save the pulse response for later use by renaming it (so later pulses don't overwrite it)

[4] Save a copy of the reference response for later use. To do this, go to the system directory and select measurement.in.l then perform a copy in the tree and then a paste in the tree (usually in the root of the tree). Rename the copied dataset so that you can use it as a reference dataset.

Here's the tree before and after the modifications

Showing the pulse response dataset and the system directory	Showing the pulse response renamed, and measurement.in.l copied up to the root and renamed.

The two responses (references and pulse) are renamed so that you can save the file and then reuse the responses as much as you wish even if more tests are done.

If you perform the above calculate frequency response on Dual.Pulse Response the result will be exactly the same as doing an on-axis test.

Speaker Workshop is currently