A remote cast, one per track.

You are recording a panel. The guests are in different places, none of them is an engineer, and the thing you will regret in the edit is having them summed together: one person too loud, one room too live, and no way to treat either of them on their own.

Source-Connect does this as a set of separate connections rather than a conference call. Each guest runs Source-Connect Talent and accepts a request from you, they all hear each other with no routing at their end, and you land each one on a track of their own. The recovery half runs underneath: if somebody’s line stutters, the repair happens after the take instead of during it.

1. Get the studio end ready first. This workflow assumes Source-Connect Studio is already configured to record a remote Talent to a DAW track and to use Auto Restore / Replace, and that every guest is on your Source Elements contacts list before the session starts.
2. Have every guest log in and wait. Each guest launches Source-Connect Talent, logs in, and checks that their microphone and headphones are the selected devices in Settings. If you have them on your contacts list, they do nothing else but accept your request when it arrives.
3. Request every connection. From Source-Connect Studio, request a connection to several contacts at once, or one at a time, leaving the Auto Restore / Replace option enabled on every one. Everybody who connects hears everybody else, with no extra routing at your end or theirs.
4. Give each guest an aux of their own. Create one mono aux track per guest and insert a Source-Connect I/O plugin on each. Rename each plugin instance after the guest it belongs to, so choosing it from a list later is unambiguous.
5. Send each aux to its own record track. Route the output of each guest’s aux track through a mono bus to a dedicated audio track, so that each guest is captured on their own.
6. Assign the outputs in the connections tab. In the Source-Connect application’s connections tab, set each guest’s output to the named Source-Connect I/O plugin instance you created for them.
7. Build your own talkback and record path. Route your microphone to a dedicated record track and insert another Source-Connect I/O plugin on it, selecting the Thru option if you want to monitor through that track. Set this instance as the input for every guest, so that everyone hears you and your own voice is recorded alongside theirs.
8. Record, then let the repair finish. Record the session normally. When tracking ends, disconnect from each guest but ask them to stay online in Source-Connect long enough for Auto Restore to repair any dropouts and, if you want it, for Auto Replace to complete.

• The guests are connected but the tracks are silent. That is the routing in steps 4 to 6, not the connection: the plugin instance assigned in the connections tab and the plugin instance on the aux have to be the same one. Support publishes the record-incoming-signal procedure per DAW, starting with Pro Tools, and also Logic Pro and Cubase and Nuendo.
• You are doing this again next week. The overall settings carry an option to remember sessions rather than always reopening the defaults, so this routing comes back instead of being rebuilt. Configuring your Settings in Source-Connect Studio/Facility is where those live.
• You want a worked example rather than a procedure. Support carries one, written for five actors on the legacy 3.9 generation: Example Use: Source-Connect with 5 actors. Read it as a scenario, not as a settings list.
• Your guests are in a browser instead. If the cast is joining a web room rather than running an application, the Gateway has its own procedure for keeping their inputs apart: Recording separate inputs with Source-Nexus Gateway.