Talkback

A talkback microphone connects to a console input or a dedicated communication input. Its signal is assigned to the destinations that need instructions, such as stage wedges, in-ear mixes or a recording room headphone feed. A switch enables speech when needed, while routing keeps that speech away from audience loudspeakers and programme recordings unless deliberately required.

Dedicated console talkback functions may provide destination buttons, a level control and momentary or latching operation. Other systems build the same function using a spare channel and carefully configured sends. Neither arrangement is automatically private. The engineer must inspect every output assignment, including matrices, recording feeds and any channels that share the communication signal.

A momentary button passes speech only while held, which reduces the chance of leaving a microphone open. A latching button remains active until switched off and can suit longer discussions, but requires an unmistakable status indication. Some installations also support a return microphone, letting performers answer without repurposing a performance microphone or shouting across the venue.

Clear communication reduces uncertain starts, repeated instructions and avoidable interruptions. A performer who hears a concise request can identify an input, play a short passage or confirm a monitor change promptly. Without an agreed communication route, engineers may mistake an unheard request for a technical fault and start changing equipment that was already working correctly.

Talkback level deserves the same care as any other monitor source. Speech arriving unexpectedly in sealed earpieces can be startling, particularly if the input gain is excessive or the operator speaks very close to the microphone. Establish a comfortable level before musicians put their full attention on the performance, then keep microphone distance and speaking volume reasonably consistent.

The system also protects the production's working environment. Private instructions can stay separate from the audience presentation, and multiple crew positions can coordinate a check without competing with stage sound. This depends on verified signal flow, not the label printed beside a talkback button. An incorrectly assigned output can still make backstage discussion public.

Start by deciding who must hear whom. An engineer may need separate buttons for all performers, one particular musician and a technical crew feed. Avoid sending every instruction everywhere simply because the console permits it. Destination choice should reflect actual responsibilities, and people should know whether their reply will reach only the engineer or a wider group.

For wedge monitoring, an open talkback microphone can form an acoustic feedback loop if loudspeaker sound returns to it. Keep unnecessary sends off, position the microphone sensibly and release the switch after speaking. For in-ear monitors, feedback through that listening path is less likely, but excessive speech level remains a concern and other open loudspeakers may still create a loop.

Check how talkback interacts with console mutes, solo functions and scene recall. A show file might recall different output assignments or levels partway through a production. If communication settings are intended to remain constant, use the console's appropriate recall protection after testing it. Do not assume a channel mute will affect every send, especially where pre-fader routing or dedicated communication buses are involved.

At a Dubai rehearsal for a small live band, the front-of-house engineer needs to request individual instruments while the musicians listen through separate monitor mixes. Before the rehearsal begins, the engineer assigns the communication microphone to those mixes, excludes the main output and asks each musician to confirm that speech is comfortable and intelligible.

The engineer first speaks to the drummer alone, requests a short kick pattern and releases the button before listening critically. Next, an all-band instruction announces that the vocal check will start. This makes the sequence understandable without keeping a microphone open over the entire rehearsal. A musician's normal vocal microphone provides a reply when needed, with its routing understood by everyone.

A second crew member listens at the audience position while another checks the recording feed. They confirm that neither carries the instructions. After loading the next console scene, the engineer repeats a brief communication test, because the stored routing could differ. The useful result is a predictable working process, not simply an illuminated talkback button or movement on a meter.

• Treating talkback as automatically private can expose instructions or conversation on a stream, recording or audience output. Verify destinations by listening, not by relying on channel names.
• Leaving a latching switch enabled can add room noise and unexpected comments to performer monitoring. Make the active state obvious and close the route when finished.
• Raising microphone gain instead of checking a quiet destination may create excessive level in other mixes. Establish the input first, then balance each destination deliberately.
• Giving long instructions during a loud musical passage makes communication harder. Wait for a suitable pause and use brief, specific requests that identify the intended recipient.
• Sending communication through unnecessary effects can reduce intelligibility. A dry speech route is usually more useful than a reverberant or heavily processed voice.

Include communication checks in the soundcheck plan rather than improvising them after problems develop. Agree on simple verbal cues, leave a reliable means of reply and explain any limitations to the musicians. If a route behaves unexpectedly, stop using it until the destination and level have been verified.