Dante Latency Budget

Budget Dante audio latency across devices and network hops.

Description

An audio-latency budget combines device contributions with an assumed per-hop network allowance.

An audio-latency budget combines device contributions with an assumed per-hop network allowance. It is a planning sum rather than a Dante network measurement.1

Budget Dante audio latency across devices and network hops.

When to use Dante Latency Budget

Use this tool to budget Dante audio latency across devices and network hops.

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.

How to use Dante Latency Budget and understand its results

  1. Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
  2. Enter deviceLatenciesMilliseconds, networkHopCount, latencyPerHopMilliseconds, maximumLatencyMilliseconds using the field table and calculation rules, then run the tool.
  3. Read deviceLatencyMilliseconds, networkLatencyMilliseconds, totalLatencyMilliseconds, latencyMarginMilliseconds, withinBudget. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
Input fieldMeaningValue type; see rules belowRequirement
deviceLatenciesMillisecondsDevice latencies (ms)list of numberRequired
networkHopCountNetwork hop countinteger; minimum: 0Required
latencyPerHopMillisecondsLatency per hop (ms)number; minimum: 0Required
maximumLatencyMillisecondsMaximum end-to-end latency (ms)number; minimum: 0Required

Enter nonnegative device milliseconds, nonnegative integer hop count and nonnegative hop allowance/budget. Return device, network and total latency, signed budget margin and inclusive pass flag. Empty device lists are allowed.

totalLatency=ΣdeviceLatency+hopCount×latencyPerHop

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output fieldMeaningValue type
deviceLatencyMillisecondsTotal device latency (ms)number; minimum: 0
networkLatencyMillisecondsNetwork latency (ms)number; minimum: 0
totalLatencyMillisecondsTotal latency (ms)number; minimum: 0
latencyMarginMillisecondsLatency margin (ms)number
withinBudgetWithin supplied budgetboolean
json
{
  "input": {
    "deviceLatenciesMilliseconds": [
      1,
      2,
      1
    ],
    "networkHopCount": 2,
    "latencyPerHopMilliseconds": 0.5,
    "maximumLatencyMilliseconds": 6
  },
  "output": {
    "deviceLatencyMilliseconds": 4,
    "networkLatencyMilliseconds": 1,
    "totalLatencyMilliseconds": 5,
    "latencyMarginMilliseconds": 1,
    "withinBudget": true
  }
}

Limitations and assumptions

No packets, network topology or device settings are inspected. Jitter, clock synchronization, buffering and actual Dante configuration limits are not inferred.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Distributed Speaker Load: Total distributed-speaker taps against an amplifier loading limit. For a complementary task, use Stage Sound Sync Delay: Calculate the sound-delay adjustment needed to reach a caller-defined audiovisual offset.

References

  1. Dante Latency Budget — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies