Power Core optical MADI for remote venues
Remote contribution in Australia often links a production room in Sydney or Melbourne to a stadium, theatre or regional station. The arriving audio may have travelled as an IP service across a carrier network, then crossed the final venue connection as AES/EBU MADI. That division of labour matters: MADI is a dependable local digital interface, while the wide-area link handles distance, routing and service management.
With compatible MADI hardware installed, Power Core’s optical MADI inputs accept light-based digital audio and make it well suited to turning a remote venue feed into a routable studio source. In Australia, the real work lies in matching fibre types, transceiver wavelengths, clocking and channel maps to the venue’s changing production demands.
Carrying digital audio from the venue
MADI carries multichannel digital audio over a matched fibre path, commonly supporting 56 or 64 channels per pair, depending on sample rate and hardware. At the venue, a MADI transmitter feeds optical transceivers; at the studio, a compatible Power Core input card receives the light signal. The route is deterministic and avoids the electrical ground differences that can complicate analogue or copper interconnects.
That makes the interface useful in a theatre, arena or regional station where the local production gallery sits some distance from the stage. A Brisbane studio can ingest a venue feed without converting it to analogue, while a Melbourne production room can route it into Ruby console workflows and expose it through VisTool. Optical MADI moves programme audio only: talkback, control, GPIO and the return feed still need planned IP or other paths.
Planning fibre, clocking and site access
Begin with a route and equipment survey rather than a nominal distance. Single-mode and multimode fibre, connector types, transceiver wavelengths and any patch panels must agree from end to end. A remote contribution checklist can give procurement, venue IT and engineering teams a common record of channel count, signal direction, spare capacity, access windows and the person authorised to approve changes.
Next, document clocking and conversion. Confirm how the venue MADI source is referenced to the studio’s house clock, where any sample-rate conversion occurs, and how silence is represented. This is especially important when a carrier backhaul joins a local MADI link: MADI solves the venue-to-node interface, but it does not replace network monitoring or an agreed failover procedure.
Equipment crossing state borders also needs a named customs owner. Australian Customs documentation, commercial-import GST treatment and temporary admission can affect a touring kit, while local suppliers should verify RCM and EMC compliance for imported hardware. If the case contains RF transmitters, ACMA licensing is a separate obligation; a MADI audio node does not itself replace transmitter approval or venue electrical-safety checks.
Rehearsing the contribution workflow
Rehearsal should reproduce the remote desk, not merely prove that a file can play. Lawo’s RƎLAY is useful here because simulated live broadcasts let teams exercise transitions, talkback and failure states without waiting for the live event. A team in Adelaide can rehearse against the same show automation and presenter mix it will use from a temporary studio in Sydney.
Build an acceptance sequence around known programme tones, stereo and multichannel stems, talkback, mute, replay and route changes. Include a deliberately failed link and the operator’s manual fallback. Record audible artefacts, error messages, restoration time and the final channel map; this turns a technical connection into evidence that can be signed off before contributors travel.
Protecting programme audio in operation
Redundancy starts with physical diversity. Two fibre strands in the same duct may fail together, so where possible use separate routes or separate carriers. Power Core should receive independently terminated feeds where practical, while VisTool monitoring exposes signal loss, silence and routing mismatches. Keep a documented analogue emergency path for the minimum talkback and programme channels needed to manage the incident.
Australian geography makes that discipline important. The route from a Perth broadcast centre to a regional mine site, or from Sydney to a Newcastle venue, may cross different carrier infrastructure and maintenance regimes. Heat, dust, storms and seasonal road closures can affect equipment rooms and field teams. Clear escalation paths and time-zone-aware schedules are as important as spare optics when the contribution feed carries an entire live show.
Choosing and commissioning the connection
The right transport depends on the boundary being crossed. MADI is a strong endpoint choice where predictable audio and channel consistency matter; managed IP is better for flexible routing between distant facilities. Many Australian commercial, public and community broadcasters use both: IP across the backbone, then optical MADI into Power Core at the venue or studio edge.
Lawo’s Broadcast 3.0 ecosystem also allows Power Core to work alongside Ruby consoles, VisTool and RƎLAY rather than treating the node as an isolated converter. AutoMix can support talk-heavy workflows, although automated mixing still needs monitoring and clear responsibility for the remote presenter.
| Connection | Strongest advantage | Main constraint | Practical role |
|---|---|---|---|
| Optical MADI | Stable multichannel audio over dedicated fibre | Point-to-point; no IP control or return path | Venue-to-studio and studio-to-studio feeds |
| Managed Dante or AES67 IP | Flexible routing and easier remote control | Depends on network configuration and monitoring | Backbone between distant facilities |
| Copper MADI | Simple, reliable point-to-point audio | Limited distance and greater EMI sensitivity | Connections within a building or rack area |
| Analogue audio | Supports legacy equipment | Requires conversion and is susceptible to noise and gain errors | Emergency or specialist fallback |
The next concrete step is to run a two-hour, full-scale path test with the actual venue carrier: patch the planned channel map into a Power Core with optical MADI installed, inject known programme and talkback signals, measure latency and recovery time, and file the result in the commissioning record before the first show.