Backing Tracks to the PA, Click to the Band: A Routing Checklist

Why the click ends up in the PA

Running backing tracks with a click seems simple until the first show where the audience hears a faint tick under a quiet intro. The goal is easy to state: route the backing tracks and the click to separate outputs so the audience gets the tracks and only the players hear the click. In practice the click can leak through software routing, a console bus, a shared headphone feed, or a patching mistake made in a hurry at an unfamiliar venue.

Community threads show this is a recurring planning question. In one Reddit thread, an anecdote rather than a survey, a band playing from a Mac asked how to get separate audience and monitor feeds, and replies compared mono tracks plus click with a stereo arrangement on more outputs [R1]. In another, a four-piece band wanted stereo tracks in the PA and the click only in headphones but owned a two-output interface [R2]. Both point to the same lesson: routing decisions start with hardware limits, not software settings.

Count independent outputs, not sockets

Before touching software, list every output your interface can address separately. An independent output is one your software can feed without that signal also appearing elsewhere. Many compact interfaces have a headphone socket that mirrors the main outputs or blends them with inputs. That socket is another way to hear the same signal, not an extra output. Counting it twice can lead you to plan a click feed that is really a copy of the main mix.

Check the current manual for your exact model and firmware, looking at how it describes headphone sources and output pairs. If it is unclear, ask the manufacturer whether the headphone feed can carry a signal absent from the main outputs, and write the answer down. Your whole plan depends on that number.

• Count line outputs your software lists by number, not jacks on the chassis
• Note whether the headphone output mirrors outputs 1-2 or can be assigned separately
• Count digital outputs only if you own a device that can receive them

Mono backing plus click, or stereo backing with a dedicated click

With exactly two independent outputs, the usual option is backing tracks summed to mono on one output and the click alone on the other. You lose stereo width, and anything panned in your stems, such as a pad moving left to right, will sit in the center. In exchange, the house engineer gets one simple backing channel to manage.

With four or more outputs, you can send stereo backing on one pair and the click on a third, sometimes with a fourth carrying spoken cues. This is the kind of multi-output arrangement the Reddit replies set against mono-plus-click [R1]. The tradeoffs are more channels for the venue to patch, more cables that can fail, and possibly an interface purchase. For a band in the two-output position described in [R2], the realistic choices are accept mono or buy more outputs. No software setting creates hardware that is not there.

Keep the click off the main bus, in software and at the console

Panning the click hard to one side of a stereo pair is not isolation. If anything downstream sums that pair to mono, whether a DI, a console channel or the PA processor, the click reaches the audience. Adjacent lines in a shared cable or multicore can also carry some crosstalk. The safer approach is a click destination that is never assigned to the main bus.

Separate two kinds of click. If your click is an audio file on its own track, Ableton's manual describes setting a track's Audio To chooser to Ext. Out and enabling hardware ports as mono outputs or stereo pairs in Channel Configuration [S1], so you can confirm the click track goes to one specific port. If you use Live's built-in metronome instead, it follows the program's cue routing rather than a track's Audio To setting, so check in the current manual where that cue output goes and deliberately point it at the monitor-only port. Then make sure browser or clip previews that also use the cue path cannot surprise performers mid-song. Other playback programs use different names, so verify in your own software's current manual.

• Audio click track assigned to one dedicated monitor-only port
• Built-in metronome, if used, reaching that same port through its cue routing on purpose
• Master output and backing tracks never assigned to the click port
• No sends from the click into reverb or delay returns that feed the backing outputs
• At the console, the click channel feeding monitor mixes only, unassigned from the main bus

Label everything the same way across every song

Inconsistent naming causes many show-night errors. If output 3 is the click in one song and keys in another, eventually the wrong signal goes to the PA. Keep the same output assignments for the whole set, name tracks in the session, label both ends of every cable, and use matching names on console scribble strips or channel tape.

Short labels such as TRK L, TRK R, CLICK and CUE work well when used identically in the session, on cables, on DI boxes and on the printed map. A venue engineer who reads CLICK should know at once that it feeds monitors only.

Test every song and transition on the real stage equipment

Headphone checks at home only prove your software routing. The real test runs through the actual PA, monitors and cables. Play a click-only section with the console set exactly as it will be for the show, the click still excluded from the main bus, and backing outputs muted at the source. Then listen at the mix position and in the room, and watch the main output meters. Any click there means a leak. Avoid using solo-in-place for this check, because it can change what the main outputs carry. Headphone or PFL solo is useful separately, to confirm a channel has signal, but it does not show whether the click reaches the PA.

Next, unmute the backing and play through every song and transition, listening closely to count-ins, quiet passages and endings. Sessions that change tempo or trigger different track groups can expose one song built differently from the rest. If you hear a tick, keep going: check console assignments, cables, and acoustic spill from loud wedges or open-back headphones near microphones.

A printed output map and a failure drill

Bring a one-page map listing each interface output, its label, connector type, whether it needs a DI, and its destination, such as main mix or monitors only, plus a band contact for show time. Venue staff can patch from a clear sheet quickly, and it discourages a well-meaning engineer from pushing your click into the mains to check the channel.

Then demonstrate what stops and what continues if the computer crashes, the interface loses power or a USB cable comes loose. Decide whether the band keeps playing, restarts or skips ahead, and rehearse it. Know whether the room hears a pop or silence and whether the drummer loses the click, and tell the engineer which faders to pull. Hum, buzzing or shocks from equipment belong to venue staff or a qualified electrician, never to band improvisation.

Hypothetical worked example

Hypothetical example, not a real band or test result. A four-piece owns an interface with two line outputs and a headphone socket and plans to put the click in the headphone jack. The manual shows that socket mirrors outputs 1 and 2, so the click would reach the PA. For their next gigs they send mono backing on output 1 and the click on output 2, patched only to the drummer's monitor mix.

Later they buy a four-output interface: TRK L and TRK R on outputs 1-2, CLICK on 3, CUE on 4, confirmed through each track's Audio To setting and Channel Configuration [S1], with the cue path checked separately. At soundcheck they play a click-only passage with the console in show configuration and hear nothing in the room or on the main meters. During a ballad they still hear a faint tick, traced to spill from the drummer's open-back headphones and solved with closed-back models.

Red flags, verification and when to escalate

Be wary of marketing that counts every jack as an output, advice that hard panning is enough isolation, and any claim, including forum anecdotes, that a setup can never leak. Forum answers describe someone else's gear [R1][R2]. Verify output counts and headphone behavior in the manufacturer's documentation, confirm routing in your current software manual, and confirm the result by ear in the room.

Escalate when your own checks cannot find the source. Ask the venue engineer to review console assignments and multicore crosstalk, contact the interface manufacturer if outputs behave differently from the manual, and leave power or grounding problems to venue staff or a qualified electrician. Do not open equipment or modify power yourself.