Latency for PurePath Components?

Bernie Thompson said:

Is the sample latency of the various components within PurePath (such as Bi-quad, DRC, etc.) documented somewhere?

Bernie,

      The TAS3x uses a sample based approach, so there will be an inherent 1 sample delay in the system. Must PurePath Studio components will follow this latency -however- there are some algorithms that have an inherent latency build into them such as the DRC, Biquad.

   An example of the biquad algorithm can be found here.

http://en.wikipedia.org/wiki/Digital_biquad_filter

     As you can see, the filter uses feedback from two  previous samples to generate the filter result.

     DRC is a different type of algorithm in that it needs to analyze the value across multiple samples to determine how to behave. It also needs time for the behavior to take place. The DRC has multiple time windows which can be set by the user for more control.

http://en.wikipedia.org/wiki/Dynamic_range_compression

Bernie Thompson said:

Perhaps there is a procedure or tool for measuring the latency?

     If exact timing is needed, the assembly is open source, so one could analyze this. You can also use COTS tools such an those provided by Audio Precision Inc, to do audio latency testing.