There are many use cases and workflows for each DAW when integrating Sessionwire for remote collaboration. We have created a basic template for each DAW to give an idea of what routing should look like in order to avoid feedback loops between users connected in Sessionwire Studio.

Each user may be using a different DAW or may/may not be using an audio interface - therefore, each user will need to reference the correct signal flow diagram for their particular DAW and setup.

Below are common setups when using Sessionwire alongside Studio One.


Sending Audio from Studio One

(To send audio from Studio One to a peer and listen to their remote audio)

Click to enlarge

This workflow is the simplest way to get up and running with Studio One alongside Sessionwire. Simply placing the Sessionwire Send plugin on the Master Fader of a Studio One session will produce the same results as in the downloadable template.

Sessionwire's Talkback Input is set to a webcam (or an audio interface with a microphone plugged into channel 1 or 2) and the Talkback Output is set to the system audio output device - this is identical to how any video conferencing software would be set up.

Sessionwire's HQ Audio Input is set to Sessionwire Plugin - Sessionwire will receive audio from the Send plugin on the Master Fader of the Studio One session. The HQ Audio Output is set to the system audio output device - this way any audio streamed from the remote end of the call is sent straight out of the output device. No need to route incoming audio into Studio One.


Sending and Receiving Audio within Studio One

(To send audio to a peer and receive remote HQ audio in Studio One)

Click to enlarge

This workflow will allow the sending of audio from a Studio One session while simultaneously receiving remote HQ audio directly into a Studio One session.

Sessionwire's Talkback Input is set to a webcam (or an audio interface with a microphone plugged into channel 1 or 2) and the Talkback Output is set to the system audio output device - this is identical to how any video conferencing software would be set up.

All high quality (working) audio in the Studio One session is routed to the Master channel which has the Sessionwire Send plugin instantiated, sending high quality audio to Sessionwire's HQ Audio Input. High quality audio being sent by the remote end is routed into Studio One via the Sessionwire Receive plugin, and sent out Outputs 1/2, avoiding the Master channel with the Send plugin.

To record HQ audio from the remote connection, route the output of the SW HQ Rcv track to any unused bus and selecting the input of the destination track as that same bus.


Using an Audio Interface for All Audio

(Users with advanced hardware setups)

Click to enlarge

In this workflow, it is assumed that an audio interface is being used as the input and output device of Studio One. A talkback mic is plugged into any channel of an audio interface and the input of the SW TB Send channel is set to the corresponding channel (circled in image above).

Local talkback is routed through the Sessionwire Talkback Send plugin to Sessionwire Studio's Talkback Audio Input. Remote Talkback Audio is returned via the Sessionwire Talkback Receive plugin and routed to the Stereo Out bus, avoiding the Main bus and the Sessionwire Send plugin.

All high quality (working) audio in the Studio One session is routed to the "Main" bus which has the Sessionwire Send plugin instantiated, sending high quality audio to Sessionwire Studio's HQ Audio Input. High quality audio being sent by the remote end is returned to Studio One via the Sessionwire Receive plugin, and sent out the "Stereo Out" bus, avoiding the "Main" bus with the Send plugin.

To record HQ audio from the remote connection, simply use Studio One's routing to select the SW HQ Rcv track as the input of the destination track.

NOTE: In the Studio One template, both the Main and Stereo Out busses are routed to hardware output 1/2 using the I/O matrix - it is necessary to have both in order to avoid starting feedback loops between users on a Sessionwire Studio call.

Did this answer your question?