Livestream Audio Tech Rider: Mixes, Sync, and Signal Handoffs

TL;DR — A livestream audio tech rider maps every stage source to the stream, names the program and backup feeds, and assigns mixing, conversion, embedding, monitoring, recording, communications, and sync checks. Do not assume the room mix will translate online. Specify connector and audio format at each boundary, monitor near the final encoded output, and rehearse speech, music, playback, ambience, breaks, and failure recovery through the complete audio-video path.

Table of contents

1. Define the stream outcome
2. Map sources and destinations
3. Choose the stream mix workflow
4. Document signal handoffs
5. Plan monitoring, sync, and recovery
6. FAQ

Define the stream outcome

Begin with the listener and delivery path, not an equipment list. Record:

• event, date, venue, revision, rehearsal, and on-air time;
• platform or receiving destination;
• speech, music, playback, host, ambience, and remote-guest content;
• mono, stereo, or another agreed output format;
• program, backup, recording, and clean-feed deliverables;
• the owner of mixing, video embedding, encoding, recording, and approval.

Treat reinforcement, monitoring, recording, and streaming as separate destinations. They can share microphones and infrastructure, but each has a different listener and may need different routing, processing, monitoring, and staffing.

The rider documents the approved technical path. It does not itself grant permission to record, stream, or redistribute a performance. Name the person authorized to approve those uses.

Map sources and destinations

Start from the current input list. Keep each source name and channel number consistent across the stage plot, split, consoles, recorder, video system, and encoder.

Add stream-only sources that may not enter the PA:

• audience or room ambience microphones;
• host, commentator, or interpreter microphones;
• prerecorded introductions and video-playback audio;
• remote guests and their return feeds;
• standby audio;
• private talkback, slate, click, and guide channels that must remain off air.

Then define every destination:

Delete unused rows. A blank template is not a production plan.

Keep private sources off air

Mark click, guide, slate, tuning signals, private talkback, and technician solo buses NOT TO STREAM. Test those exclusions after console scenes, routing files, or show files are loaded.

For a remote contributor, document send and return paths independently. The return may require mix-minus so the contributor does not hear their own delayed signal. Name the device and operator that create the mix, then test it with the real remote path.

Choose the stream mix workflow

The room hears direct sound from instruments, loudspeakers, and the audience. The remote listener hears only signals included in the stream mix. An FOH left/right output is therefore not automatically a complete online mix.

Choose one deliberate workflow:

Avoid feed from desk. State which bus carries the program, whether house-mix changes affect it, and who may adjust it.

For independent FOH, monitor, and stream control, use the microphone splitter guide. For network transport, add endpoint, routing, clock, control, and recovery details from the digital audio network guide.

Document signal handoffs

Follow the audio from source to listener:

1. microphone, DI, playback, or remote source;
2. stage input and split or shared preamp;
3. stream console or mix bus;
4. program output and converter;
5. video switcher, embedder, capture interface, or encoder;
6. streaming service;
7. decoded return on a separate receiving device.

At each boundary, write:

• sending and receiving team or device;
• connector, channel count, direction, and mapping;
• analog or digital format and nominal level;
• sample rate and clock source when digital;
• embedded or separate relationship to video;
• artist and production responsibilities;
• primary and backup routes;
• test owner and acceptance point.

Connector shape is not a format. XLR, USB, HDMI, or network does not identify level, direction, mapping, or protocol. Use the mic-level versus line-level guide for analog boundaries.

Example program handoff

Replace the example with the real path. An adapter may change connector shape without converting level or format.

Plan monitoring, sync, and recovery

Monitor the delivered result

Meters show that a device sees signal; they do not prove the listener receives the intended mix. Provide a quiet monitoring position and inspect as close to final delivery as practical:

• stream-console program bus;
• audio at the encoder or video-program output;
• decoded return from the destination on a separate device and network path where available.

Name who watches each point. The stream mixer also needs communication with FOH, video, playback, stage management, and the encoder operator. Keep those communications outside program routing.

Verify audio-video sync

Video processing, conversion, and encoding can change timing. Document where audio delay can be adjusted and who owns the decision. Test a visible and audible event through the complete production path, then inspect the encoded or decoded result.

Do not copy a generic delay value into the rider. Required compensation depends on the actual camera, switcher, processing, encoder, and platform chain. Recheck after equipment, routing, frame-rate, or format changes.

Rehearse the complete path

1. Identify every input and confirm mapping.
2. Confirm gain and phantom-power ownership where relevant.
3. Verify stream-only and off-air sources.
4. Test mono or left/right routing at every boundary.
5. Listen at the encoder and decoded return.
6. Verify sync.
7. Rehearse playback, remote guests, hosts, and transitions.
8. Record and replay representative content.
9. Interrupt the primary feed and prove recovery.
10. Save the approved routing and revision.

Use representative program material. A spoken check one two cannot prove a music mix, while a music test cannot prove host, interpreter, remote-return, or break routing.

A backup is real only if it reaches the destination, can be selected quickly, and was heard during rehearsal.

Pre-send checklist

• Stream destination, contacts, rehearsal, and on-air times are current.
• Every stage and stream-only source has one stable name.
• Program, backup, recording, and local PA are separate destinations.
• Format and provider are named at every boundary.
• Gain, mix, embedding, encoding, sync, and monitoring owners are assigned.
• Click, guide, slate, solo, and private communications are off air.
• Remote return and mix-minus are documented where used.
• Encoder input and decoded return can be monitored.
• Representative content and recovery are rehearsed.
• Capture and distribution are authorized.

FAQ

What should a livestream audio tech rider include?

Include contacts and schedule, source list, program and backup destinations, mix workflow, physical and digital handoffs, gain and clock ownership, stream-only and off-air sources, monitoring points, audio-video sync, recording requirements, communications, rehearsals, and failure responses.

Can the FOH mix be used for a livestream?

It can be an agreed source, but it is not automatically suitable. The room hears acoustic sound that online listeners do not. Confirm stream-only sources, ambience, balance, processing, operator attention, and monitoring at the encoder or decoded output.

How do you send audio to a livestream?

Create a named program output, then document its channel count, connector, format, level, mapping, provider, and destination through the video or encoding chain. Test every boundary and listen to the delivered return.

How do you test audio and video sync for a livestream?

Send a visible and audible event through the complete camera, switcher, audio, encoder, and delivery path. Inspect the encoded or decoded result, adjust delay at the agreed stage, and repeat after relevant changes.

What backup audio should a livestream have?

Use an alternate program route appropriate to the production, clearly labeled, monitored, and selectable by a named operator. It may be a separate mix or a deliberately simplified source. Prove it end to end during rehearsal.

Keep the stream path with the Rider

Build the source map, stage plot, and input list in Techrider.live, then attach the verified stream handoff and share one current production plan with audio, video, and venue teams.

---

Last updated: 2026-08-11 · Reviewed for livestream source maps, program and backup feeds, signal handoffs, monitoring, audio-video sync, communications, and end-to-end tests.