Power Core delay compensation for satellite and IP feeds in Australia
Power Core sits at the heart of many radio operations across Australia, where studios in Sydney, Melbourne and Brisbane routinely combine satellite downlinks with IP contribution circuits. The compact audio node does far more than routing and mixing — its delay management engine keeps lip-sync and programme timing coherent when a single broadcast is assembled from feeds that arrive by very different paths. Engineers working on networked workflows for the ABC, ARN and community stations rely on that precision to keep talk segments, music beds and remote reports sitting exactly where they should.
The Australian continent adds its own complexity. A live feed from Perth to an east-coast studio crosses three time zones and often hops between satellite and fibre, while an outside broadcast from a country show may travel over a cellular IP path with jitter that changes minute by minute. Power Core's audio delay compensation is designed for exactly that kind of patchwork, giving operators a single point of control for managing offsets across legacy and modern contribution links.
The timing challenge of multi-source broadcasts
Every signal in a radio chain carries some delay, whether it is the 250 ms of a typical satellite hop or the variable buffering added by an IP codec. When a network newscast pulls in a correspondent from a remote bureau, the studio anchor and the field reporter will sound out of step if those offsets are not reconciled. Listeners notice even a small mismatch, and advertisers running time-sensitive reads are unforgiving of drift during a commercial break.
Australian broadcasters handle this every day. A morning show in Sydney might cut to a regional reporter in Toowoomba feeding back over a microwave link, then to a sports caller in Adelaide reading from a live AFL match. Each of those sources arrives with its own latency profile, and Power Core allows the operator to align them against a house reference so that every voice shares the same starting point in the mix.
How Power Core handles latency across feeds
Inside the node, each input path carries a configurable delay line that can be trimmed in small steps. Engineers measure the offset of an incoming feed using test tones or a clapper, then dial the matching delay into Power Core so that the signal arrives at the bus aligned with the studio microphone. The process is repeatable, so once a satellite hop has been characterised, its value can be stored as part of the preset.
Because Power Core is built on the same RAVENNA/AES67 backbone used elsewhere in Lawo's portfolio, delay values can travel with the stream as metadata. A feed passing through a routing matrix or a remote VisTool screen therefore retains its timing relationship, even if the physical path changes. Operators in regional hubs such as Cairns or Hobart can move signals around the network without losing the carefully tuned offsets that keep their output clean.
Satellite vs IP in Australian operations
Satellite remains a workhorse for broadcasters covering events in places where fibre is impractical, such as mine sites in the Pilbara or cattle stations in the Top End. The path is predictable, which makes delay compensation straightforward, but the round-trip latency is fixed and cannot be shortened. IP feeds, by contrast, can deliver lower delay when conditions are right, yet their jitter requires a buffer that grows and shrinks over the course of a broadcast.
Power Core accommodates both by offering independent delay lines per source and a monitoring view that exposes the total offset for each contributor. Engineers working on the summer cricket circuit, for instance, can hold a satellite rights feed at a known value while a journalist connects from the press box over 5G with a slowly changing IP buffer. The console keeps both locked to the same timeline, so the on-air product never reveals the underlying complexity.
Live sport and event workflows
Major sporting events put timing systems under their most public stress. A State of Origin call from Brisbane, an A-League sideline report in Melbourne, or a Sydney New Year's Eve outside broadcast all demand that crowd reaction, commentary and music arrive together. When a single programme combines a stadium PA feed, a commentator microphone and a network satellite return, the operator's job is to make the listener feel as if everyone is in the same room.
Power Core's per-channel delay is also useful when broadcasters need to respect contractual timing windows, such as a sponsored segment that must air within a few milliseconds of a network clock. Visual elements, including quick-turnaround video clips, can be prepared in parallel using a workflow like ready-to-air video files and rolled in once the audio bed is confirmed. The combined audio and video path then holds together through the rest of the broadcast.
Regional networks and remote feeds
Australia's geography pushes broadcasters towards hub-and-spoke models. Capital city studios aggregate content from regional centres, and the long tails of those networks often run over a mix of satellite, IP and even bonded cellular. Community stations in places like Broome or Alice Springs depend on affordable contribution links that were never designed for low-latency work, so any tool that hides their shortcomings is welcome.
Power Core compensates for the realities of those remote feeds without forcing the station to invest in new circuits. Once an operator has characterised a contributor's typical latency, that value can be applied automatically whenever the source connects. This makes it practical for small teams to run networked programming across vast distances, with the studio in Perth or Darwin sounding just as tight as one in Sydney.
Integration with RƎLAY VRX and software tooling
For facilities that prefer a software-first approach, Power Core's delay data can be exposed to Lawo's wider ecosystem, including RƎLAY VRX virtual radio tools. This allows timing relationships to be visualised and adjusted from a remote workstation, which is helpful for engineers covering overnight shifts or working across time zones. A producer in Adelaide preparing for a national broadcast can review the alignment of all incoming feeds before going to air, rather than reacting during the first break.
The same connectivity makes it easier to maintain consistency when a station swaps between physical consoles and software surfaces. As long as the delay values are stored with the source rather than the surface, the operator's workflow remains predictable, and the on-air result stays clean.
Practical setup and monitoring
The daily use of Power Core's delay compensation is less dramatic than the theory suggests. Most engineers build a library of values during commissioning, then rely on those presets whenever a known source connects. A few minutes spent measuring a new satellite return or IP codec during installation pays back across years of trouble-free broadcasts.
Monitoring matters as much as setup. Power Core exposes timing relationships through the same interface used for routing and mixing, so an operator glancing at the surface during a break can see whether a feed has drifted. If an IP contributor's buffer has grown, the value can be adjusted on the fly without pulling the source out of the mix.
This makes the system approachable for operators who are not network engineers. A relief announcer in a regional studio can be shown how to nudge a single fader's delay in case a remote caller sounds late, without needing to understand the underlying signal path.
A practical starting move is to block out a single commissioning hour this week to measure and log the latency of every regular satellite and IP contributor feeding your main studio, then enter those values into Power Core so they live as part of the daily preset rather than a last-minute adjustment.
