Integrating Lawo's Broadcast 3.0 with third-party codec management

Networked studios have replaced hardware islands in Australian radio. The ABC, SBS and the larger commercial networks in Sydney, Melbourne and Brisbane have re-plumbed their routing over the past decade, and Lawo's Broadcast 3.0 vision sits squarely in that transition, treating audio, video and control as one fabric rather than separate disciplines.

Codec management often lives outside that fabric. Many facilities still rely on dedicated APT, Tieline or GatesAir units handling IP, ISDN or 4G/5G links. The challenge is making a Lawo Power Core or Ruby console feel native alongside those external devices.

Australia's spread, with capital-city DAB+ markets alongside remote mining or rural transmitters, shapes how broadcasters design redundancy. Broadcast 3.0 must slot into that picture without forcing sites to rip and replace kit.

This piece looks at scripting crossfades, redundancies and codec switching across vendors, drawing on AoIP behaviour, AutoMix transitions and standards like SMPTE 2110 and AES67.

Architecture of a hybrid codec and console network

Broadcast 3.0 relies on an IP backbone supporting SMPTE ST 2110, AES67 and AMWA NMOS discovery and routing. A Power Core engine can advertise audio streams as NMOS resources, and RƎLAY virtual radio tools expose browser interfaces for journalists while the same architecture publishes metering and tallies over the network.

When a third-party codec joins, it usually appears as a destination rather than a source. Lawo consoles send cleaned-up programme audio through the network, and the codec egress node shapes it for uplink. Automated crossfade scripting shows transition logic triggered from external events, including a tally arriving on a virtual GPIO stream.

Return paths matter as much. Contributors feeding in from regional Victoria or Western Australia over IP codecs expect their own mix-minus, talkback and IFB to follow through gateway devices. Broadcast 3.0's open control layer patches those destinations dynamically, rather than hard-wiring analogue tie-lines.

Monitoring and control across vendor boundaries

Unified dashboards remain a goal for engineers juggling multiple vendor systems. Lawo's VisTool and HOME cover the Lawo side, while third-party codec management typically sits in tools such as Tieline's TieCast, Comrex ACCESS Manager or proprietary SNMP dashboards. Layered alerts mean an operator does not watch six screens during an outside broadcast.

NMOS IS-04 and IS-05 remove most of the pain. Once a codec is registered, VisTool or any BCP-compliant controller can move subscriptions, adjust jitter buffers and read status. Engineers in Perth working a Pilbara uplink can confirm connection state from the same pane showing console channels.

For broadcasters with staff split across cities, role-based access in HOME keeps regional IT teams and central engineering aligned. Codec manufacturers and their integration partners often supply companion plugins exposing NMOS endpoints or REST hooks, which VisTool wraps as custom widgets.

Network realities across the country

Bandwidth is rarely uniform from Broome to Bondi. Studios in central Sydney enjoy fibre, but a relay near Kalgoorlie or a mine camp north of Newman depends on microwave, satellite or public 5G. Ruby consoles handle variable conditions through floating-point AoIP processing, yet the codec on each end still sets the ceiling.

Time zones shape multi-site control. A producer in Adelaide handing over to Sydney mid-broadcast needs every codec along the path to see the change. HOME's event logging and audit trail let teams reconstruct regional network feeds, which ACMA-licensed operators expect during incident reviews.

Redundancy design weighs heavily too. Australian broadcasters often run bonded cellular or dual-path IP encoders alongside fibre, and Broadcast 3.0's parallel-stream support patches both paths to one console without manual repatching, a cleaner failover than the matrix-only approach.

Regulatory and standards alignment

Australian broadcasters operate under ACMA rules, including the digital radio standard used for DAB+ in capital cities and obligations tied to licence areas. Codec management has to respect those boundaries, particularly when transmitting into adjacent licence areas or rebroadcasting across state borders.

Lawo's alignment with ATSC 3.0 and next-generation radio standards is documented in detail, including material on Broadcast 3.0 standards covering the relevant specs. While ATSC 3.0 is more relevant to North American markets, principles around Next Generation Audio, hybrid delivery and immersive sound feed back into Lawo's roadmap and inform how Australian groups plan ahead.

Sites using third-party codecs must keep loudness, dynamic range and stream metadata compliant end-to-end. Power Core can insert loudness logs into the same stream the codec forwards, removing the need for separate metering hardware at the gateway.

Workflow patterns that actually save time

Commercial networks often use AutoMix for long-form music where a presenter fades over a segue. The same VisTool layout can host a button triggering a codec destination change, routing a Melbourne-syndicated show to a different uplink when the network switches regions mid-broadcast.

Newsrooms benefit too. A reporter at Parliament House in Canberra dials into a RƎLAY codec on a laptop, appears as a clean feed in the console, and goes to air without the control room reconfiguring a patch. The codec management system tracks connection state, hands over to a backup cellular path, and clears down at segment end.

AFL coverage relies on rapid venue switches, and the same recipes that handle a daytime match work for an evening remote from a regional festival. Each event triggers a VisTool preset that rewires console sends, activates the right codec profile and updates on-air tallies.

The team has scheduled a two-hour lab session in the next maintenance window, with the codec, the Power Core and a VisTool workspace registered to a single NMOS registry. The test replays a recorded outside broadcast and confirms every handover, alarm and log event in the audit trail before the configuration is moved onto a live morning schedule.