Support Center Workflows The Source-Nexus Suite

One studio, one pipeline.

Why the Source-Nexus Suite is the platform for universal audio routing and remote collaboration: the Control Panel, Router, Review, I/O, Mute-On and the Gateway, configured once as a single signal path.

Five applications, one session, no free hands

The review is this afternoon. The client is at home, the director is in another city, and between them they need to hear your timeline, hear you talking over it, and hear the reference track you are going to pull up in a browser halfway through. None of them is going to install anything, and you are going to be busy mixing.

The Source-Nexus Suite is how that becomes one setup instead of five. You make your own virtual audio device and name it. You patch your desktop applications and your talkback microphone into it outside the DAW. You put one plugin on the master fader, one on a track, and one on the channels you want the transport to gate. Then you send a link. Everything after that is playback.

Before you start

Source-Nexus Control Panel Source-Nexus Router Source-Nexus Review Source-Nexus I/O Source-Nexus Mute-On Source-Nexus Gateway
  • Two standalone applications. The Source-Nexus Control Panel is a virtual audio device manager: it is where a custom device comes from. Source-Nexus Router is the patchbay that works outside your DAW, across applications and hardware inputs.
  • Three DAW plugins, in AAX, VST and Audio Unit: Source-Nexus Review for the monitor path, Source-Nexus I/O for a single track, and Source-Nexus Mute-On for the channels you want the transport to gate.
  • A browser, for everybody else. Source-Nexus Gateway is the web room your clients and stakeholders open from a link, with nothing to install at their end.
  • A host DAW with a master fader or monitor bus you can put an insert on, and one spare track for the auxiliary tap in step 4.
  • If routing is new to you, read Basic Routing Concepts first. It is the page that makes the rest of this read like a procedure instead of a list of menus.

Seven steps, in order

  1. Make your own virtual device. Launch the standalone Source-Nexus Control Panel and click the + (Add) button to create a new virtual device. Give it a descriptive name, such as DAW_To_Broadcast, select the channel count you need, and click Done to register it system-wide so it appears in any application’s audio settings.
  2. Sum your desktop sources outside the DAW. Launch the standalone Source-Nexus Router and click Add to build parallel connection lines that combine your local presentation microphone and your desktop applications into a single output path, choosing the device you just created as the destination.
  3. Put Source-Nexus Review on the monitor path. In your project, insert the Source-Nexus Review plugin on the final slot of your Master Fader or Monitor Bus, and map its To Nexus Chat lane to the device you created. That merges your timeline mix, your talkback microphone and your desktop audio into one broadcast line.
  4. Tap a single track with Source-Nexus I/O. For app-to-track work — recording a live web stream, or feeding a standalone player into an auxiliary channel — put the Source-Nexus I/O plugin on a dedicated DAW track. It bridges audio across applications without touching your master fader setup.
  5. Let the transport do the muting. Place Source-Nexus Mute-On on your talkback and communication channel strips and set the primary slot to Broadcaster mode, so that it follows your transport status. When you hit Play or Record it dims your monitors and mutes open microphones, and opens them again when you hit Stop.
  6. Open the room your clients will join. Open your browser, log in to your Source-Nexus Gateway room, and in room settings set the primary audio input to your Nexus Broadcast driver node. Send the room invite link to your clients, directors and stakeholders.
  7. Run the session. Play the timeline. Your audience hears a full-frequency stereo mix and your talkback in their browsers with nothing installed, and when they speak back their voices arrive through the From Nexus Chat node into your headphones or monitors, isolated from your broadcast path and your record tracks.

How you know it worked

  • The device you named in step 1 appears by that name in every application’s audio settings, not just in the Control Panel.
  • One stream carries everything the room needs: the timeline, your voice, and whatever you play from the desktop — and your clients joined it from a link, in a browser, with nothing installed.
  • You have stopped touching a talkback button. Hitting Record silences the control room; hitting Stop gives it back.
  • Client talkback lands in your monitoring and nowhere else. It is not on the broadcast, and it is not on a record track.
  • Nothing in the chain is a temporary patch you will have to remember. Source-Nexus Router saves and reloads a configuration, so the next session starts from the one you just proved.

The things that actually go wrong

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

The device you made is not in the list

A custom device has to be registered before another application can see it, and on Windows the Control Panel and the system talk to each other in their own way. Start at the page for creating one, then the platform note.

Creating a new device on the Source-Nexus Control Panel

The route is built but nothing is arriving

A route has a source device and a destination device, and either end can be pointed somewhere you did not mean. Router has a page for each, and level meters that tell you which half is silent.

Creating a new Route in Source-Nexus Router

Your clients cannot hear the room

Most of it is browser permission and input selection at their end, not routing at yours. The Gateway’s own common-issues page is the first stop, and it is the one to send them.

Source-Nexus Gateway: Common Issues

Where this comes from

The official support hub

Every Source-Nexus Suite guide in one place: Control Panel, Router, Review, I/O, Mute-On and the Gateway, each with its own user guide.

The Source-Nexus Suite hub

The same pipeline, with talent on the end of it

What this looks like when there is a performer to record rather than a mix to present: Source-Connect carries the voice, the Suite carries the room.

Directing a remote voiceover session

The same pipeline, carrying surround

When the master bus is 5.1, 7.1 or an immersive bed, Review has a downmixer and this becomes a fold-down question as well as a routing one.

Streaming spatial and surround mixes to remote clients

All Source Elements workflows

The people already working this way