Signal Path
Buffer Path
Environment
Temperature
Pressure

`101.325 kPa` = `1 atm` = `1013.25 hPa`.

Estimated monitoring result

Adjust the path to estimate practical latency and compare it with what your DAW reports.

One buffer — the basic cost of the current buffer size
Estimated input — input side plus plugin share
Estimated output — output side plus plugin share
Estimated round-trip — whole monitored path in milliseconds
Heard total — electronic latency plus air travel time
Browser audio report Open to read what Web Audio reports for this output path

This asks Web Audio what the browser exposes for the current output path. It is a browser-path readout, not a DAW round-trip measurement.

No browser report collected yet.

Budget breakdown

Where the estimate is actually coming from.

Musical meaning

Translate the delay into beat-relative terms instead of only milliseconds.

Buffer comparison

How the same path behaves across common buffer sizes at the current sample rate.

Buffer 1 buffer Path buffers Plugin Electronic Air Heard total At tempo
How to think about the result

Reading the number

This tool estimates the path you describe. It does not prove that your DAW actually behaves that way.

oneBufferMs = (bufferSize / sampleRate) * 1000

bufferPathMs = oneBufferMs * (inputBuffers + outputBuffers + extraBuffers)

pluginMs = (pluginSamples / sampleRate) * 1000

estimatedRoundTripMs = bufferPathMs + pluginMs

speedOfSoundMps = moist-air estimate from temperature, humidity, and pressure

totalAirDistanceMeters = transducerToListenerMeters + distanceToMicMeters

airDelayMs = (totalAirDistanceMeters / speedOfSoundMps) * 1000

heardTotalMs = estimatedRoundTripMs + airDelayMs

If the `Reported round-trip` field differs from the estimate, that gap usually means the path has hidden buffering, different monitoring behavior, driver overhead, or the DAW is reporting a narrower part of the path than the musician feels.

Last Updated - 2026 April 1

Latency

Latency is for the ordinary recording question: how much time is this path actually costing?

It takes the pieces people usually reason about separately and puts them on one page:

  • buffer size and sample rate
  • path buffers
  • plugin delay
  • air travel
  • the musical meaning of the final number

The point is not to pretend the browser can detect your whole studio. The calculator is the manual model. The browser report is just a quick look at what Web Audio says about the current output path.

Limits

The calculator assumes a block-based path where latency is mostly sample rate, buffer size, path buffers, plugin delay, and air travel. Real systems can still differ because of drivers, DAW behavior, hidden buffers, direct monitoring, or timing jitter.