Routing Pro Tools’ Audio to SYQEL

On SYQEL Desktop, pick App Audio: Pro Tools in the audio source list. No virtual cable is needed. In the web app, or on a system too old for App Audio, send Pro Tools’s output through a virtual audio device instead.

SYQEL Desktop: pick Pro Tools directly

  1. Play something in Pro Tools.
  2. In SYQEL, open the audio source list at the left of the top bar. If Pro Tools isn’t listed, click the refresh button (↻) next to it.
  3. Pick App Audio: Pro Tools. The entry uses the name your system gives the app, so it may include a version or edition.
  4. On a Mac, the first time you pick an App Audio source, macOS asks for permission. Allow it.

You keep hearing Pro Tools as usual. App Audio needs macOS 14.4 or later, or Windows 10 build 19041 or later. On an older Windows build, pick your speakers or headphones instead to capture everything the computer plays.

On Windows, SYQEL hears Pro Tools only if it plays through Windows audio. If nothing comes through, open Setup › Playback Engine and choose Windows Audio Device instead of an ASIO driver.

The web app, or an older system: use a virtual audio device

The web app can only hear a microphone or an audio input, not other apps. Send Pro Tools’s sound into a virtual audio device, then pick that device in SYQEL.

  1. Set up a virtual audio device: BlackHole or Loopback on a Mac, or VB-Cable on Windows. Those guides also show how to keep hearing the music.
  2. In Pro Tools, open Setup › Playback Engine and choose the virtual device (on Windows, avoid ASIO drivers). Pro Tools’ own routing also lets you send just certain tracks or buses to the virtual device.
  3. In SYQEL, pick the virtual device in the audio source list, for example BlackHole 2ch, Loopback Audio or CABLE Output (VB-Audio Virtual Cable). The web app adds ”— system audio” to the name.

On a Mac, with Loopback you can instead add Pro Tools as a source in your Loopback device and leave Pro Tools’s settings alone.

If the Input meter at the right of the stage doesn’t move, see Troubleshooting audio detection.

Did this help? If you’re still stuck, email [email protected].