What is REMI? Remote production in broadcast: how audio travels, syncs and is monitored from afar

0

Covering a match, a concert or a studio show without dispatching an OB truck and its whole crew: that’s the idea behind remote production, usually known by the acronym REMI (Remote Integration Model), also called at-home production. On site you leave only the bare minimum to capture; the mixing, playout and supervision happen from a central control room, sometimes hundreds of kilometres away. The model has won over television and radio alike — and it’s audio that concentrates the real challenges. Let’s break it down.

A compact broadcast console, typical of remote production setups
Credit: Calrec

The principle of REMI

In a classic production, the whole technical setup travels: OB truck, console, mixing crew, intercom. REMI flips the logic. At the event you install only the capture (mics, cameras) and the transport gear that puts the feeds onto a network. Everything else — mixing console, playout, sound engineers, direction — stays in a central control room that can handle several events a day with the same team.

The benefits are obvious: less travel, lower costs, a smaller carbon footprint, and above all a pooling of people and gear. One team can run three sporting fixtures without leaving their seats. In return, everything rests on the reliability of the link, and that’s where audio gets demanding.

Making sound travel: transport

The heart of REMI is transporting the feeds between site and control room. Two broad approaches coexist. Over dedicated high-capacity links, you extend standardised audio-over-IP — Dante, AES67, SMPTE ST 2110 — beyond the local network, carrying dozens of uncompressed channels at studio quality. Over public or bandwidth-limited links, you use contribution codecs that compress the sound intelligently and ride out the vagaries of the internet.

To understand these building blocks, two companion reads: our explainer on audio-over-IP with Dante for high-density local transport, and the one on contribution codecs for long-distance links. REMI often combines both: ST 2110 on a dedicated fibre, a codec as backup over bonded cellular. For the standards themselves, our overview of AoIP: Dante, AES67 and ST 2110 sets the scene.

Everyone on time: synchronisation

As soon as you handle audio-over-IP across several sites, synchronisation becomes critical. Equipment must share a common clock, or the feeds drift, click or drop out. That’s the job of the PTP protocol (Precision Time Protocol), which distributes a timing reference across the network. Between two distant sites, ensuring that reference is an art in itself — often leaning on locally synchronised GPS sources. The topic deserves a pause: we detailed it in our guide to PTP and clocking.

The crux: intercom and monitoring

Here’s where REMI audio is won or lost. With the team at a distance, the talkback network (intercom) becomes vital: the director in the central control room must talk to the operator left on site as if they were side by side. A well-configured, redundant IP intercom is the backbone of remote production. That’s the whole subject of our article on intercom in broadcast production, whose demands REMI pushes to the limit.

Monitoring is the other challenge. The sound engineer mixes an event they can’t see with their own eyes and hear through a link that inevitably adds delay. So you need a reliable return feed with controlled latency, and clear indicators (levels, loudness, feed presence) to catch a link failure instantly. You work by ear, but with reinforced visual safety nets.

Latency, the permanent companion

Every remote link adds delay. A few milliseconds on a nearby fibre, far more over cellular or satellite. That latency creates two problems: the responsiveness of intercom exchanges (speaking and being heard without awkward lag) and lip-sync on air, which means aligning audio to video at the end of the chain. You don’t remove latency; you measure it, compensate for it and make it predictable. Serious setups always plan for redundancy: a main path and a backup path able to take over without dropping the broadcast.

Full REMI or hybrid?

Not every production goes all the way. In full REMI, almost no one is left on site on the mixing side: everything is driven from the central control room. In hybrid mode, you keep a small local setup — a pre-mix, an operator, a compact console — that provides initial shaping and acts as a safety net if the link weakens. The choice depends on the stakes, the budget and the appetite for risk. For a sensitive live show, hybrid reassures; for a high volume of standardised events, full REMI delivers its full economics.

My take

REMI isn’t a cost-cutting gimmick: it’s a deep reshaping of the craft, where the network becomes the stage. On the audio side, it rewards those who look after the foundations — clean transport, flawless sync, redundant intercom, readable monitoring. The trap would be to think “remote” means “simpler”; it’s the opposite, you move the complexity from the truck to the network. The good news is that the building blocks are mature and proven. Built with method and a real backup plan, a remote setup holds up as well as an OB truck — and lets you cover what you could never otherwise afford.

Share.

About Author

After 20+ years in professional audio: live sound engineering, studio technical direction (Deep Forest, Pierre Jacquot), head of digital marketing at Playback.fr. A first-hand witness to the analog-to-digital shift, I track the whole audio landscape and break it down here — no fluff.