Soft Patch vs Physical Patch on a Mixer: Map the Signal Correctly

TL;DR — A physical or hard patch is the real connection between a source and a socket, cable, stage box, splitter, or output. A soft patch is the console or audio-network mapping from an available I/O port to a processing channel or destination. One cannot repair the other. Record both sides, name the preamp owner, test source-to-destination routing, save a known 1:1 recovery state, and verify every output before handoff.

Physical patch and soft patch are two separate maps

A physical patch, sometimes called a hard patch, is made with hardware: a microphone cable into stage-box socket 1, an XLR output into a powered speaker, or a multicore connection between stage and FOH.

A soft patch is a logical assignment inside a digital console, processor, or audio network. It can map stage-box socket 1 to console channel 12, send matrix 3 to a local output, or route one available source to more than one processing path without moving a cable.

Source
  │ physical cable
  ▼
Stage-box socket 1
  │ soft input patch
  ▼
Console channel 12
  │ bus and output routing
  ▼
Matrix 3
  │ soft output patch
  ▼
Output socket 6
  │ physical cable
  ▼
Amplifier / powered speaker / recorder

The input list and patch sheet describe what should connect. These two patch layers describe how that requirement becomes an actual route.

Use physical patching for the hardware boundary

Physical patching establishes the electrical or optical connection. It determines which source reaches a hardware input, which output connector feeds a destination, and which cable type, gender, format, or adapter is required.

Change the physical patch when:

• the source is plugged into the wrong socket;
• a cable, connector, adapter, or stage-box port has failed;
• phantom power or preamp ownership must remain on a specific input;
• an analog split or isolated handoff is required;
• the destination needs a different connector or signal format;
• a 1:1 festival patch is safer than a custom software remap.

Moving a cable is visible to the stage team, but it can affect every user of that socket. Before repatching a shared split or networked stage box, confirm who owns the preamp and which consoles, recorders, or broadcast systems depend on the source.

Use soft patching for logical assignment

Soft patching is useful when the hardware should stay in place but the console layout or destination needs to change.

Common uses include:

• placing festival inputs on a preferred channel order;
• switching a channel from a local input to a stage-box or network source;
• mapping a spare socket to an existing processing channel;
• assigning mix buses and matrices to physical outputs;
• routing tie lines directly between I/O ports;
• sending one source to two processing channels for different purposes;
• changing from live inputs to multitrack returns for virtual soundcheck.

The flexibility creates hidden state. A fader labelled KICK may not receive physical socket 1, and output 6 may not carry mix 6. Names help, but only the patch matrix proves the connection.

Source sockets, preamps, and channels are not interchangeable

On many systems, the physical socket owns the analog preamp, pad, and phantom power. A soft patch assigns that socket's converted signal to a processing channel. Reassigning socket 1 from channel 1 to channel 12 does not necessarily move the head amp; gain and 48V may still belong to socket 1 and may be shared with another console.

Keep these identifiers distinct:

For shared-head-amp workflows, read preamp gain versus digital trim. Soft patching changes assignment; it does not grant ownership.

Choose the simplest patch that survives handoff

A 1:1 patch—socket 1 to channel 1, socket 2 to channel 2—is easy to inspect and recover. A custom soft patch can produce a more useful surface layout without moving hardware. Choose the smallest mapping that supports the real production need.

Avoid clever remaps that save seconds during setup but cost minutes during a fault. If a non-1:1 map is necessary, make it readable in the console labels and handoff document.

Input patch, output patch, and tie lines

An input patch assigns a hardware, network, USB, card, or playback source to a console processing channel. An output patch assigns a bus, matrix, direct out, monitor, talkback, or other source to a physical or network destination.

A tie line usually routes an I/O source directly to an I/O destination without consuming a normal mix bus. It can provide a clean handoff to recording, broadcast, another console, or a stage output, but it may bypass expected channel processing, mutes, meters, and controls. Document its source and destination explicitly.

Flexible consoles may allow many-to-one, one-to-many, or alternate source assignments. Confirm whether a new assignment replaces an old one, creates a mult, or becomes an alternate that must be selected later.

Build and verify the complete route

1. Freeze the physical socket map

Label stage boxes, subsnakes, racks, and output panels. Record the source, connector, socket number, cable destination, provider, and any phantom-power requirement. The stage-box patch-list guide provides a practical hardware inventory.

2. Audit available I/O

Confirm installed cards, stage racks, network devices, sample rate, clock state, port names, and online status. A saved cross-point is not valid if its device is absent or configured differently.

3. Create the input map

Map each physical or network source to the intended processing channel. Apply stable names at both the socket and channel layers where the system permits. Record any mult, alternate input, or virtual-soundcheck return.

4. Create the output map

Trace every main, monitor, fill, delay, stream, record, and communication path to its actual output socket or network destination. Do not stop when a bus meter moves.

5. Test in signal-flow order

Use one safe, identifiable source at a time. Verify the physical input, preamp meter, channel meter, bus, matrix, output meter, physical connector, and final destination. Follow the live sound troubleshooting checklist rather than changing several layers at once.

6. Save and rehearse recovery

Store the verified show-file version and export a patch report or screenshots only for local operations—not as Learn article content. Keep a written 1:1 or baseline recovery map. Test what happens after a scene recall, file load, device restart, or switch to virtual soundcheck.

Document both sides of every patch

In Techrider.live, align stage-plot labels, input-list rows, and patch notes. Invite the responsible engineer to edit the same Rider, save after an approved change, inspect history when a mapping differs, and export a dated PDF for crews who need an offline copy.

Patch handoff checklist

• Every source has a physical socket and processing-channel assignment.
• Physical input, digital source, and channel numbers are not conflated.
• Preamp, pad, and phantom-power ownership is named.
• Mults, alternate inputs, tie lines, and virtual returns are explicit.
• Every output is verified at its final physical or network destination.
• Scene recall cannot silently replace the approved map.
• A known baseline and recovery sequence are available.

FAQ

What is a soft patch on a digital mixer?

A soft patch is a software assignment between an available I/O source and a console channel or between a bus or direct signal and an output destination. It changes the logical map without moving the physical cable.

What is the difference between a hard patch and a soft patch?

A hard or physical patch is the real cable and socket connection. A soft patch is the saved logical routing inside a console, processor, or audio network. Both must be correct for the signal to reach its destination.

Does soft patching change the preamp gain?

Not by itself. On many systems the physical input socket owns the analog preamp, while the soft patch sends that input to a processing channel. Confirm which device and operator owns gain, pad, and phantom power.

Can one physical input feed two mixer channels?

Many digital systems allow one input source to feed multiple processing channels. This can support separate processing paths, but the channels may share one preamp. Check gain ownership, latency, routing, mute behavior, and headroom.

How do you document a digital mixer patch?

Record the source, physical rack and socket, digital source label, processing channel, preamp owner, alternate or mult assignments, final output destination, recall behavior, and recovery baseline. A channel number alone is not enough.

Make every mapping traceable

Create the current stage plot and input list with Techrider.live, use matching names at each boundary, and document exceptions to the simplest map. A useful handoff lets another engineer trace source, socket, channel, bus, output, and destination without guessing.