Power Core sample rate conversion for 48 and 96 kHz radio
Power Core’s sample rate conversion lets broadcast engineers combine 48 kHz and 96 kHz streams in one managed audio system. A studio feed, outside contribution and high-resolution venue feed can enter the same processing environment and leave at the rate each destination requires, reducing friction when the audio is correct but its format is not.
For Australian broadcasters, this is a practical issue. ABC, commercial, community and educational stations generally work in 48 kHz, while touring shows, post-production and some event coverage use 96 kHz. Facilities from Sydney and Melbourne to regional centres must often bridge those workflows.
Used with Ruby, VisTool and RƎLAY, Power Core can support a coherent path from capture and contribution to monitoring, recording and playout. The gains depend on disciplined design: clocking, latency, network capacity and conversion quality need to be planned together.
Why Australian radio networks encounter mixed rates
A 48 kHz workflow is the safe broadcast default because it matches much installed playout equipment and the wider television and production ecosystem. A 96 kHz workflow can retain greater frequency range and timing margin for archival or creative work. Neither rate is automatically better; the complete source-to-speaker chain decides the result.
The mismatch appears when a Brisbane venue sends high-resolution audio to a Melbourne hub, or a regional station accepts a 96 kHz feed while its playout remains 48 kHz. During the arvo drive slot, an external converter failure is not graceful. Conversion must be transparent, monitorable and easy to diagnose.
How Power Core handles the conversion
Conceptually, Power Core receives one rate, resamples it for the processing graph, and converts again only if the destination needs another rate. A 96 kHz input can be mixed with 48 kHz programme material and delivered as 48 kHz, while a talkback feed can be sent to a 96 kHz recorder.
Sample-rate conversion is not clock synchronisation. SRC changes the number of samples per second; disciplined word-clock distribution and supported network synchronisation still matter. Current product options should be checked in the official Power Core overview, then tested against the facility’s actual timing plan.
Building a practical mixed-rate signal path
Begin by listing every source, processing stage and destination by rate, channel format, latency and clock domain. Keep native-rate paths where possible, place conversion at clear boundaries and nominate the authoritative clock. A typical design carries 48 kHz studio audio around the core and accepts one 96 kHz contribution on a separate port.
Ruby can provide operator control while Power Core handles routing and processing. VisTool supports visual control in complex studio or live workflows, and RƎLAY extends virtual radio functions across distributed sites. Avoid converting merely because conversion is available: each extra stage can add filtering, delay and another point of failure.
Controlling clocking, latency and signal quality
A good SRC stage controls aliasing and imaging, but it cannot recreate detail absent from the source. Upsampling 48 kHz to 96 kHz doubles the sample count without creating genuine content between the 24 kHz source ceiling and the 48 kHz theoretical ceiling. Downsampling filters above the lower-rate limit first.
Latency belongs in the path budget. Converted streams may need buffering or delay compensation to stay aligned with native-rate material and any lip-sync feed. Test round trips with the real clocks, network devices and monitoring route. Nominal processing delay on a data sheet is not proof that the installed route is acceptable.
| Consideration | 48 kHz stream | 96 kHz stream |
|---|---|---|
| Common Australian use | Studio programme, talkback, playout and transmission | High-resolution contribution, capture, archive and creative production |
| Network demand | Lower per channel | Generally higher because more samples are carried |
| Theoretical frequency ceiling | 24 kHz | 48 kHz |
| Mixed-rate role | Native system rate in many installations | Specialist feed usually converted at the system boundary |
| Main operational risk | Connecting to a mismatched clock domain | Unnecessary conversion, extra bandwidth and added delay |
Where rate conversion earns its keep
The clearest case is live production with 96 kHz stage or orchestra feeds while the console, recorder and monitoring chain run at 48 kHz. Power Core lets those sources share one processing environment. This suits theatre and music events in Melbourne or Sydney, where a venue feed may arrive with a different clock from the studio.
It also helps post-production and archive workflows. A 96 kHz recording can remain native through capture and creative work, then be converted once for a 48 kHz broadcast master. Community stations with modest staffing gain from one routing platform, provided staff can clearly see and control every conversion.
Planning deployment, monitoring and ownership
Deployment starts with an inventory: expected rate of each port, fixed or variable operation, maximum channel count, clock source and latency needs. Check storage as well as network bandwidth. At the same bit depth, 96 kHz uncompressed audio carries twice as many samples per second as 48 kHz audio, though compression alters the transport calculation.
Configuration should display rates clearly, alarm on invalid clocks and retain status for remote support. Redundant paths and an agreed bypass protect live transmission to commercial networks, the ABC and community services. For another perspective during feasibility or commissioning, Atomic Bands offers useful context on the surrounding broadcast ecosystem.
What Australian broadcast teams should remember
Power Core’s sample rate conversion is not a reason to replace a stable 48 kHz installation with 96 kHz throughout. Its value is at the edges: when a worthwhile source arrives at another rate, a destination needs a specific rate, or a distributed chain must bridge clock domains. Convert once, keep the core consistent and document each boundary.
The design should meet ordinary Australian operating expectations: clear displays, dependable monitoring, controlled latency and no need to “have a go” when a live feed fails at 3 a.m. The point to remember is that mixed-rate working becomes routine when clocking, bandwidth, converter quality and ownership are settled before transmission day.
