VO Weekly Workflow: Loopback I/O (Part 2)

Studio One uses a "matrix" approach to handle Input and Output routing. Here we see in the Input tab that the connected interface - an SSL2+ (MkI) - has both the hardware channel inputs and the "Loopback" channels. (Note - the Loopback channels had to be added manually. Studio One did not "see" those natively).
Studio One uses a “matrix” approach to handle Input and Output routing. Here we see in the Input tab that the connected interface – an SSL2+ (MkI) – has both the hardware channel inputs and the “Loopback” channels. (Note – the Loopback channels had to be added manually. Studio One did not “see” those natively).

Before we start trying to record different streams of audio, it’s helpful to understand a bit about I/O routing. As I mentioned in last week’s email, “I/O” stands for “Input/Output.” The actual I/O routing determines how each piece of software connects with different audio signals. Some signals – like that from the microphone – flow “into” the app, while anything that is broadcast from the app is flowing “out.” While this may seem like a simple concept, it can get a bit confusing when we start sending the output from one app to another.

If you’ve used Zoom, you’ve had to route audio into and out of that application. The “I/O” in Zoom sessions has become very user-friendly for consumer-level devices. Zoom prompts “Select a Microphone” and “Select a Speaker” when starting a session. Since most VO’s work with an audio interface attached to their computer, Zoom is actually sending all of the inputs from an interface into the Zoom session. If you have a two channel interface like a Scarlett 2i2 Gen4, Zoom will use the input from both of those sources. On the other hand, Source-Connect not only sees the Scarlett, but will require you to specify whether you want Channel 1, Channel 2, or even the Loopback Channels if they exist. This is a good example of how different applications manage the I/O differently.

Since I began talking last week about Loopback being used in Audacity, let’s start with that recording environment. And…let’s just say that the controls are a bit lacking. As of late 2025, the routing seems to be a holdover from the early days of this app. You can make these controls visible on the main Audacity window by going to the “VIEW” menu, moving through “Toolbars” and selecting “Device Toolbar.” This places small pull-down menus on the main screen. These show the current audio driver (Core Audio for MacOS), the Mic and Speakers selection, but most importantly the “1 – Mono”/”2 – Stereo” selection. These choices can also accessed through the Audacity Settings/Preferences, under the Audio Settings tab. If you have an interface with Loopback, “3” and “4” only show the number with no name for that input.

Audacity control layout showing the "Device Toolbar" as explained above. Here, the Input Channel menu has been activated. You can see how Audacity names the first two channels, but has nothing in the name for Channels 3 and 4. That does not mean there's no input - just that Audacity provides a generic label.
Audacity control layout showing the “Device Toolbar” as explained above. Here, the Input Channel menu has been activated. You can see how Audacity names the first two channels, but has nothing in the name for Channels 3 and 4. That does not mean there’s no input – just that Audacity provides a generic label.

Audacity always routes the input sequentially. If you have only 1 track recording, that will always be capturing the audio coming from Channel 1 of the audio interface. If your mic is attached to Channel 2 of your interface (as with the new Gen4 Solo), then you will not capture any audio. In order to capture audio from Channel 2, you need a second mono track actively recording (or the “right” channel of a stereo track). Since Loopback audio shows up under Channels 3 and 4, there must be a corresponding track. You need to be recording into 4 mono tracks (or two stereo tracks).

Audacity “Preferences” (Settings) panel, under the “Audio Settings” tab. You can also view the Device Settings through the master Preferences/Settings panel.

Luckily, Audacity’s I/O routing is the most arcane. With Twisted Wave, when you go into Twisted Wave “Settings” panel, then the “Devices” tab, there will be a button for “Select Channels”. Here you can see all the inputs and Outputs properly named, and simply drag them into the desired order.

Twisted Wave's I/O panel is accessed through Twisted Wave Preferences/Settings, under the "Devices" tab, by pressing the button for "Select Channels." The channels can then be dragged into position. So if you want the input from a microphone connected to Channel 2, you simply drag that into the first Input position. This saves the day for anyone using a Focusrite Solo Gen4.
Twisted Wave’s I/O panel is accessed through Twisted Wave Preferences/Settings, under the “Devices” tab, by pressing the button for “Select Channels.” The channels can then be dragged into position. So if you want the input from a microphone connected to Channel 2, you simply drag that into the first Input position. This saves the day for anyone using a Focusrite Solo Gen4.

On multitrack music DAW’s, such as ProTools or Studio One, there will be some sort of a grid matrix where the Inputs and Outputs are designated once the audio interface has been selected. Adobe Audition is a bit of hybrid, as it has both a waveform (single-track) mode and a multitrack option. All individual inputs – both physical channels and the “virtual” loopback channels – are accessible when using multitrack.

Input/Output routing panel in Pro Tools. Similar to the Studio One routing shown above, this clearly shows options for mono and stereo inputs into this multitrack music recording software.
Input/Output routing panel in Pro Tools. Similar to the Studio One routing shown above, this clearly shows options for mono and stereo inputs into this multitrack music recording software.

It’s good to have an understanding of where these Inputs and Outputs are accessed in your software of choice. In the next post, we’ll look at how these can be used to separate and capture different parts of our session audio.


Have you tested your studio’s audio quality to make sure it meets professional standards? For a free review of your vocal recordings, please use the upload tool on my Audio Review page.

If you have found this resource helpful or inspiring, please feel free to share or link to this resource using one of the buttons below. If you would like to receive these weekly posts directly to your email, you can sign up here

3 Responses to “VO Weekly Workflow: Loopback I/O (Part 2)

  • Jim,

    Just an FYI. I have an RME interface on Windows 10 with an ASIO driver. I also have Source-Connect v3.8 and v4.0. While v3.8 sees my interface via the ASIO driver, v4.0 does not, only seeing Windows Control Panel>Sound>Record and Playback Tabs. After much back and forth with Source-Connect Support, this is what they finally said:

    “Full ASIO support for Source-Connect v4 is pending actually. I think that is why you are seeing what you are seeing and why you do not see the full RME channel list.

    Running via the Windows sound control panel will be required until we have a version with full ASIO support released.

    I do not know the exact timeline for that version but it is already in the dev timeline.

    For Source-Connect v3 it actually only uses ASIO device directly. The same third-party drivers that work for 3.9 (NB from me: there is no 3.9 for Windows, only 3.8) will work for 4 as well. FLEXASIO and ASIO4ALL.”

    Bruce Hayward

    • Thanks for that. I know some of the delays in shipping Source-Connect 4 had to do with Windows audio drivers. Hopefully they get the ASIO performance dialed in. That’s a tough one to solve.

  • Fortunately, with RME’s multi-client drivers and TotalMix, I can easily run S-C v4.0 through Windows Control Panel>Sound until they do, without having to use FLEXASIO or ASIO4ALL or the Source-Connect I/O (Link) plug-in (which doesn’t work with all programs. Then again, given most studios are resistent to change, I’m sure v3x is going to be in use for quite some time, plus there’s Source-Elements free “bridge” service between v3x and v4.0.