Line check

The crew works through the patch in a known order, activating one source at a time. A technician speaks into a microphone, plays an instrument or requests a representative signal from playback. The engineer confirms that the expected channel receives it, checks for obvious noise or distortion and acknowledges the result. The aim is positive identification, not simply seeing meters move somewhere on the console.

The input list provides the reference for channel number, source name, connector position and any special requirements. A useful check distinguishes a missing source from a mispatched source. If the snare microphone appears on the overhead channel, the signal exists but the patch is still wrong. Correct the physical or console assignment and update the documentation before moving on, rather than relying on memory.

Gain should be sufficient to assess the signal safely, with room for louder performance later. Required phantom power, pads and input modes must be checked deliberately. Keep unnecessary output paths muted while establishing inputs. A line check may include monitor and system returns, but those should be tested as named destinations at controlled levels rather than sending every active source everywhere at once.

A missing cable is much easier to diagnose before several musicians play together. A line check separates infrastructure faults from musical decisions, preserving rehearsal time for performers. It also catches wrong channel labels, unexpected stereo reversal and accidental connections to spare sockets. Without this foundation, an engineer can spend time equalizing the wrong microphone or adjusting a monitor send from a channel that contains a different instrument.

The process reduces uncertainty during changeovers. A replacement microphone may connect to the correct stage socket yet arrive on an unexpected console channel because the scene patch changed. Checking the actual source through the active route reveals that mismatch. A successful line check is still not a promise of show readiness: movement, full performance level and combined sources can expose problems absent from a brief isolated test.

1. Confirm the current patch revision, active console scene and person responsible for calling the check.
2. Ask for one identified source, then verify its expected input meter and channel label before listening through an appropriate monitoring path.
3. Assess basic level, unwanted hum, crackle, distortion and any source-specific requirement such as phantom power or a DI connection.
4. Check stereo sources on both sides, identifying left and right independently instead of assuming that one working side proves the pair.
5. Verify essential output destinations separately, acknowledge completed checks and keep an explicit list of unresolved faults.

Use communication that cannot be confused with a request to unmute the whole system. Calling a channel number and source name together helps when the stage technician and console engineer use different reference points. For example, a request for the stage-right vocal at input seven identifies both the position and patch. A clear acknowledgment closes the loop so the technician knows when to move to the next source.

When a signal is absent, trace signal flow in stages: source operation, local cable, interface, stage input, transport, console patch and monitoring route. Check the simplest likely cause first without changing several variables simultaneously. A healthy input meter with silent headphones suggests a different fault from no signal at the preamp. Document the point at which the signal disappears before substituting equipment.

Before a Dubai corporate event, a band shares the system with lectern speech and video playback. The engineer keeps audience outputs muted while a technician checks the stage sources. Two vocal microphones pass immediately, but the acoustic guitar produces no meter activity. The technician confirms the instrument output, checks the DI power requirements and discovers a local cable plugged into the wrong stage socket.

After correcting the socket, the engineer confirms the guitar channel, listens for a clean signal and marks it complete. Playback is checked next using content that identifies both stereo sides, followed by the lectern microphone at a realistic speaking distance. The crew then tests each required output at a modest level, ensuring speech is not accidentally routed into an unwanted backstage feed.

Only then does the band begin a representative passage for soundcheck. The engineer can now focus on musical balance, stage monitoring and system behavior instead of finding basic patch errors. The unresolved-items list remains visible until every issue is either corrected or explicitly covered by an agreed alternative. A checked box should mean a verified path, not an assumption based on yesterday's setup.

• Testing with several sources active makes it difficult to identify crossed channels and can hide a missing microphone behind nearby spill.
• Tapping a microphone aggressively can create large transients without representing real speech or musical performance. Use a controlled voice or appropriate source test.
• Declaring a channel healthy from meter activity alone misses distortion, wiring noise and the possibility that the wrong source is arriving.
• Changing gain while an unexpected output remains open can send startling levels to performers or listeners.
• Treating line check as a full rehearsal overlooks monitor balance, feedback margin and musical dynamics that require a representative performance.

Repeat the relevant checks after meaningful changes. A swapped DI, moved cable or newly recalled patch can invalidate an earlier result. This does not require restarting the entire event preparation every time; identify the affected route and verify it again. Keep performers informed so an efficient technical check does not become an unexplained delay at the moment they are ready to play.