Mounting Ruby in a Custom Flight Case for Touring Live Broadcast Events
A Ruby mixing console can become the operational centre of a touring broadcast package, but transport-ready installation requires more than placing the surface inside a rugged box. The case must protect faders, screens, connectors and network equipment while allowing a crew to deploy the system quickly at venues across Australia.
A well-designed flight case also needs to support Lawo’s wider software-based workflow. Ruby can work alongside Power Core audio nodes, VisTool interfaces, RƎLAY virtual radio tools and AutoMix, so the case should be planned as a compact control environment rather than a container for a single console.
| Design area | Touring requirement | Practical target |
|---|---|---|
| Console protection | Shock, vibration and impact resistance | Closed-cell foam and isolated mounting |
| Connectivity | Fast setup with repeatable patching | Rear panel with labelled EtherCON, XLR and power connectors |
| Thermal management | Reliable operation in warm venues | Ventilation path with filtered intake |
| Power | Safe distribution for Australian venues | Protected power inlet, RCD strategy and compliant cabling |
| Serviceability | Rapid fault finding between shows | Removable rear panel and accessible cable loom |
| Transport | Manageable weight and handling | Reinforced casters, handles and balanced loading |
Start With The Touring Workflow
Before measuring the Ruby frame, document how the system will be used at a live broadcast. A radio outside broadcast may need microphone inputs, commentator positions, mix-minus feeds, IFB, codec returns and a clean programme output. A concert or theatre production may require more monitor paths, scene changes and integration with a venue network.
List every connection that must remain available during operation. Power Core can place processing and I/O closer to the sources, reducing the number of analogue lines that need to travel back to the console. VisTool can provide an additional control surface for less frequently adjusted functions, while RƎLAY may handle remote or virtualised radio tasks away from the physical desk.
The case footprint should reflect the crew’s working habits. A small panel for talkback, monitor selection and essential GPIO can prevent operators from opening the case during a live segment. Keep frequently used controls visible, and reserve internal space for network switches, power distribution and labelled spare cables.
Build Around Isolation And Access
Use a robust plywood or composite flight-case shell with aluminium edging, recessed hardware and butterfly latches. The Ruby surface should sit on an isolated support frame rather than directly on the case base. Closed-cell foam, elastomer mounts or an engineered floating tray can reduce shock transmission during road freight between Sydney, Melbourne, Brisbane and regional venues.
Avoid compressing the console against the lid. Allow clearance around faders, displays and ventilation points, and use a removable lid that can be stored safely while the show is running. If the lid becomes a work surface, add a separate protective layer so dust, coffee and loose hardware cannot reach the controls.
Rear access is equally important. A removable connector panel can carry labelled network, audio, GPIO and power connections, while the Ruby remains fixed in its operating position. Use service loops inside the case so a connector can be replaced without dismantling the entire loom. Every cable should be marked at both ends with durable labels that remain readable under low stage lighting.
Plan Power And Network Redundancy
Australian venues commonly provide 230–240 V, 50 Hz power, but available outlets, earthing arrangements and distribution quality can vary. Touring equipment should use compliant power distribution, suitable circuit protection and an appropriate residual-current protection strategy. Electrical work and event operations must also align with the relevant state or territory requirements, along with workplace health and safety duties for the crew.
Separate mains wiring from audio and network cables wherever possible. A dedicated internal power compartment, strain relief and covered terminals reduce accidental contact and help control electromagnetic interference. Include a power inlet that can be locked or recessed, plus a clearly marked isolation switch if the design and local compliance review permit one.
Power Core and Ruby depend on dependable network infrastructure, so use a managed switch with labelled ports and a documented configuration. Consider redundant links where the system design supports them, and keep a tested spare switch or fibre converter in the touring inventory. The network should be isolated from venue guest traffic; domains such as unrelated web content should never be treated as part of a professional control network or testing workflow.
Protect The System From Heat And Dust
Australian touring can involve hot loading docks in Perth, humid summer events in Brisbane or dusty outdoor sites outside Adelaide. A sealed case protects equipment in transit, but a completely airtight operating enclosure can trap heat. Design a controlled airflow route with filtered intake and exhaust openings that cannot be blocked when the case is positioned against a wall.
Measure the heat output of the console, switch, power supplies and any processing hardware installed in the rack. Fans should be replaceable and quiet enough for a radio studio or theatre pit. Temperature monitoring is useful for early warning, particularly when a case is left powered during a long broadcast day.
Dust filters need routine cleaning, especially after outdoor festivals or road travel. Keep a small maintenance kit with spare filters, fan units, patch leads and labelled adapters. If the production also displays gaming or entertainment-related media, confirm that visual assets are suitable for the audience; understanding dropping-symbol mechanics may be relevant to a content team, but it should remain separate from the audio control network.
Test The Case Before Its First Show
A completed case should be tested as a touring system, not simply powered on at the workshop. Load a Ruby show file, confirm fader and touchscreen operation, verify Power Core routing, and check that VisTool panels display the correct controls. Test RƎLAY connections and AutoMix behaviour if they form part of the event workflow.
Perform a shake and handling inspection after the first transport simulation. Check that rack screws remain tight, cables do not pull against connectors, lids latch correctly and casters roll without twisting the frame. Test the case at realistic room temperature and with every installed device operating simultaneously.
The final documentation should include a wiring diagram, IP plan, power schedule, connector map and startup sequence. Add photographs of the rear panel and internal cable routing so a replacement operator can restore the system quickly. Before dispatching the case, complete one full rehearsal with the actual microphones, intercoms, codecs and venue-style network connections, then record the tested configuration in the touring file.