Routling Wiki Features FAQ Join the Waitlist

Per-Application Routing

Send different applications to different destinations - music to speakers, game to headphones, calls to both.

intermediate

Windows gives every app one output device. Routling lets each application land somewhere different.

The goal#

  Spotify   ──▶ Speakers
  Game      ──▶ Headphones
  Discord   ──▶ Headphones + Stream
  Browser   ──▶ Headphones only

Two ways to get an app's audio#

MethodWhen
App Capture and System AudioThe app is playing; nothing to configure
Routling I/OYou want an explicit, stable route, or the app does not appear in capture

App Capture is easier. Routling I/O is more deliberate and survives the app not currently playing.

Build it with App Capture#

1. Open your interface#

Open Device, pick your ASIO interface.

2. Add destinations#

Right-click → ASIO Channels → Output:

  • Your speaker channels
  • Your headphone channels

3. Capture each application#

Right-click → App Capture for each program you want to route. Each must be playing audio to appear in the list.

You get one node per application.

4. Wire them#

SpotifyGameDiscordSpeakersHeadphones

Connect each capture node to whichever destination you want. One source can feed several destinations - Discord to both headphones and your stream.

5. Balance#

Scroll each wire to set its level. Because gain is per connection, Discord can be loud in your headphones and quiet in your stream at the same time.

Sending an app somewhere specific#

To route audio into an application - a processed mic into Discord - use Routling I/O:

  1. Right-click → Routling I/O → Outputs (Routling → apps) → To Routling 1.
  2. Connect your processed source into it.
  3. In the target application, select the matching Routling device as its input.

Independent volume per destination#

The main benefit. One source, several destinations, separate levels:

0 dB-12 dBMusicHeadphonesStream

Comfortable in your headphones, quiet in the stream, one source.

Add a Volume Knob if it is a level you keep adjusting, or a Ducker to make music drop automatically under your voice.

Gotchas#

  • App Capture needs the app to be playing to show up. Start playback first.
  • Do not capture an app and System Audio together - that app arrives twice.
  • Captures are secondary devices, so they carry the secondary buffer latency. See Latency and Buffers.
  • If an app is not running when a session restores, its node waits as a placeholder and reconnects when the app starts.