Routling I/O
Virtual audio devices that appear in Windows, so any application can send audio to Routling or take audio from it.
Routling I/O gives you virtual audio devices that show up in Windows like real hardware. Any application can select them - OBS records from Routling, Discord receives a processed mic, a media player sends into your graph.
How it differs from App Capture#
| Routling I/O | App Capture | |
|---|---|---|
| Direction | Both - apps send and receive | Capture only |
| App setup | The app must select the device | Nothing to configure |
| Works with | Any app with a device picker | Apps currently playing audio |
| Use for | Sending audio to an app | Grabbing audio from an app |
If you want audio out of Routling and into another program, this is the only way. App Capture and System Audio cannot send.
The two directions#
Right-click the canvas → Routling I/O:
| Submenu | Meaning |
|---|---|
| Inputs (apps → Routling) | Apps play into these; audio arrives in your graph |
| Outputs (Routling → apps) | Your graph plays into these; apps record from them |
The naming is from Routling's point of view. A Routling Input is something another app treats as its output device.
The driver installs 8 in + 8 out, on every tier. In Windows they appear as Routling IN 1-8 and Routling OUT 1-8; on the canvas the nodes are labelled From Routling N and To Routling N.
Sending audio to another app#
To get a processed microphone into Discord:
- Right-click → Routling I/O → Outputs (Routling → apps) → To Routling 1.
- Connect your processed mic into that node.
- In Discord, set the input device to
Routling OUT 1.
Discord now receives the processed signal, and never touches your interface directly.
Receiving audio from another app#
- Right-click → Routling I/O → Inputs (apps → Routling) → pick a device.
- In the source application, set its output device to the matching
Routling IN N. - Connect the node onward in your graph.
Useful for applications that will not surface in App Capture, or when you want an explicit, stable route rather than a capture that depends on the app playing.
Match the numbers: To Routling 1 on the canvas is Routling OUT 1 in the other application's device list.
Requirements#
Routling I/O depends on the Routling WDM driver being installed. If nodes fail to attach, the log says:
Limits and gotchas#
- 8 in + 8 out, all tiers. Routling I/O is not tier-gated.
- These are secondary devices, so they carry the secondary buffer's latency - see Latency and Buffers. Raise it to Safest if a WDM path crackles.
- Do not create a loop: an app receiving from
Routling OUT 1should not also send back into an input that feeds it. - Set the other application's sample rate to match Routling's where possible.
Related#
- App Capture and System Audio - capture without configuring the app
- Virtual ASIO - many channels to a DAW instead
- Streaming Setup - Routling I/O feeding OBS