Building A Multitrack Recording Setup With Ruby And Power Core
A multitrack recording system built around Lawo Ruby and Power Core can give radio stations, production houses and live teams a flexible way to capture separate sources without creating a maze of analogue cabling. Ruby provides the operator-facing mixing environment, while Power Core supplies networked audio processing, routing and I/O resources.
The result is a setup that can serve several purposes: recording interviews in a Sydney studio, producing voiceovers in Melbourne, capturing a live music session or preparing content for a regional broadcaster. The key is to design the signal path before connecting equipment, then decide which functions belong in the console, the audio node or the recording workstation.
| Component | Primary Role | Best Use In A Multitrack Setup |
|---|---|---|
| Ruby console | Mixing, monitoring and operator control | Live contribution, studio production and mix-minus |
| Power Core | Networked DSP, routing and audio I/O | Source management, processing and scalable connectivity |
| VisTool | Custom graphical control | Remote operation and simplified user interfaces |
| DAW | File recording and editing | Isolated tracks, overdubs, editing and mastering |
| AoIP network | Transport between devices | Flexible routing across studios and technical areas |
Define The Recording Objective
Start by identifying whether the project requires isolated microphone tracks, a stereo programme mix, or both. A radio interview may need separate host, guest and remote contributor channels, while a live acoustic session could require individual vocal, guitar, percussion and ambience tracks.
Ruby can handle the operator’s monitoring and balance decisions, but the recording workstation should receive clean, clearly named sources. This allows an editor to revise levels later without being locked into the live mix. Keep a separate stereo mix for fast publishing, alongside the multitrack files for detailed post-production.
Build The Signal Path
A practical path might run from microphones and line sources into Power Core, through input processing and routing, then to Ruby for control and monitoring. Direct outputs or dedicated network sends can feed the DAW, while return channels from the workstation come back through the same audio infrastructure for playback and review.
This arrangement reduces dependence on point-to-point wiring. A producer can monitor the live mix, an engineer can check isolated tracks, and a presenter can hear a controlled headphone feed. Before recording, label every source according to its role rather than its physical socket, using names such as “Studio A Host” or “Guest Return”.
Plan Networked Audio Carefully
Power Core is most useful when the network is treated as part of the audio system rather than as ordinary office infrastructure. Use managed switches, documented port assignments and a clear approach to redundancy. Clocking, multicast behaviour and network capacity should be tested before the first production day.
Australian facilities often span long distances between studios, control rooms and technical racks. A broadcaster in Brisbane may need a centralised workflow serving rooms in Sydney or Perth, while a regional station may have limited engineering support on site. A documented network design makes troubleshooting faster when staff are working across different time zones.
Configure Ruby For Operator Speed
The Ruby surface should make common actions immediate: source selection, talkback, monitoring changes, headphone feeds and recording start points. Avoid forcing an operator to navigate several layers for routine tasks. A well-organised layout is especially valuable during fast-paced breakfast radio, outside broadcasts or live sport coverage.
Use Ruby’s flexibility to create distinct operating profiles for interviews, music sessions and voice production. A presenter might need a simple fader arrangement, while an engineer recording a band requires more visible input channels and monitor controls. Consistent colour conventions and channel naming help casual users work safely.
Separate Monitoring From Recording
Monitoring and recording should be designed as related but independent paths. The presenter needs confidence that the programme sounds correct, while the engineer needs access to pre-fade or otherwise suitable isolated signals. If every recording channel follows the final fader mix, later editing becomes unnecessarily restrictive.
Create dedicated headphone mixes for talent, guests and the control room. Include talkback where required, but prevent open microphones from feeding unintended destinations. In a multi-room facility, test what happens when a source is muted, a return channel is lost or the DAW stops responding.
Integrate The DAW And Control Layer
The DAW should receive stable, predictable channels from Power Core, with sample rate and clocking agreed across the system. Name tracks before the session begins, prepare a template, and include a safety stereo recording if storage and workflow allow. This is faster and more reliable than building a project while guests are waiting.
VisTool can provide tailored screens for transport control, routing status or simplified production tasks. That can be useful in a university station, a community broadcaster or a remote Australian bureau where the person operating the room may not be a full-time audio specialist. The broader value of a configurable workflow is reflected in this production workflow case study, where operational design is central to making complex activity manageable.
Prepare For Live And Remote Sources
A multitrack setup should accommodate more than local microphones. Radio teams may combine studio contributors, codec feeds, mobile reporters and remote guests. Power Core and Ruby can help organise these sources into consistent processing and monitoring paths, while the DAW preserves individual material for later editing.
For an outside broadcast at a Melbourne arts venue or a regional music festival near Newcastle, plan for uncertain connectivity and changing source counts. Keep spare inputs, verify headphone distribution, and create a fallback recording path. Australian power, venue access and weather conditions can affect setup time, so a tested scene and a compact backup plan have practical value.
Test, Document And Scale
Run a complete rehearsal using the same microphones, network paths and software versions intended for production. Confirm that every isolated track records correctly, that playback returns to the expected monitor path and that talkback does not leak into programme files. Check file storage, naming conventions and backup destinations as part of the soundcheck.
Once the basic system is reliable, it can expand with additional Ruby positions, Power Core resources, remote control panels or more recording rooms. Keep a current signal-flow diagram beside the technical rack and record any changes after commissioning. The practical takeaway is simple: define the tracks first, route them deliberately through Power Core, make Ruby fast to operate, and test the complete recording chain before going live.
