Multitrack Recording Tech Rider: Inputs, Clock, and File Handoff

TL;DR — A multitrack recording rider should identify every source, feed point, track name, interface, sample rate, clock owner, operator, monitoring path, backup, and file handoff. Decide whether feeds are split, console-direct, or networked before load-in. Test the complete path by recording and replaying every required track—not merely by watching meters move.

Table of contents

1. Define the recording deliverable
2. Choose the recording feed
3. Build the track and patch list
4. Document clock, format, and control
5. Plan monitoring, storage, and handoff
6. Advance and test the recording
7. FAQ

Define the recording deliverable

“Record the show” is not a technical specification. Agree on the deliverable before choosing hardware:

• isolated tracks for every required input;
• a stereo reference mix, when needed;
• audience or room microphones;
• timecode, slate, or show notes when another team needs synchronization;
• the full performance, selected songs, rehearsal, or soundcheck;
• file format, sample rate, bit depth, naming, recipient, and deadline;
• permission, release, and ownership handled by the responsible production team.

Name the recording engineer, system provider, production contact, and person authorized to accept the files. Treat recording, streaming, broadcast, and press feeds as separate destinations unless the production has deliberately combined them.

Use the responsibility pattern in the concert production contact sheet to keep approvals and handoffs attached to named people.

Choose the recording feed

The feed point determines who controls gain and what can interrupt the recording.

A microphone splitter rider explains the FOH, monitor, and recording split. A recorder does not always need a separate analog split, but it always needs a defined and testable feed.

Do not assume that “USB,” “Dante,” “MADI,” or another interface name proves compatibility. Record the exact device, port, mode, channel capacity, sample rate, connector, and required driver. Confirm them against the actual hardware, firmware, and manuals.

Build the track and patch list

Use the same source names and numbers as the show input list. Add recording tracks and feed points instead of creating a second contradictory list.

This table is an example structure, not a standard channel count. Include every required show input, recording-only microphone, stereo pair, tap point, provider, and physical stage position. Add processing or mute behavior when it affects the feed.

The input-list and patch-sheet guide provides the base source list. Show recording-only microphones on the stage plot when they occupy space, require stands, or cross working routes.

Document clock, format, and control

Recording format

State the agreed sample rate, bit depth, file type, and channel format. The correct choice depends on the production, post workflow, interface, storage, and video synchronization requirements. Every connected device must support that format in its selected mode.

Do not copy a theoretical maximum channel count. Console ports and interface cards can expose different capacity or behavior at different settings; verify the real show configuration.

Clock ownership

Digital systems need one intentional clock plan. Document:

• the clock leader or master device;
• how every other device follows it;
• the physical or network clock path;
• the selected sample rate;
• who may change the configuration;
• the recovery procedure if synchronization is lost.

Clicks, pops, missing audio, or failed routes can indicate clock or format disagreement. A meter at one point does not prove that the entire recording path is synchronized.

Gain and routing control

State who controls microphone gain, phantom power, pads, channel routing, direct-output taps, and record arming. When recording shares preamps with FOH or monitors, agree how gain changes are communicated. Do not promise independent gain control unless the system provides it.

Plan monitoring, storage, and handoff

Monitoring

The recording engineer needs a cue path that can solo every track without affecting the room or performers. Show the operator position, monitoring device, headphones or loudspeakers, and communication path.

Meters reveal level and clipping; listening reveals buzzes, wrong routes, clock artifacts, handling noise, and mislabeled sources.

Storage and backup

Calculate storage from the actual track count, format, and duration using the recorder documentation. Confirm the primary volume, available capacity, secondary recording or agreed backup, power arrangement, operator, and procedure between sets.

A backup must name a real device, signal path, storage destination, and limitation. Two files on one recorder and one storage device do not cover every shared failure.

File delivery

Agree on folder and filename conventions before the show. A practical structure includes date, artist, venue, set, and stable track number. Deliver a matching track sheet and note substitutions, dropouts, or incomplete takes.

Confirm the transfer drive or approved upload destination, verification step, retention period, and person authorized to receive the files. Never place credentials in a public rider.

Advance and test the recording

Before show day

1. Close the show input list and recording deliverable.
2. Choose the feed method and assign every device and cable.
3. Verify capacity, format, clock, drivers, and storage.
4. Map show inputs to recording tracks with stable names.
5. Assign gain, phantom power, routing, arming, and delivery owners.
6. Schedule enough time to test and replay the system.

On site

1. Patch and label every source, split output, interface, and record track.
2. Confirm sample rate and clock status across all digital devices.
3. Line-check every show and recording-only input.
4. Record a short test with all required tracks active.
5. Replay representative tracks, stereo pairs, and room microphones.
6. Verify primary and backup recordings write to the intended locations.
7. Record the show, log exceptions, close files safely, and verify delivery.

The production manager, FOH engineer, and recording engineer can be invited to edit and save the same Rider and inspect its history. Export a dated PDF after the final channel map is confirmed.

Common multitrack-recording mistakes

Copying the FOH list without record tracks. Add a one-to-one map and recording-only sources.

Naming only the interface protocol. Specify devices, ports, modes, routes, clock, and ownership.

Leaving the direct-output tap undefined. Processing, mute, and fader behavior can change the recording.

Checking meters without replaying audio. A record-and-listen test finds routing, naming, and signal-quality errors.

Treating storage as an afterthought. Calculate capacity from the real format, duration, and track count.

Pre-record checklist

• Deliverable, permission, format, recipient, and deadline are confirmed.
• Every source has a show channel and recording track.
• Feed points, tap behavior, and recording-only microphones are documented.
• Devices, ports, modes, capacity, and drivers are verified.
• Sample rate and clock ownership match across the system.
• Gain, routing, arming, and monitoring owners are named.
• Primary storage and a real backup have verified capacity.
• A test recording has been replayed and heard.
• File naming, track sheet, transfer, and retention are assigned.

FAQ

What should a multitrack recording tech rider include?

Include the deliverable, source-to-track map, feed method, devices and ports, sample rate, bit depth, clock owner, gain and routing responsibilities, monitoring, storage, backup, test procedure, filename convention, and file recipient.

How do you record a live concert in multitrack?

Route each required source through a defined split, console output, interface, or audio network to a separate track. Label the tracks, synchronize digital devices, set safe levels, record a test, replay it, and monitor the recording throughout the show.

Does a live recording need a microphone splitter?

Not always. Feeds can come from an analog split, console direct outputs, a digital interface, or an audio network. The method must provide the required channels and define gain, phantom power, routing, clock, and failure responsibilities.

What sample rate should a live recording use?

Use the rate agreed by production and post-production that every connected device supports in its selected mode. Confirm video synchronization, interface capacity, storage, clocking, and the receiving editor's workflow instead of assuming one setting fits every show.

How should live multitrack files be delivered?

Deliver clearly named files with a matching track sheet and show notes. Agree on the drive or upload destination, folder structure, recipient, verification, deadline, and temporary backup-retention policy before recording begins.

Keep every show input connected to its recording track

Build the stage plot and input list in Techrider.live, invite the recording engineer to edit the same Rider, and export one confirmed show-day PDF after the recording map is saved.

---

Last updated: 2026-08-10 · Reviewed for live multitrack feed, clock, monitoring, storage, and file-handoff planning.