playgrid.ccBrowse tools

Digital audio timing / Free producer tool

Audio latency calculator

Estimate theoretical audio-path latency from buffer size, sample rate, input and output stages, processing samples and known fixed delays.

Live calculator

Set the buffer and sample rate

Each buffer stage uses the same block size. Add only stages and fixed delays that belong to the path you want to estimate.

Sample rate: whole-number Hz from 8,000 to 384,000.

Buffer: whole samples from 1 to 65,536.

Common sample rates

Common buffer sizes

Theoretical path total at 48000 Hz.

Path assumptions

Count each stage explicitly

0–16 buffer stages each

Theoretical total

5.333333 ms

256 samples equivalent · 2.666667 ms per buffer

Path stageAssumptionDuration
Input buffering1 × 128 samples2.666667 ms
Output buffering1 × 128 samples2.666667 ms
Extra/safety buffering0 × 128 samples0 ms
Plug-in or processing delay0 samples0 ms
Known fixed delayUser-entered device/driver time0 ms
Total256 sample-based + 0 ms fixed5.333333 ms

This is a theoretical sum, not a measured latency result. Drivers, converters, USB or Thunderbolt transport, hidden safety buffers, operating-system scheduling and device DSP can add delay. Use reported input/output latency or a loopback test when accuracy matters.

How theoretical audio latency is calculated

One buffer stage lasts:

buffer duration in milliseconds = buffer samples ÷ sample rate × 1,000

The calculator keeps the path components separate, then adds them:

theoretical total = input buffers + output buffers + extra buffers + processing delay + known fixed delay

Input, output and extra stages are whole counts of the selected buffer size. Plug-in or processing delay is entered in samples and converted at the selected rate. Known converter, driver or device delay is entered directly in milliseconds. The total sample equivalent converts the entire sum—including fixed milliseconds—back at the selected rate, so it may be fractional.

What the path stages mean

  • Input buffer stages represent sample blocks collected before processing. Use zero for an output-only playback estimate.
  • Output buffer stages represent blocks queued for playback.
  • Extra or safety stages represent additional full buffers only when their existence is known or intentionally assumed.
  • Processing delay represents reported plug-in delay, lookahead or another known sample-based stage.
  • Known fixed delay holds delay reported in milliseconds, such as converter or device DSP time.

The output-only and input-plus-output buttons change only the three buffer-stage counts. They do not invent converter, driver, safety-buffer or plug-in values.

Buffer duration is not total latency

A 128-sample buffer lasts approximately 2.667 ms at 48 kHz. One input plus one output buffer therefore contributes approximately 5.333 ms before any other stage. That arithmetic is exact for the stated assumptions, but the assumptions rarely describe the entire physical path.

Do not automatically double a buffer value without identifying why two stages belong in the path. Conversely, do not report a single buffer as round-trip latency when input and output buffering are both involved.

Theoretical estimates versus measured results

This calculator does not measure an interface, driver or computer. Actual latency can also contain:

  • analogue-to-digital and digital-to-analogue converter delay;
  • hidden driver or hardware safety buffers;
  • USB, Thunderbolt or network transport scheduling;
  • operating-system and audio-engine scheduling;
  • plug-in delay compensation and device lookahead;
  • mixer, DSP and monitoring-path processing.

Prefer a device or audio engine's reported input and output latencies when they are trustworthy. For end-to-end verification, a loopback test captures the real path more directly. Enter a known difference as fixed delay only when its source and units are understood.

Reading changes in buffer size and sample rate

At a fixed sample rate, doubling the buffer size doubles each buffer stage's duration. At a fixed buffer size in samples, doubling the sample rate halves its duration. Higher sample rates may increase processor load, however, and that tradeoff is not represented by the timing formula.

Changing the displayed buffer or sample rate does not change the hardware. It recalculates the hypothetical path described by the inputs.

Common mistakes

  • Mixing samples from one sample rate with milliseconds calculated for another.
  • Adding a safety buffer merely because one might exist instead of documenting the assumption.
  • Treating reported plug-in delay as an extra stage when the audio engine has already compensated for it.
  • Comparing a one-way playback estimate with a measured round-trip result.
  • Presenting the theoretical total as a guaranteed or measured latency.