Ruby headphone feeds without signal-flow guesswork
A radio desk can look simple from the doorway: microphones, a few faders and two pairs of headphones. In a busy show, the presenter may need a clean microphone cue, the producer needs a stereo confidence feed, and the engineer may need a remote return or mix-minus bus without changing what the audience hears. A single shared monitor mix becomes a bottleneck as soon as several voices and locations are involved.
For complex headphone feeds, Ruby’s internal audio routing matrix turns those listening jobs into separate, software-defined paths. It can assign internal sources to the headphone buses an operator actually needs while leaving the programme mix independent. The practical benefit is consistent monitoring, fewer accidental level moves and a quicker handover between local content, network programming and live coverage.
Build the monitoring map
Start with the listening task rather than an output number. List who needs to hear the clean mic, full programme, remote contribution, talkback or a talkback return, then give each job a named destination. Ruby’s matrix is an internal routing layer; it does not remove the need for correct gain structure, physical patching or a properly configured studio intercom. Its value is that the assignments become repeatable instead of being improvised with spare outputs.
Australian control rooms often use familiar verbal cues such as “take a listen” or “give us a level”. In a Melbourne studio, for example, a host can hear a local bulletin while the producer checks the network return, and a second operator can monitor the talkback path without moving the host’s feed. Names such as Presenter Cue, Producer Confidence, Guest Foldback and Remote Return make those decisions visible during a fast changeover.
Route sources with intention
Choose the point in the signal chain that matches the purpose. A clean source feed is useful for judging articulation and mic technique; a programme or confidence feed answers “what is going to air?”; a decoded return answers whether the remote contribution is intelligible. Route these as distinct matrix sources where possible, rather than raising a common stereo mix and hoping the unwanted material disappears.
Talkback needs a separate plan. A mix-minus bus should exclude the destination microphone, and an operator’s talkback should reach only the intended headphone or studio destination. Keep presenter cues, guest returns and alternate confidence feeds distinguishable, especially when a show moves from a network voice in Sydney to a local voice in a regional centre. That concern is not unique to radio: a Ukrainian television discussion of resilient broadcast operations reinforces the value of a dependable alternate path when a contribution or outgoing feed changes.
Keep levels and talkback controlled
Monitoring should reveal the programme, not introduce a second set of level problems. Set source trim and headphone gain in a deliberate order, check headroom for a loud cough or an interview surprise, and make sure the confidence feed is taken from the point that represents the on-air signal. Keep processing, dimming and solo decisions inside the monitor path so they do not silently alter the broadcast mix.
Talkback is the classic feedback trap, so label both ends of the conversation: who is being addressed, which microphone must be excluded, and where the return is going. A practical comparison clarifies the common choices:
| Listening need | Useful matrix assignment | Result |
|---|---|---|
| Presenter cue | Clean source to a dedicated headphone bus | The host hears detail without changing the main fader |
| Confidence | Stereo programme to a separate monitor destination | The producer hears the audience-facing mix |
| Guest return | Mix-minus or decoded return to a named bus | The guest hears the intended mix without a talkback loop |
| Engineer check | Remote or talkback source to a controlled output | Faults can be isolated without disturbing the desk |
For an Australian station combining network audio with local bulletins, advertising and sport, this separation makes a live handover less fragile. When an AFL feed in Melbourne or a cricket feed in Brisbane has to give way to local continuity material, the operator can switch listening assignments while keeping the talkback relationship intact. ACMA-regulated broadcasters still depend on a stable on-air path, so the fallback route should be treated as part of normal show preparation.
Connect the wider broadcast system
Ruby’s monitor choices work best when they agree with the wider Broadcast 3.0 workflow. VisTool can provide the control view, Power Core nodes can carry the audio between studios, and RƎLAY or AutoMix can support the virtual-radio functions around the desk. The matrix then remains the place where an operator’s listening assignment is defined, while the underlying signal travels through the configured studio and IP infrastructure.
Older equipment does not have to force a return to manual patching. Lawo’s AES3-to-IP gateway explains how Broadcast 3.0 can connect legacy AES3 devices to IP, which is useful when a Ruby monitor path must reach a recorder, codec or loudspeaker system in an existing rack. The routing decision stays in Ruby; the transport layer handles the bridge.
Document who can change each destination and what the normal, alternate and emergency states look like. That discipline matters across Australia’s time zones, where a producer in Sydney may be preparing a handover for a regional presenter while the network feed is already running. Clear route names and a simple cue sheet reduce dependence on whoever happens to be at the desk.
Rehearse the real Australian workflow
A useful rehearsal is not a generic check of every fader. Recreate the actual chain: network programme from Sydney or Melbourne, a local microphone, a guest return, talkback and the confidence feed used for an advertising break. Include an AFL or cricket venue scenario if the station covers live sport, and let the presenter or producer use the same Australian wording they use during a real shift. The test is whether each person hears the intended source without asking for a higher common level.
Then change one condition at a time. Remove the remote return, mute a network feed, lose a headphone channel or place the programme in alternate continuity; confirm that the fallback feed, talkback exclusion and on-air confidence remain usable. Record the final assignments in the desk documentation and review them after any studio change. Every dependable headphone feed is a named, level-controlled and rehearsed signal path, not an improvised collection of monitor outputs.
