Return Feed and Talkback: Two Remote Production Terms Explained

Almost every conversation about remote production support starts with the same two phrases: return feed and talkback. They sound like jargon, yet each one answers a very ordinary question. Can the person at the far end see what the show looks like right now, and can they hear the director? If either answer is no, the best camera and the fastest link will not save the programme.

I am a systems engineer, so I tend to meet these terms as boxes, cables and settings. Crews meet them as moments: a presenter who cannot tell when to start, a camera operator who is framing blind. This note keeps the words plain, because a small crew spread over several locations has no spare person to translate between engineers and directors.

In the same spirit, I will use autumn productions as the running example: talks, panels and short studio programmes where one gallery cuts between two or three sites.

A return feed is the programme output sent back to a remote location. Your contributor at another site sends pictures and sound to the gallery; the return feed carries the finished mix, or sometimes a clean version of it, back to them. It is called a return because it travels the opposite way to the contribution.

Why does the remote site need it? A guest in a borrowed room usually has no idea what viewers are seeing. With a return feed on a monitor they can watch the cut, see when a graphic covers their shoulder and judge when they are on air. Without it they guess, and guessing shows.

The return does not need to be beautiful. A small, slightly delayed picture is usually enough for a guest, as long as everyone understands it lags behind the real output. What matters is that it exists, that it is checked before the show, and that someone knows who is watching it.

• Contribution goes from the remote site to the gallery
• Return feed goes from the gallery back to the remote site
• A delayed return is normal and should be explained to guests

Talkback is the private channel on which the director speaks to the crew and guests, separate from anything the audience hears. In a single building it is a wired intercom. Across several sites it is usually a voice link running beside the video, and it deserves as much care as the pictures.

The rule I ask every crew to keep is simple: talkback is never mixed into the programme sound. It sounds obvious, but a wrongly routed fader is one of the commonest ways a director's instruction reaches viewers. We check the routing on paper before the rehearsal and again by ear during it.

Good talkback habits matter more than good equipment. Short instructions, the name of the person addressed first, and silence when the director is cueing. A remote operator who hears a calm voice at the right moment will usually do the right thing without being told twice.

On a live remote day the return feed and talkback are checked as a pair. The remote operator sees the programme on the return, hears the director on talkback, and confirms both before anything else is rehearsed. If one fails, the other often fails with it, because they frequently share the same internet connection or the same router.

That shared path is the point worth planning for. If the video link degrades, talkback may become choppy at the very moment you need it. Where the site allows, we prefer to give talkback its own route, even a modest one, so the director can still speak when the picture is struggling.

Monitoring sits behind all this. Someone in the gallery watches the incoming sites for dropped frames and audio problems, and tells the director early. A small crew can only work across several locations when one person is clearly responsible for watching the links.

• Check return and talkback together before rehearsal
• Give talkback its own route where the venue allows
• Name one person to watch the incoming links

Before the day, a short list of questions saves a great deal of trouble. Does the site have a wired connection, or only Wi-Fi? Who will be standing next to the camera? Is there a second screen where the return feed can be placed, in front of the guest rather than behind them?

Ask also about the room itself. A quiet corner with a door that closes helps talkback far more than expensive headsets. If a guest must wear earpieces, ask them to try them beforehand, because discovering a fitting problem after the programme has started leaves no good options.

None of this requires technical knowledge from the contributor. It requires a friendly call a few days before, a clear description of what they will see and hear, and one named contact at their end. In my experience, that call prevents more problems than any piece of kit we bring.

If you remember nothing else from this note, remember the order: link first, return feed second, talkback third, then pictures and sound for the programme itself. Each step depends on the one before it, and each takes only a few minutes when done calmly in that order.

For a first remote show, keep the arrangement modest. Two sites, one return feed to each, one talkback channel, one person watching the links. Complexity can be added show by show once the crew trusts the basics.

These are the habits behind the remote production support we offer: small crews, clear words for each part of the chain, and a gallery that knows where every signal is coming from and going to.

• Test the link, then the return feed, then talkback
• Keep talkback out of the programme mix
• Start with two sites and add more later