Live Sound Troubleshooting Checklist: Find Audio Faults Fast

TL;DR — Troubleshoot live sound by defining the symptom, deciding whether it affects one channel or the whole system, and tracing one known test signal from source to destination. Check power, connectors, patching, input source, gain, mute, bus assignment, processing, output patch, and loudspeaker path in order. Change one variable at a time, keep levels safe, label confirmed faults, and update the current Rider when the working configuration changes.

Table of contents

1. Start with a safe fault report
2. Use signal flow instead of guessing
3. Troubleshoot common symptoms
4. Use substitution tests correctly
5. Run a pre-show recovery checklist
6. Document the fix
7. FAQ

Start with a safe fault report

A live sound troubleshooting checklist is a repeatable sequence for finding where an audio path stops working or becomes unreliable. It prevents several people from changing unrelated controls at once and gives the team a record of what was tested.

Before touching the system, describe the fault precisely:

• symptom: no sound, low level, distortion, hiss, hum, crackle, intermittent audio, or wrong destination;
• scope: one source, several related channels, one mix, one loudspeaker zone, or the entire system;
• time: constant, triggered by movement, present after a scene recall, or appearing only at performance level;
• last known good point: source output, stage input, console meter, bus meter, physical output, amplifier, or loudspeaker;
• recent change: cable move, patch change, power cycle, show-file load, network change, or equipment substitution.

Protect people and equipment first. Lower or mute the affected destination before reconnecting output wiring, changing powered loudspeaker connections, or sending test signals. Follow the equipment manufacturer's power and connection procedures. Never defeat a protective earth connection to chase hum.

Local or global?

The fastest first split is whether the fault is local or global.

If one channel fails while every other path works, begin at that source. If all outputs fail, do not spend ten minutes swapping a single microphone cable.

Use signal flow instead of guessing

Trace the actual route shown in the live sound signal-flow guide:

source → mic / DI → cable → stage input → transport → console input
→ input processing → bus assignment → bus / matrix → physical output
→ system processing → amplifier / powered speaker → loudspeaker

At each point ask two questions: Does signal arrive? Does it leave? Console meters, cue/PFL, device indicators, network status, and a controlled test tone can locate the boundary. A meter is evidence only for the point it measures; input activity does not prove that the channel is assigned to the correct bus or physical output.

Use this sequence:

1. Confirm the intended source is producing signal.
2. Confirm the connector is fully seated and the cable is the correct type.
3. Verify the stage socket and console input patch against the current input list and patch sheet.
4. Check input source selection, gain or trim, pad, phantom power where required, polarity, mute, and channel processing.
5. Verify channel-to-bus assignment and the relevant send or fader.
6. Check bus mute, master level, processing, matrix assignment, and output patch.
7. Confirm the physical output, system processor, amplifier or powered speaker, and loudspeaker connection.
8. Restore level gradually and verify the complete destination.

Do not flatten every setting or reload an unrelated show file as a first response. That destroys useful evidence and can create more faults.

Troubleshoot common symptoms

No sound from one input

Start at the source and move downstream. Confirm that a microphone switch, instrument volume, playback output, or DI power state is correct. An active DI may require its specified battery or phantom-power arrangement; a passive DI does not. Verify mic level versus line level and do not assume that matching connector shapes mean compatible signals.

Then check:

• source cable and XLR cable with known-good replacements;
• stage socket and input patch;
• digital console input-source selection;
• gain, pad, phantom power, mute, gate, insert, and channel assignment;
• whether PFL shows signal before the fader;
• sends to the required main or monitor bus.

No sound from a monitor or PA zone

Send a known-good input to the affected mix at a controlled level. Verify the bus master and mute, then the output socket assigned to that bus. Digital consoles can route a valid mix to the wrong physical connector, so a moving bus meter does not prove that the expected jack is active.

Inspect the line cable, system processor, amplifier channel, powered loudspeaker input mode, and loudspeaker cable. If the problem is one side of a stereo or paired system, compare the two paths at equivalent points.

Distortion

Find the first point where the signal becomes distorted. Check source output, DI pad, input type, preamp gain, channel and bus meters, inserts, bus processing, system processor, and powered-speaker input sensitivity. Reducing the final loudspeaker level cannot repair clipping that already occurred upstream.

Use the gain-staging guide to restore headroom. If only one source distorts, isolate that channel. If every source distorts at the same destination, inspect the shared bus and output path.

Hum, buzz, hiss, or crackle

Separate the noise from the program signal. Mute input channels, then add paths one at a time at a safe level. Check for damaged cables, inappropriate unbalanced runs, loose connectors, excessive input gain, wrong input sensitivity, and nearby interference sources.

Keep protective earth intact. Use equipment-approved balanced connections and properly designed isolation or DI solutions where needed. Never improvise a mains-ground modification. The balanced versus unbalanced audio guide explains why connector type alone does not guarantee a balanced path.

Intermittent audio

Record what triggers the dropout: cable movement, connector pressure, performer motion, high level, heat, scene change, wireless movement, or network status. Watch meters on both sides of the suspected point. A faulty cable or connector is common, but an over-aggressive gate, bad insert, wrong clock, digital patch, RF fault, or protection state can produce similar symptoms.

Quarantine a confirmed faulty cable or device immediately. Label it clearly and move it out of the working spares so another crew member does not put it back into service.

Feedback

Reduce the affected path, identify the microphone and loudspeaker involved, and correct placement, routing, open-mic count, stage level, and gain before applying precise EQ. Use the dedicated guide on how to prevent microphone feedback for a safe response sequence.

Use substitution tests correctly

A substitution test replaces one suspected element with a known-good equivalent. It is useful only when the replacement is compatible and everything else stays unchanged.

For example:

1. mark the current safe level and mute the destination;
2. replace only the suspected XLR cable;
3. restore the connection and level safely;
4. test the same source and route;
5. record whether the symptom moved, disappeared, or remained;
6. return the system to a documented state.

Swapping left and right paths can show whether a fault follows the feed or remains with an amplifier/loudspeaker branch. Make that swap only at a suitable line-level point with outputs controlled. Never perform an improvised swap that changes load, connector wiring, phantom-power conditions, or equipment safety.

Keep a known-good test kit

A practical test kit may include:

• a verified dynamic microphone;
• short verified XLR and instrument cables;
• an appropriate passive or active DI with its required power source;
• headphones suitable for console cue monitoring;
• a cable tester used within its rated applications;
• readable fault tags and a marker;
• the current input list, patch sheet, and output map.

The kit is useful only if its known-good items remain separated from untested returns.

Run a pre-show recovery checklist

• The symptom, affected scope, and trigger are written clearly.
• A safe master or destination level is established before tests.
• One known-good source can be traced through the system.
• Physical and digital input patches match the current document.
• Gain, pad, phantom power, mute, gate, insert, and source selection are checked.
• Bus assignment, send, master, matrix, and physical output patch are checked.
• System processing, amplifier, loudspeaker, and cabling are verified.
• Only one variable changes during each substitution test.
• Faulty items are labeled and removed from working stock.
• The restored route is tested at a representative but safe level.
• The fix, replacement, and action owner are recorded.

Document the fix

If a repair or substitution changes a source, channel, stage socket, bus, output, monitor destination, or equipment requirement, update the current Rider. Do not leave the working configuration only on console tape or in a crew message.

In Techrider.live, invite the relevant engineer or production lead to edit the same Rider, save the corrected input, monitor, and stage details, and inspect history when the team needs to understand a change. Share the current link and export a dated PDF when an offline handoff is required.

FAQ

How do you troubleshoot a live sound system?

Define the symptom and scope, establish a safe level, then trace one known-good signal from source to destination. At each stage verify arrival, departure, power, connector, patch, gain, mute, assignment, processing, output routing, amplification, and loudspeaker path. Change one variable at a time.

Why is there no sound from the PA?

Common causes include missing power, a master or bus mute, no channel assignment to the main bus, incorrect digital input or output patching, a disconnected cable, a system processor or amplifier state, or the wrong powered-speaker input setting. Find the last point with valid signal before replacing parts.

How do you find a bad channel in a mixer?

Send a known-good source and cable into the suspected input, then send the same source into a known-good channel with equivalent settings. Compare PFL, meters, patching, gain, processing, bus assignment, and output. Keep the test level controlled and change only one element at a time.

What causes hum and buzz in live sound?

Hum or buzz can come from damaged or inappropriate cabling, unbalanced connections, grounding relationships between equipment, power problems, loose connectors, or electromagnetic interference. Isolate connected paths one at a time, use approved balanced or isolation solutions, and never remove protective earth.

How do you troubleshoot intermittent audio?

Identify the trigger and monitor signal before and after each suspected point. Test cables and connectors, gate and insert settings, digital patch and clock status, wireless conditions, power, and protection states. Remove and label any confirmed faulty item so it cannot return to service accidentally.

Keep the working path current

Build the current stage plot, input list, and monitor plan in Techrider.live, then keep the corrected route in the Rider that the whole production uses. A repeatable test sequence plus one current document makes the next fault faster to isolate.