Support Center Workflows Directed remote voiceover

Direct the read, from anywhere.

How to build a remote voiceover tracking environment out of Source-Connect and the Source-Nexus Suite, with the performer on one side and the people directing them on the other.

The scenario

Two rooms, and everybody is talking at once

You are tracking a performer who is somewhere else, and you are not the only person with an opinion. A director wants to watch, an agency wants to listen, and every one of them wants to speak between takes. Meanwhile you have a talkback microphone open in a control room that also has to be silent the moment you hit record.

Two rooms, then, and a rule for each. Source-Connect carries the performance on its own path into your DAW. The Source-Nexus Suite handles everything that is not the performance: your talkback on a plugin, the muting handled by the transport instead of by your hand, and a browser room the people directing can join from a link.

What you need

Before you start

Source-Connect Studio Source-Nexus Review Source-Nexus Mute-On Source-Connect Talent Source-Nexus Gateway

Source-Connect at both ends — the card names Talent or Studio — carrying the performer’s microphone into an armed track in your DAW. The recording path itself is its own guide, and this page assumes it.
Source-Nexus Review, on your master monitor fader, as the place your talkback microphone lives. Selecting your Talkback Microphone and Using the Talkback Switch are the two pages that own that half.
Source-Nexus Mute-On, on the record-enabled track, so that the transport does the muting. Support publishes a Mute-On article written specifically for a remote recording session.
A Source-Nexus Gateway room for the directors and stakeholders, and a virtual webcam if you want them to see as well as hear.
No transport lock — this workflow does not do sync. The performer hears you and you record them; nothing on this page locks their transport to yours or puts picture under the read. If your session needs that, it is timecode, and it is a separate subject that support owns in full: Quick Start Guide for SYNC and LTC/MTC in Source-Connect Studio/Facility.

The setup

Seven steps, in order

Build the recording path first. Launch Source-Connect and establish a secure bidirectional link to the remote voice actor, routing their incoming microphone signal into an armed audio tracking lane inside your DAW. Nothing else on this page is worth setting up until this part records.
Put Source-Nexus Review on the monitor fader. Place the Source-Nexus Review plugin on the final insert slot of your master monitor fader, which is the path the control room hears rather than the path the performer is recorded on.
Map your talkback microphone into Review. Route your local engineering or producer talkback microphone directly into the To Nexus Chat input panel, so that the voice giving notes is carried by the plugin and not by the record path.
Let the transport mute the control room. Add the Source-Nexus Mute-On plugin to your record-enabled audio track and choose the Low_Latency_Monitor_Fix preset, so your local talkback lines go silent when you hit record and the control room cannot bleed into the talent’s headphones or the tracking path.
Open the room the directors will join. Open your browser and log into your Source-Nexus Gateway web room. In the room settings panel, set the video source to your virtual webcam and the primary audio input to your Nexus Broadcast driver node.
Send the link to the people directing. Send the secure Gateway link to your external directors or agency stakeholders. They hear the session and see whatever your virtual webcam is sending, live in their own browsers, with nothing to install.
Track the session. When you hit record, the talent tracks via Source-Connect and the talkback lines are already down. The moment you hit stop, all voice talkback lines open back up, so the note and the discussion happen immediately rather than after somebody has found a button.

What good looks like

How you know it worked

Hitting record silences the control room without anybody reaching for anything, and hitting stop gives the room back.
The performer’s track carries the performance and nothing else — no talkback, no director, no room.
The directors are in a browser, hearing the take and seeing what your webcam is sending, and none of them asked you for a file.
The conversation after a take starts straight away, because the talkback did not need to be re-opened by hand.

When it does not

The things that actually go wrong

Each one has a support article under it. These are the pages to open with the session still live, not afterwards.

Mute-On is gating the wrong thing

The preset in step 4 is one of a published set, and which channel strip it sits on decides what goes quiet. The article written for a remote recording session is the one that matches this workflow rather than a mix session.

Using Source-Nexus Mute-On for a remote recording session

The talent is connected but not recording cleanly

Recording the talent is its own documented procedure, and support publishes it twice: once for the Suite with Pro Tools, and once for Source-Nexus I/O on its own.

How to record your talent with the Source-Nexus Suite and Pro Tools

Your DAW is Nuendo or Cubase

The card’s procedure is written around a generic insert and a generic armed track. The nearest DAW-specific account support publishes is written for Nuendo and Cubase, and its own title says it runs without RTS — the same no-transport-lock shape as the seven steps above.

How to run an ADR session without RTS using Source-Connect in Nuendo/Cubase

You need the performer’s transport locked to yours. That is timecode, and it is a separate subject from everything above — the procedure on this page does not do it. Support owns it: Quick Start Guide for SYNC and LTC/MTC in Source-Connect Studio/Facility, with the SYNC settings and sending and receiving timecode beside it.
The directors cannot hear or see the room. Almost all of that is at their end, in their browser. Send them Source-Nexus Gateway: Common Issues, and check how to invite viewers at yours.
You want the talkback in your hand rather than on the transport. Review’s own Mute/Dim functions and Mute-On’s DIM and Global DIM are the manual half of the same job.

Official source

Where this comes from

The official support hubs

This workflow spans two product sets, and the card names both. The Suite hub carries Review, Mute-On and the Gateway; the Source-Connect 4 Hub carries the recording half.

The Source-Nexus Suite hub