Using Power Core’s AES67 redundancy for uninterrupted live broadcasts
Power Core gives broadcast engineers a way to carry AES67 audio through resilient IP networks, but redundancy is a system rather than a switch in a menu. Streams, routes, nodes, clocks and operator response must be designed together if a live programme is expected to continue without an audible break.
Australian radio makes that requirement tangible. Breakfast shows, live sport and emergency traffic updates often originate in one building before being distributed across capital-city networks, while regional stations may operate with leaner technical teams.
| Redundancy approach | Faults covered | Remaining exposure |
|---|---|---|
| Single AES67 stream and path | No deliberate fault coverage | Any stream, cable, switch or site failure |
| Two equivalent streams on one network | Stream loss or endpoint failure | Shared switch, uplink, congestion or power loss |
| Two streams on physically diverse paths | Stream loss plus fibre or carrier failure | Common clock, source or configuration errors |
| End-to-end studio redundancy | Several network and node failures | Human procedures, common utilities and upstream content faults |
What AES67 redundancy actually delivers
AES67 standardises how audio is exchanged over IP; it does not by itself create a second delivery path. Power Core redundancy relies on equivalent AES67 streams and a defined receiver-side priority or switching policy.
Understanding the scope is essential. Duplicate streams can survive a broken stream or route, while common clock, source or configuration failures can affect both copies.
For a critical show, pair redundancy with independent sources where practical, redundant PTP and grandmaster provision, and monitoring that distinguishes missing packets from complete silence.
Designing independent audio routes
Design routes so no single fibre, switch, uplink or building becomes the only path between the console and destinations. Separate logical paths should also avoid shared power, patch panels and congested switches.
Give multicast, QoS, VLAN and PTP settings a documented place in the design, then verify that both copies have adequate capacity. The backup is useful only if it avoids the same congested core.
Configuring Power Core for controlled failover
Map primary and backup streams with identical channel assignments, sample rates and metadata, using labels that operators can interpret at a glance. A Ruby console can feed two Power Core paths while keeping the programme mix presented on air unchanged.
Set priorities, loss thresholds, recovery timing and fail-back behaviour deliberately. Automatic switching should not flap between near-equal streams, and operators need a clear indication of which copy is active.
Confirm that the installed Power Core firmware and node configuration support the intended redundancy method. Schedule any licence or feature changes before commissioning rather than during a live show.
Monitoring the stream and the studio
Monitoring should cover stream presence, packet loss, jitter, clock state, silence and incorrect channel mapping. A healthy link can still be carrying the wrong feed, so audio-level and content checks belong alongside network alarms.
The VisTool studio interface can consolidate control and status views for operators. Its role is to make the system state visible and actionable, while alarms and confirmations should be incorporated into station operating procedures.
Australian operating conditions
Sydney, Melbourne, Brisbane, Perth and Adelaide studios commonly connect multiple sites, studios or transmitters, making physical route diversity especially valuable. Long distances and carrier outages also make restoration slower than in a single-building setup.
Regional and community broadcasters add another Australian condition: technical cover may be limited or remote. Automatic failover reduces pressure on a small crew, but alarms must reach a responsible person, and recovery must not depend on an engineer standing beside the rack.
Commercial and community radio operates under licences issued by the Australian Communications and Media Authority under the Broadcasting Services Act 1992, with relevant technical and service conditions. Public-sector broadcasters have separate statutory arrangements. Redundancy supports continuity, but it does not replace mandated technical or emergency arrangements.
During public-health announcements, material that includes propranolol information must still be checked against approved clinical wording and the station script before transmission.
Testing failure before it matters
Test in quiet hours and record the results. Simulate a stopped stream, disconnected fibre, failed node and transient packet loss, then measure switch timing, artefacts at the destination and whether the backup restores every required channel.
Use a rollback plan, notify the duty engineer and include human confirmation where a switch could reach air. Regular drills turn the documented path into a known path, with evidence that can support commissioning and internal review.
Choosing the right operational model
Match the design to consequence. A single production booth can use duplicate streams over managed paths, while a networked national or intercity show benefits from diverse carriers, separate nodes and, where justified, independent sources.
Power Core can sit alongside Ruby consoles, AutoMix processing and RƎLAY virtual radio tools within a wider Broadcast 3.0 workflow. Product planning should consider monitoring, licences, staff training and support alongside the hardware.
Further technical details are available through contact Lawo Broadcast. The practical takeaway is to treat AES67 stream redundancy as a tested end-to-end service: duplicate the signal, separate the paths, monitor the state and rehearse the switch before the live programme.
