A shared broadcast rack for Australian radio

Designing a multi-station rack with Power Core and Ruby for a shared broadcast facility starts by treating it as a service for several stations, not one oversized desk. It may feed community radio in Brisbane, a metropolitan network in Sydney and a music programme made in Melbourne, yet each output needs clean boundaries and a known recovery state.

Power Core nodes gather physical and networked sources into a routing core, while Ruby and VisTool provide tactile and visual control within Lawo's Broadcast 3.0 ecosystem. The brief should cover live, recorded, remote and maintenance scenarios, including one station on air while another is serviced. Labels, documentation and recovery moves matter as much as the signal diagram for relief operators.

Start with the room and workflow

Australian conditions shape the room. Brisbane brings humidity and summer heat, Melbourne can swing sharply through the day, and regional sites may wait long for specialists or parts. Allow cooling, filtration, strain relief and clear airflow suited to the site. Show power, fibre entry and local playback equipment on both architectural and signal drawings.

Plan normal production, partial failure and full recovery separately. Partial failure could lose one output card, network path or intercom zone; full recovery must return the facility to a safe baseline. A fair dinkum crew rule is that no bypass relies on memory. If an engineer calls it “no worries”, handover still needs the route, time and owner.

Map every signal path

Begin with a source matrix, not an equipment list: microphones, playback, remote contribution, news feeds, timecode, talkback and monitoring returns. On Power Core, assign deliberate ingress and egress for Ravenna/AES67, MADI and other connections in use, then give each station independent contribution and programme routing. Shared converters must not silence three unrelated shows.

Keep production, programme, confidence, cue and intercom paths visibly separate. Each station needs its own mute, master and mix-minus. Reserve real card space, fibre ports, power and cooling for expansion; “room for later” is not a spare. Label patch points in plain English, with colour as a secondary cue.

Separate control, clock and content

VisTool can provide approved control and status views on authorised workstations, while RƎLAY virtual radio tools can extend radio functions into the browser. Separate media, control and management traffic, authenticate accounts and document addresses so a replacement workstation can be configured without dismantling the rack. Administrators should know which controls can affect an on-air feed.

Define the clock hierarchy. Distribute house reference and word-clock signals where required, ensure network devices follow the facility master and stop a convenience source resetting production gear. Store automation in UTC but display local time; Australian daylight-saving changes must alter displays without shifting scheduled programme. Keep one naming standard, since “the morning show mic” is ambiguous on a shared desk.

Design for failure and tired crews

Model failures plainly: a node disappears, a switch reboots, a studio loses mains or an operator selects the wrong input. Local mix-minus and per-station power can keep unaffected outlets stable; software should return to a documented scene, not an old one. Critical routes need a tested bypass. In regional locations, local spares and clear remote support can be worth more than redundant equipment nobody can service quickly.

Resilience includes people on overnight shifts. Breaks, handover notes and a quiet space reduce mistakes. If a presenter develops tremor or anxiety, an occupational-health clinician or pharmacist should guide treatment; propranolol patient information can support that discussion, but cannot replace medical advice. Fatigue and wellbeing should be managed as operational controls, not dismissed with “she'll be right”.

Build monitoring people trust

Give engineers confidence monitoring without giving presenters a route to contaminate programme. Separate confidence feeds from the broadcast master, meter before and after processing, and prioritise host loudspeakers, headphone splits and cue speakers. Calibrate reference monitors to a common target. Agree loudness and true-peak specifications for each service, since radio, streams and interviews can differ.

Give talkback clear permissions. A host may cue a guest, while an operator may need emergency override; they should not share one unrestricted button. Test talkback into every studio and remote box, including with closed doors and active microphones. Logs should identify who made an override, turning routine corrections into controlled operations rather than public arguments.

Automate with restraint

Automation should remove repetitive work that distracts from content. Lawo's AutoMix podcast workflow shows how automatic microphone handling can streamline multi-microphone recordings, a useful pattern for panel shows and community production. Apply it only to defined speech sources, with a bypass for live interviews, music cues and feeds needing stable dynamics.

Scene recalls, automatic mutes, clip starts and level assists need visible state and manual override. For Ruby, store broadcast, rehearsal and emergency positions rather than a snapshot for every fader combination. Prevent automation from changing another station's channels. Record recalls and failures, then rehearse manual recovery until an operator can use it without help pages.

Buy for support as well as features

Australian buyers often work with local integrators, distributors and service technicians across community and commercial stations, ABC facilities and regional operators. Compare lifecycle support, training, spare parts and response times rather than hardware price alone. Import lead times, currency movement and warranty terms reshape budgets, while volunteer-run community stations need simple operation and remote support that does not assume a resident engineer.

Shared rooms may house stations with different editorial and advertising controls. A blackjack bonus strategy, for example, may be reference material for a gaming item, but it has no place in routing or monitoring design; legal review stays separate from engineering acceptance. Test the finished system against the brief: signal paths, failover, talkback, sync, noise, latency and operator recovery. Hand over labelled diagrams, settings and known limitations.

The shared rack should remain understandable under pressure: centralised where that saves time, isolated where stations need independence, and documented so a relief engineer can recover the show without guesswork. The essential choice is not that Power Core and Ruby provide capable components, but that every route, permission and failure response has an owner the next person can verify.