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 BitWig Studio.


Sending Audio from BitWig Studio

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

Click to enlarge

This workflow is the simplest way to get up and running with BitWig alongside Sessionwire. Simply placing the Sessionwire Send plugin on the Master channel of a BitWig project 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 channel of the BitWig project. 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 BitWig.


Sending and Receiving Audio within BitWig Studio

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

Click to enlarge

This workflow will allow the sending of audio from a BitWig project while simultaneously receiving remote HQ audio directly into a BitWig project.

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 audio tracks intended to be streamed to the Remote connection in Sessionwire are included in a Group within the BitWig project. The HQ Audio Input is set to the Sessionwire Plugin - Sessionwire will receive audio from the Send plugin on the Group's governing track. The HQ Audio Output is set to the Sessionwire Receive plugin which is inserted on an audio track in the BitWig project that is routed to the Master track. This routing will make feedback loops or delays between local and remote sessions a non-issue.

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


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 BitWig.

A talkback mic is plugged into any channel of an audio interface and the input of the SW TB Send track 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 Master bus.

All high quality (working) audio and MIDI tracks in the BitWig session are a part of the "MIX" Group 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 BitWig via the Sessionwire Receive plugin, and sent out the Master bus.

To record HQ audio from the remote connection, input of the target track can be set to the SW HQ Rcv track or the output of the Sessionwire Receive Device.

Did this answer your question?