Building a multilingual translation booth with Power Core and Ruby
Australia's broadcasting landscape is one of the most linguistically diverse in the Asia-Pacific. SBS Radio has long delivered content in more than 60 languages, while community stations from Fairfield to Footscray serve diaspora audiences across Sydney and Melbourne. When a single studio needs to switch between English, Mandarin, Vietnamese, or Arabic without compromising audio quality, the underlying infrastructure has to be both flexible and resilient.
A modern translation booth built on Lawo's Power Core engine and Ruby mixing surface offers exactly that kind of dependability. Treating each language take as a routable stream on a shared network lets engineers in Brisbane or Perth configure booth presets, manage DSP resources, and hand control to remote interpreters using familiar software tools rather than purpose-built hardware.
Why IP routing underpins a flexible translation booth
Traditional analogue booths needed a separate console per dialect, each wired into a dedicated patch bay. IP-based radio consoles invert that relationship, letting a single Power Core host multiple independent mix buses that behave like separate consoles, each with its own processing chain and I/O.
This approach aligns with Broadcast 3.0 principles, where audio, control, and metadata travel together as network packets. An interpreter working into Tagalog in Parramatta can be routed to a different transmitter than a Cantonese commentator in Hurstville, all without repatching a single XLR.
A side-by-side comparison illustrates the difference for a four-language workload.
| Feature | Analogue booth stack | Power Core IP booth |
|---|---|---|
| Mixers required | 4 dedicated consoles | 1 Power Core (4 virtual buses) |
| Patch points | 96+ physical tie-lines | Network routing (AES67/ST 2110) |
| Booth footprint | Full rack per language | Half-rack, shared |
| Setup time per event | 2–3 hours | 15–20 minutes |
| Remote control | Hardware remote only | RƎLAY virtual surface + VisTool |
| Redundancy | Manual failover | Dual-network, hitless merge |
Power Core as the audio backbone
Power Core is the DSP engine doing the heavy lifting. With up to 96 DSP channels and front-panel I/O options for analogue, AES3, MADI, and Ravenna/AES67, it can ingest anything from studio microphones to feed circuits arriving via satellite.
For a translation booth handling the AFL Grand Final commentary in English, Pitjantjatjara, and Mandarin, an operator can dedicate specific channel strips to each talent. Every strip carries its own gate, compressor, and EQ, then sums into a separate programme bus. The same chassis driving the main on-air feed can simultaneously mix interpreter return audio, IFB, and mix-minus for the off-tube booth.
Hot-swappable power supplies and dual-network cards make the unit suited to Australian conditions, where regional broadcasters in places like Cairns or Broome sometimes run on a single fibre path. If the network drops, Power Core's AutoMix logic keeps levels consistent across languages without operator intervention.
Ruby console: tactile mixing without compromise
The Ruby surface gives interpreters and producers a familiar fader-per-source workflow. Its 40mm faders, OLED labels, and assignable rotary encoders make it easy for operators to manage four or six language feeds simultaneously, even under deadline pressure.
Because Ruby is network-aware, multiple consoles can be parked on the same Power Core. A senior producer in Adelaide can sit at one Ruby while an interpreter in a remote cupboard runs a thin client. The system's console-follows-mix philosophy means fader moves on one surface ripple across the others in real time. For parliamentary broadcasting from Canberra, where Hansard-style transcription happens live, that kind of multi-surface control proves its worth.
RƎLAY virtual radio tools for distributed booths
When interpreters cannot all be on-premises, RƎLAY software surfaces extend the booth into any laptop with a network connection. Each RƎLAY instance appears as a control client to Power Core, giving the remote operator talkback, fader access, and processing control.
This setup is particularly useful for community radio stations in Darwin or Hobart, where visiting language experts may only be available via the NBN or a commercial link. A Hmong commentator joining from a home studio can be patched into the same mix bus as on-site talent using identical tooling.
VisTool dashboards for remote monitoring
Operators rarely stay chained to the console, and the VisTool web dashboard allows engineers to monitor every translation booth from a tablet in the corridor or a workstation across the building. Custom screens can show language labels, channel meters, talkback status, and even GPIO states for red-light indicators.
For broadcasters covering events from the Sydney Cricket Ground to regional rodeo broadcasts in Tamworth, having a single pane of glass across all booths simplifies troubleshooting. Engineers can mute a hot mic, change a processing preset, or switch a feed from one Ruby surface to another without entering the studio. The VisTool web dashboard insights page walks through the screen-building workflow in detail.
Local realities shaping an Australian deployment
Compliance with ACMA technical standards, Australia's wide geography, and the quirks of the NBN all shape how these systems get rolled out. Studios in regional centres from Cairns to Broome often run with limited on-site engineering support, making remote diagnostics a working requirement rather than a convenience.
Multi-language events such as the AFL Grand Final or Test match coverage require pre-show talkback checks between each booth and master control, plus a documented fallback path. Hands-on rack support is hard to find outside the capital cities, which is why many Australian broadcasters partner with local integrators like Atomic Bands when shipping a mobile kit to a regional rodeo or a Test cricket venue.
Firmware drift across regional Power Core installs can create subtle AES67 compatibility gaps with older third-party gear. Reserve one hour this week to audit Power Core firmware across the fleet and confirm interoperability before the next major broadcast window.
