Stage Box and Subsnake Patch List: A Live Sound Guide

TL;DR — A stage box patch list maps every source from its nearby connection point to the main stage I/O and console channel. Give each box a stable name, list the source, local socket, next destination, final input, and owner, then label the hardware to match. Show box locations on the stage plot when placement affects cable runs. Keep artist requirements separate from the venue’s final physical patch.

Table of contents

1. Understand the signal path
2. Decide when a subsnake helps
3. Build the patch list
4. Show boxes on the stage plot
5. Label, patch, and verify
6. FAQ

Understand the signal path

A stage box is a group of audio connectors placed near the stage. Depending on the system, it may connect to the console through an analog multicore, a digital transport, or another installed audio path.

A subsnake is a smaller multicore used to collect several nearby sources before they reach a main stage box, splitter, or rack. It is also called a sub-snake, satellite box, drop box, or stage drop in some crews. Terminology varies, so the document should define the label used for that show.

The physical path may be:

Kick microphone → Drum subsnake D1 → Main stage box A17 → splitter input 17 → console input 17

That path contains several different numbers. Treating all of them as Channel 17 hides the exact handoffs and makes troubleshooting slower.

Input list versus physical patch

An input list describes the artist’s sources and required destinations. It should remain useful even if the venue changes its stage-box layout.

A stage box patch list records how those sources enter the actual system for a specific setup. The two lists should agree on source names and input order, but they do not have to use the same physical socket number.

Do not rewrite the artist’s channel requirement silently to match an available socket. Record the physical route separately.

Decide when a subsnake helps

A subsnake is useful when a group of sources is clustered away from the main stage box. Common examples include:

• a drum kit with several microphones;
• a keyboard position with multiple outputs;
• a horn or string section;
• a playback and wireless rack;
• sources distributed across stage left and stage right;
• a festival stage using repeatable connection zones.

The goal is not to maximize the number of boxes. It is to reduce long individual cable runs, crossings, clutter, and changeover work while preserving access and safe cable routes.

Choose locations from the sources

Place a box where short source cables can reach it without crossing performer paths, stairs, riser edges, doors, wheels, or changeover routes. Keep connectors accessible to the patch crew and protect them from feet, liquids, moving backline, and scenic elements.

Do not choose the exact venue patch architecture in an artist rider unless the artist carries and controls that system. An artist can show preferred connection zones and carried hardware; the venue or audio provider confirms the final boxes, cable paths, capacity, and system compatibility.

Count complete paths, not only inputs

Before assigning sockets, inventory:

• microphone, DI, playback, and talkback inputs;
• spare or alternate sources that may be patched;
• return paths required for wedges, wired IEMs, or other artist equipment;
• analog or digital format at every handoff;
• fan-outs, multipins, adapters, or tails;
• split destinations for FOH, monitors, recording, or broadcast;
• available physical sockets in the configured system.

An input connector and an output connector are not interchangeable just because they share the same box. Label the direction explicitly.

Build the patch list

Start with the current input list. Add physical routing columns only after the stage layout, equipment providers, and system boundaries are known.

Recommended columns

Use identifiers that can be read on the stage. SL-04 is more useful than Box 2 somewhere left.

Example stage patch

This is an example structure, not a universal channel order. Match the show’s approved input list and the provider’s real system.

Preserve stereo pairs and source identity

Keep paired sources adjacent and use explicit labels such as Playback L and Playback R. Do not write only Stereo in one row: the patch crew needs two physical paths, and the console engineer needs to know which is left and right.

Use the same source name on the input list, patch list, console file, cable label, and stage plot. If the source is renamed, update every place where crews use that name.

Plan useful spare capacity

Do not promise an arbitrary percentage of spare sockets. Instead, identify the likely failure or change points:

• one available socket near a dense instrument position;
• a documented alternate path around a damaged subsnake channel;
• spare fan-out or adapter capacity where the system needs it;
• clearly reserved inputs for approved guest or support-act sources.

Mark a spare as SPARE; do not leave an unexplained gap that might be patched accidentally.

Show boxes on the stage plot

Show a stage box or subsnake on the stage plot when its location affects:

• source cable reach;
• riser or rolling-platform disconnects;
• performer movement;
• stage traffic and changeovers;
• a carried split or monitor rack;
• the boundary between artist and venue equipment.

Use a simple labeled rectangle or connection symbol. Include the box name and direction, such as DRUM INPUT SUBSNAKE, without drawing every cable as a line across the plot.

Keep detailed socket mapping in the patch list. The plot should answer where; the patch list should answer which connector goes where.

Mark responsibility boundaries

If the band carries an IEM rack and hands labeled tails to the venue, show:

1. the artist’s microphones or supplied inputs;
2. the carried splitter or rack;
3. the labeled FOH tails;
4. the venue connection point;
5. who supplies each cable and adapter.

For split ownership, phantom power, and gain responsibility, use the Microphone Splitter Tech Rider.

Label, patch, and verify

Before load-in

• Confirm the current input count and source names.
• Confirm box types, locations, socket counts, and system format.
• Agree the artist/venue/vendor handoff.
• Check that carried fan-outs and multipins match the supplied system.
• Print or make available the same revision used to prepare console files.
• Assign who may change the physical patch.

Label the system

Labels should survive the show but be removable without damaging equipment. Match the patch list exactly:

• box name on every local box;
• socket numbers visible at the connector;
• both ends of fan-outs and long cables;
• multipin or trunk identity;
• input and output direction;
• artist-owned versus provider-owned hardware when ambiguous.

Color can support the labels, but it should not be the only identifier.

Patch in a controlled sequence

1. Position the boxes and protect the cable routes.
2. Connect trunks, multipins, or network links under the responsible provider.
3. Patch sources to labeled local sockets.
4. Patch the next handoff to the main stage I/O or splitter.
5. Confirm the console patch against the approved list.
6. Apply phantom power only from the agreed point.
7. Line-check one source at a time from performer end to console.
8. Record any approved change on the current patch list.

The Line Check vs Soundcheck guide explains why connectivity verification should be completed before musical evaluation.

Troubleshoot by boundaries

When a source fails, follow the documented path in order:

1. source and short cable;
2. local socket;
3. subsnake trunk;
4. main box or split;
5. console input assignment;
6. channel processing and routing.

Change one boundary at a time. Moving several plugs without updating the document can make the signal return while leaving an undocumented patch for the next crew.

Common patching mistakes

Using one number for every layer. Local socket, main input, split input, and console channel may differ.

Putting a full patch diagram on the stage plot. Dense cable lines hide positions and access. Keep connector detail in a table.

Naming boxes by color only. Color is easy to confuse in low light and inaccessible to some readers. Add text identifiers.

Letting labels drift from the list. Hardware, document, and console names must match.

Assuming a digital stage box is compatible. Connector format, transport, clocking, firmware, network design, and control ownership require provider confirmation.

Changing the artist input list to solve a venue patch. Preserve the source order and record the physical mapping separately.

Pre-show checklist

• Every source has a stable artist input number and name.
• Every local box has a unique visible identifier.
• Local sockets, next handoffs, and final inputs are mapped.
• Input and output directions are explicit.
• Stereo pairs and spares are labeled.
• Artist, venue, and vendor responsibilities are assigned.
• Stage plot shows boxes that affect placement or changeover.
• Phantom-power and split ownership are agreed.
• Hardware labels match the current patch list.
• Approved changes will be recorded during line check.

FAQ

What is a stage box in live sound?

A stage box groups audio connectors near the stage and connects them to a console or audio system through an analog multicore, digital transport, or installed path. It reduces the need for many long individual cables between sources and the mix position.

What is a subsnake?

A subsnake is a smaller multicore that collects nearby sources and connects them to a main stage box, splitter, or rack. It is useful around drums, keyboards, stage-left or stage-right instrument groups, and repeatable festival patch zones.

How do you make a stage box patch list?

Begin with the approved input list. For each source, record its local box and socket, next handoff, final physical input, console channel if confirmed, provider, and operational notes. Give every box a visible name and label the hardware to match.

Should stage boxes be shown on a stage plot?

Show them when location affects cable reach, performer paths, risers, changeovers, carried racks, or responsibility boundaries. Keep the detailed socket map in a separate patch table so the stage drawing stays readable.

What is the difference between an input list and a stage box patch list?

The input list states which sources the artist requires. The stage box patch list maps those sources through the physical connectors used for a particular system or show. Source names and intended channel order should agree even when socket numbers differ.

Keep the physical patch connected to the Rider

Build the stage layout and input list in Techrider.live, invite the responsible engineer to edit and save the same Rider, and keep the approved source names aligned with the show’s stage box patch.

---

Last updated: 2026-07-31 · Reviewed for stage boxes, subsnakes, physical input mapping, labeling, split handoffs, and line-check workflow.