- REMI brings the signals from the venue to a central control room, instead of bringing the control room to the venue.
- The link carries cameras, audio, camera control, tally, intercom and returns.
- Low, constant latency and two network paths are mandatory.
- It pays off for recurring events, at venues with good connectivity and when the central control room already exists.
- The venue still needs a crew: camera operators, audio and technicians.
On this page
Short answer
Remote production, known as REMI, for remote integration model, is the model in which only the cameras, the microphones and a minimal crew go to the event. The signals travel over fiber or a dedicated network to a central control room, where the director, switcher, replay, graphics, audio mixing and outputs sit. Instead of taking the control room to the event, the production brings the event to the control room. That cuts travel and equipment on site and lets the same control room cover several events, but it requires a fast network with low delay and a backup.
How it works in practice
- 01At the venueCameras, lenses, microphones and the equipment that converts and encodes the signals. The local crew includes camera operators, a field audio technician and network and video technicians.
- 02On the wayThe signals leave encoded at low latency over fiber, a dedicated network or high-capacity internet, on two independent paths.
- 03At baseThe control room receives the signals, aligns their timing and produces as if the cameras were next door: switching, replay, graphics, audio and output to the broadcaster or platform.
- 04Back to the venueBase sends back the program feed, intercom, tally and camera control commands, so the crew on site works as in a normal production.
What must travel over the link
- Video from each camera, at a quality good enough for switching and replay.
- Audio from every microphone and from the ambience, for mixing at base.
- Camera control: iris, color and exposure driven from base through the remote panel of the CCU.
- Tally: the light that tells the camera operator they are on air.
- Intercom: the conversation between the director and the local crew, with minimal delay.
- Returns: the program feed back to monitors, screens and the teleprompter at the venue.
Each of these items needs bandwidth, network priority and a plan B. Forgetting intercom or tally when designing the link is the most common mistake on a first remote production.
Bandwidth, encoding and latency
Bandwidth depends on the number of cameras and the type of encoding. Lightly compressed codecs with a delay of a few lines, such as JPEG XS, preserve the picture for switching and replay and usually take between one hundred and two hundred megabits per second per HD camera. Codecs such as low-latency HEVC use far less bandwidth, at the cost of more delay and more processing. Uncompressed signals in SMPTE ST 2110 only fit on high-capacity fiber links.
Latency matters more than it seems. The camera operator sees the return late, the director speaks on intercom and the answer lags, the shader's color control reacts after the adjustment. The goal is low delay and, above all, constant delay, so the crew gets used to the rhythm. To estimate the bandwidth for each camera and for the whole set, use the broadcast bandwidth calculator.
Sync and redundancy
Every camera must arrive aligned in time, or the cut becomes a jump. That is why the venue uses a common reference, usually locked to GPS, and base aligns the frames on arrival. The signals leave on two network paths, from different carriers or routes, and the receiver uses whichever arrives better. Recording the cameras at the venue as well is a simple backup in case the network fails.
Run a full network rehearsal before the first event: every camera, intercom, tally and returns at the same time, for at least the length of a whole event. Network problems show up under load and over time, not in a five-minute test.
Remote production models
- Full remote: only acquisition at the venue; everything else at base.
- Split: part of the production stays at the venue, such as audio or replay, and switching happens at base.
- Distributed: the production uses several centers or professionals in different places, connected by the same network and sometimes by cloud processing.
Advantages and limits
Remote production cuts travel, hotels and equipment shipping, puts the production crew in rooms designed for the work and lets one control room cover several events on the same day. It also makes it easier to keep quality consistent across a whole season.
The limits are the dependence on the network and the cost of connectivity, which does not always exist at the venue. Remote sites without fiber, or one-off events with complex production, can work better with an OB truck or a flypack on site.
The comparison REMI or on-site production puts the criteria side by side, from cost to risk.
When it pays off
- Championships, leagues and event series with the same format.
- Venues with fiber or a dedicated network available.
- When the central control room already exists and sits idle part of the time.
- Events in several cities on the same day, run from the same base.
If the venue has no fiber, a middle route is to take a compact control setup to the event for switching and send only the program feed and a few isolated cameras to base, over lower-capacity links.
Where i9 comes in
A remote production brings together both halves of what i9 does. i9 Studios runs cameras and technical and ENG crews on site, based in São Paulo with crews in Manaus.
i9TV designs streaming and encoding and live links to carry the signals from the venue to base.
On the other side of the link, i9TV integrates control rooms that receive the cameras and produce the show.
If you are considering producing a series of events remotely, start with the link design and the network rehearsal. The multicamera systems team helps define cameras, control and connectivity.
i9 does this every day: production, broadcast, engineering and equipment, with one team accountable from start to finish.