Keep a routed audio path separate from a clock-stable one

Define the period and devices under review

Identify the network-audio devices that carry the event’s consequential paths and the rehearsal interval being evaluated. Record which outputs matter to the audience, recording or contribution feed. A stability statement without a time period or device scope is difficult to use: it may describe a different setup or omit the device associated with a reported dropout.

Ask the authorized technical owner to preserve relevant status evidence while the agreed rehearsal runs. Coordinate observation times so an audible symptom can be compared with technical events. Do not ask the producer to change leader preferences, switch settings, energy-saving behavior or network security. The acceptance task is to establish what happened and what the qualified owner has verified, not to implement a troubleshooting recipe.

Distinguish present status from event history

Audinate’s Clock Status Monitor documentation describes timestamped instability and synchronization events; a device losing synchronization is automatically muted until it regains it. It also notes that clearing the log resets the status icon. A green indicator therefore cannot substitute for preserved history.

Have the specialist identify relevant events and the devices involved. Compare their timestamps with the observed audio symptom, while keeping correlation separate from a proven cause. A matching event can guide investigation without establishing why synchronization was lost. Preserve the original evidence before any authorized cleanup so the handover does not lose the only trace of an intermittent condition. Record the technician’s interpretation alongside, not in place of, the observations.

Define what correction must demonstrate

Ask the technical owner to state the proposed correction, affected paths and verification scope in terms the production team can understand. The producer need not prescribe network settings to require evidence that the previously affected receiving path now behaves as intended. Agree a representative retest period and operating conditions appropriate to the event, with the owner explaining any limitations.

Observe both the relevant technical status and the delivered audio during the retest. Do not manufacture a live failure or disconnect infrastructure to prove resilience without a separate authorized engineering plan. If the problem cannot be reproduced, say so. Lack of recurrence during a limited rehearsal is useful evidence but not proof that the original cause has disappeared. Keep any unresolved risk and operational response visible to the production decision-maker.

Handover an evidence-based readiness statement

Summarize the affected device, event times, audible consequence, specialist finding and retest result. Distinguish corrected and demonstrated, not reproduced, and still unresolved. Include the configuration identity needed to recognize a later change. The readiness statement should be understandable without interpreting raw engineering graphs, while leaving those records available to the responsible technical staff.

Reopen the relevant acceptance item after a material device or network change identified by the specialist. Keep ordinary routing checks separate: successful routing does not replace clock review, and clean clock evidence does not prove that every source reaches the right destination. This separation helps the team avoid declaring the system ready because one dashboard appears healthy while another essential acceptance question remains unanswered.

Make the reasoning concrete.

A fictional streamed workshop has a brief audio mute during rehearsal. By the time the producer checks the control display, the current indicator is green, and the receiving audio has returned.

The producer chooses interval-based review and records any remaining uncertainty rather than treating recovery as proof of permanent correction.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Scope

   Which devices, paths and rehearsal interval are covered?

2. Events

   What timestamped status evidence was preserved?

3. Symptom

   What did the receiving path actually do?

4. Disposition

   What did the qualified specialist establish or leave unresolved?

5. Retest

   Which conditions and duration bound the new evidence?

Watch for the wrong conclusion.

• Erasing logs before reviewing an intermittent fault.
• Treating a present indicator as the whole event history.
• Confusing a timing check with routing acceptance.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis. Sources support only specifically attributed principles. Platform guidance can change; legal requirements depend on jurisdiction and context. No measured results or named human reviewer are claimed.

• Audinate Dante Controller User Guide: Clock Status Monitor →Primary network-audio product documentation · Supports: Supports timestamped clock events, mute behavior on lost synchronization and the effect of clearing the log. The acceptance framework is original analysis.