Routing Reliable N-1 Feeds With Power Core

Remote contributors are now part of everyday radio production. A presenter in Sydney, a sports reporter in Melbourne, or a specialist guest calling from regional Queensland may need to hear the programme while avoiding their own voice and return audio. That personalised return path is an N-1 feed, also known as mix-minus.

Power Core’s internal matrix provides a practical way to build these feeds inside a networked Lawo environment. Instead of relying on a tangle of external mixers and point-to-point wiring, engineers can define sources, destinations, mixes, and control relationships in a central audio infrastructure.

Why N-1 Audio Matters For Remote Radio

A standard programme mix contains the presenter, music, beds, callers, and studio microphones. Sending that complete mix back to a remote host creates a delay loop when the host’s own microphone signal returns through the contribution link. The result can be distracting, or unusable, for live conversation.

An N-1 feed removes the recipient’s own contribution while retaining the material they need to follow the show. A host may hear the presenter, playout, news reader, and talkback caller, while their own microphone is excluded. A second remote guest can receive a different mix-minus that excludes their contribution as well.

Australian broadcasters often manage contributors across large distances and changing network conditions. A breakfast programme produced in Sydney may connect with a reporter in Perth, where the time difference affects scheduling, while a regional station may depend on mobile or NBN connectivity. Consistent mix-minus routing helps keep the conversation natural when the connection itself is less predictable.

Building The Signal Path In Power Core

The internal matrix can be treated as a routing layer between local sources, network inputs, processing paths, and destinations. First, identify the programme bus, each remote return, and the contribution sources that must be removed from those returns. Clear naming is essential: labels such as REMOTE_A_TX, REMOTE_A_RX, and PROGRAMME_N-1 make troubleshooting faster during a live shift.

For each remote host, route the required programme elements to a dedicated N-1 bus. Exclude that host’s incoming microphone or codec return from the bus, then send the resulting mix to the appropriate output or network destination. The same approach can be repeated for multiple guests, with each bus excluding a different source.

Gain structure should be settled before the matrix is used for live work. Keep contribution returns at a stable operating level, check the programme bus for unexpected processing, and confirm that the remote codec receives the intended output rather than a confidence or control-room feed. A short test with headphones at the contributor’s location can reveal routing errors that meters alone will not show.

Managing Talkback, Delay, And Local Sources

Talkback is separate from the main mix-minus design. A producer may need to speak privately to a remote host, while the host still receives the programme. Configure a controlled talkback path that can be added to the relevant return without accidentally entering the public output.

Delay also requires careful planning. Codec latency, satellite links, and software contribution tools can make a remote guest hear the programme later than expected. If the host hears their own voice through the return, even a correctly configured N-1 will not remove the delay caused by their local acoustic environment. Headset use, microphone placement, and local monitoring discipline remain important.

Local studio sources should be considered individually. A music bed might be appropriate for a presenter but unnecessary for a news correspondent. A producer’s intercom may belong on a private return rather than the broadcast mix. The matrix makes these choices repeatable, while VisTool or a compatible control surface can expose useful source and destination controls without requiring an operator to edit complex routing during transmission.

Integrating Processing And Broadcast Control

Routing and processing work best when their roles are clearly separated. Power Core can provide the networked audio infrastructure, while console logic and software control determine which sources are active. This supports flexible workflows for radio, live production, post-production, and other applications that need shared audio resources.

For speech-heavy remote segments, AutoMix processing can help manage several open microphones before the programme is sent to the appropriate N-1 buses. Automatic level control does not replace good routing: each contributor must still be excluded from their own return, and the engineer must verify that processing has not introduced an unwanted contribution path.

External devices may still be part of the system, including codecs, GPIO interfaces, telephone hybrids, and studio peripherals. When a custom interface or specialist hardware is required, an OEM integration partner can help bridge the gap between the audio network and a particular facility design. The matrix should remain documented as the authoritative signal map, even when third-party equipment is connected.

Operating Safely In Australian Stations

Australian radio facilities may need to support local programmes, syndicated content, outside broadcasts, and remote contributors in the same day. A Melbourne studio can hand over to a national network, while a station serving rural New South Wales may use a smaller operator team and fewer technical resources. Preset-based routing reduces the risk of rebuilding a mix-minus under pressure.

Compliance and privacy also matter. The Australian Communications and Media Authority regulates broadcasting, and stations should apply their normal procedures for contributor consent, recorded calls, and access to studio communications. An N-1 path must be checked so private talkback, producer instructions, or off-air material cannot leak into the public programme.

Before going live, test each remote destination separately. Ask the contributor to identify what they can hear, speak while the programme is active, and confirm that their own voice is absent from the return. Save a known-good state, document the matrix destinations, and provide operators with a simple recovery route if a codec or network endpoint changes.

Requirement	Power Core matrix approach	Operational check
Remote host return	Dedicated mix-minus bus	Host hears programme content without their own contribution
Multiple guests	Separate N-1 bus for each guest	Each bus excludes the correct source
Producer communication	Independent talkback path	Private instructions stay off the programme
Variable programme content	Controlled source selection	Music, beds, and local sources are included deliberately
Fault recovery	Named routes and saved states	Operator can restore a tested configuration quickly

The key principle is simple: every remote contributor needs a return designed around what they must hear and what they must not hear. With clear source names, dedicated N-1 buses, controlled talkback, and a verified fallback state, Power Core’s internal matrix can make remote hosting dependable across Australian radio workflows.