Scaling Ruby Productions with Power Core
A Ruby console can give a radio studio a clear, efficient operating surface, yet larger productions quickly bring more sources into the mix. Multiple studios, remote feeds, automation returns, codecs, telephone hybrids and outside broadcasts can all compete for available channels.
Power Core extends that working capacity through a networked audio architecture. Instead of treating the console as a self-contained mixing box, broadcasters can place processing, routing and I/O where the production needs them, while keeping control available from Ruby.
This approach suits Australian broadcasting, where a network may combine metropolitan studios in Sydney or Melbourne with regional facilities in Queensland, Western Australia or remote locations. It also supports the practical realities of outside broadcasts, long contribution paths and lean technical teams.
The result is a more adaptable channel-count strategy. Broadcasters can add sources and production areas without redesigning the entire control room, provided the system is planned around signal flow, DSP resources and operator requirements.
Why channel count becomes a production issue
A small studio may need only microphones, playout, a few remote codecs and monitoring paths. A larger broadcast production can require separate feeds for presenters, guests, producers, newsroom returns, music beds, commercial playback, clean feeds and communications.
Sports and major live events increase the pressure. An AFL or NRL broadcast may combine venue microphones, commentator positions, remote interviews and studio inserts. A music or cultural event in Brisbane, Perth or Adelaide can require additional submixes and feeds for broadcast, streaming and venue coordination.
Ruby provides the operator-facing control, while Power Core supplies a scalable processing environment behind it. This division helps keep the surface focused on the sources and buses that matter during a live shift.
How Power Core extends Ruby
Power Core functions as a networked audio engine and I/O platform, supporting routing, mixing, processing and connectivity across a Lawo-based environment. Audio can be distributed over standards-based IP networks, including RAVENNA and AES67 workflows, rather than being tied to a single rack or console frame.
For Ruby users, the practical benefit is access to additional DSP channels and signal paths without filling the desk with every physical input. Power Core can handle sources that are shared across rooms, while Ruby presents the controls needed for the current programme.
This model also separates capacity from location. A Power Core unit can serve a main studio, a backup room, a voice booth and an outside-broadcast position through the network, subject to the system design and licensing configuration.
Designing the networked signal flow
A successful expansion begins with a source inventory. List microphones, playout systems, codecs, studio-to-studio links, phone systems, newsroom feeds, monitoring destinations and transmission outputs. Mark which signals need processing, which need simple routing and which must be available in more than one room.
Australian stations often need to connect city-based production with regional contributors and remote presenters. A networked design can make those sources available without repeatedly repatching local hardware, while appropriate redundancy and managed network infrastructure help protect day-to-day operations.
Power Core can also support a cleaner division between production layers. For example, one area can handle microphone pre-processing and mix-minus feeds, Ruby can manage the live presenter mix, and another set of outputs can feed streaming, recording or a station’s transmission chain.
Matching capacity to the workflow
Channel-count planning should account for buses, monitor paths, mix-minus feeds and backup sources, rather than counting microphones alone. A production with 24 microphones may need many more active paths once cue sends, clean feeds and contributor returns are included.
| Production requirement | Ruby control role | Power Core contribution |
|---|---|---|
| Main studio mix | Faders, layers and bus control | DSP channels, routing and processing |
| Remote contributors | Source selection and mix-minus control | Codec interfaces and return paths |
| Outside broadcast | Fast access to event sources | Networked I/O and shared processing |
| Streaming and recording | Output and monitor management | Additional buses and feed distribution |
| Backup operation | Access to essential controls | Redundant or alternative signal paths |
Leave spare capacity for seasonal and occasional work. A station that covers the Melbourne Cup, election night or a large concert will need more flexibility than its everyday breakfast show suggests.
It is also sensible to separate permanent sources from temporary ones. Fixed studio microphones and playout systems can have stable routing, while Power Core resources and network inputs can be assigned to pop-up productions as required.
Keeping operators in control
More channels should not mean a cluttered operating experience. Ruby’s surface can be organised into layers and views so that presenters, producers and technical operators see the controls relevant to their role. Frequently used sources can remain immediately accessible, while less common feeds stay available without consuming physical space.
This matters in fast Australian radio environments, where a small team may move from breakfast programming to a live cross, a news update and an outside broadcast in the same shift. Clear naming, colour conventions and consistent bus layouts reduce mistakes when time is tight.
VisTool can complement the physical surface by providing graphical control of routing and system functions. That can be useful for a producer’s position, a technical area or a backup workstation, particularly when the main Ruby surface is busy with live mixing.
Supporting complex live productions
Larger productions often depend on many wireless microphones, talkback feeds and changing contributor combinations. A networked Power Core and Ruby setup can provide the processing and routing needed to manage those sources while preserving straightforward control for the operator. Lawo’s discussion of wireless microphone control is especially relevant to productions where several voices must remain intelligible.
AutoMix can assist in applications where multiple microphones need consistent speech balance, including drama, theatre and certain live broadcast formats. The operator can retain overall editorial control while automated assistance reduces the need to ride every open microphone continuously.
For radio, the same design principles apply to panel discussions, outside broadcasts and hybrid studio events. A station can build dedicated mixes for transmission, online streaming, venue sound and recording without forcing every destination to share the same balance.
Building an expansion path
A practical deployment normally starts with the most immediate capacity problem. That could be extra studio inputs, more remote contribution paths or a second production room. Once the network, naming scheme and routing approach are established, additional Power Core resources can be introduced with less disruption.
Document signal ownership and failure behaviour before going live. Operators should know which sources remain available if a network path, workstation or console surface becomes unavailable. Technical staff should also test clocking, latency, monitoring and mix-minus performance under realistic load.
For broadcasters across Australia, this matters because facilities may need to serve metropolitan audiences, regional stations and temporary event locations from the same core infrastructure. Power Core gives Ruby a way to grow with those demands while keeping daily operation familiar.
The key point is simple: Ruby provides the hands-on control, while Power Core expands the processing, routing and connectivity behind it. When channel capacity is planned around complete production paths rather than fader numbers alone, larger broadcasts become easier to manage, adapt and support.
