Trace each playback stem to its intended physical destination

Name the content before naming the connectors

Identify the playback file revision and the purpose of each channel or stem. State which material is public, which belongs only to a performer or operator, and which destinations need a separate feed. Do not rely on a stereo filename to explain what its channels contain. A producer should obtain a channel manifest from the content owner before asking the venue to accept the package.

Resolve ambiguous labels such as main, spare or guide. Describe what should be audible and where, and explicitly identify forbidden destinations. Record whether a destination is an audience system, recording input, remote contribution or private monitor. Keep any confidential material out of test fixtures. Use harmless, distinguishable sample content approved by the audio team so an accidental destination error does not expose private speech or disrupt an occupied venue.

Trace the intermediate routing layers

QLab 5 documents separate cue outputs and device outputs, with a patch matrix connecting them. This establishes why a cue-output label alone does not prove the physical destination. The workflow below extends that distinction into a producer’s acceptance record rather than prescribing a QLab configuration.

Have the qualified operator trace the agreed source channel through the playback patch, selected device output and downstream destination. Record the relevant identities in one row. If several channels intentionally combine, label that combination and its owner rather than treating it as an unexplained duplicate. If a channel is deliberately unused, mark it unused. A complete map should expose an unexpected path without requiring a reviewer to infer meaning from connector numbers alone.

Verify destinations using controlled evidence

Agree a safe rehearsal window and verification method with the audio team. Check identifiable sample content one path at a time and obtain confirmation from the receiving point. A playback meter establishes activity inside the software; a receiving observation establishes a different part of the route. Record both when they help isolate a failure. Do not ask unqualified staff to disconnect equipment or inject signals into a live system.

Test required absences as well as arrivals. A private guide reaching the audience is a failure even if the intended monitor also receives it. Distinguish a routing defect from content that already contains the wrong material. If the file itself combines public and private audio, a downstream label cannot separate them by intent. Return that issue to the content owner and verify the corrected export before accepting the patch.

Reconcile substitutions against the accepted map

When an interface, playback computer or receiving destination changes, compare the new path with the accepted map. The same numerical output can represent a different physical connection on another device. Ask the operator to identify affected rows and repeat their end-to-end checks. Do not accept a substitution merely because the new device has the same number of sockets or the application no longer reports a warning.

Freeze the verified map with the playback package revision and receiving configuration. Keep temporary changes visible, including any deliberately unavailable destination. Hand the operator a short discrepancy list rather than mixing unresolved issues into an apparently final diagram. The production lead can then decide whether to simplify the playback requirement or wait for correction. Acceptance concerns the demonstrated route; it does not certify the venue’s entire audio infrastructure or guarantee future performance.

Make the reasoning concrete.

A fictional museum presentation carries narration for visitors and a separate rehearsal count for a performer. A replacement audio interface is connected shortly before the final run, and the original output numbers are retained without checking their destinations.

The producer chooses path reconciliation before accepting the replacement, using harmless sample labels rather than the live performance material.

Take the questions into your next brief.

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

1. Content

   What does each source channel contain?

2. Intent

   Which destinations must receive or exclude it?

3. Path

   Which cue output, device output and receiving point implement that intent?

4. Evidence

   Who observed arrival and absence at the destinations?

5. Substitution

   Which changed components require a repeated check?

Watch for the wrong conclusion.

• Approving a route from software meters alone.
• Assuming identical output numbers mean identical physical destinations.
• Ignoring unintended destinations because the wanted one works.

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.

• QLab 5: The Audio Output Patch Editor →Primary versioned product documentation · Supports: Supports the distinction and routing relationship between cue outputs and device outputs in QLab 5. The end-to-end acceptance method is original analysis.