DAW Integration
Connect a DAW to Routling so you can record routed audio, process DAW output, or use the DAW as a live effects rack.
Three ways to combine a DAW with Routling, depending on which direction the audio needs to flow.
Which approach#
| You want | Use |
|---|---|
| Many channels, both directions, lowest latency | Virtual ASIO |
| A simple stereo path in or out | Routling I/O |
| The DAW to own the interface entirely | Neither - see below |
Approach 1 - Virtual ASIO#
The main option. Routling appears as an ASIO device in the DAW, giving up to 16 channels each way.
Setup#
- Open your interface in Routling as the primary device.
- Right-click canvas → Mixing & Effects → Virtual ASIO.
- In the DAW's audio settings, select Routling Virtual ASIO.
- The Virtual ASIO node moves from waiting to ready.
Recording routed audio into the DAW#
Connect sources to the node's To DAW ports:
Each Routling channel arrives on the matching DAW input, so you can arm separate tracks and record them independently while everything continues to run live.
Processing DAW output through Routling#
Connect the node's From DAW ports onward:
The DAW plays normally; Routling handles final processing and where it goes.
Both at once#
Send DAW output into Routling and record Routling's mix back - useful for monitoring a live setup through DAW plugins while capturing the result.
Approach 2 - Routling I/O#
Simpler when you only need stereo. Routling appears as an ordinary Windows device, so it works with DAWs that are not using ASIO.
- Right-click → Routling I/O → Outputs (Routling → apps) → To Routling 1.
- Connect your mix into it.
- In the DAW, set that as an input device and record it.
Higher latency than Virtual ASIO - it goes through the secondary buffer. Fine for recording, less good for live monitoring. See Latency and Buffers.
Approach 3 - let the DAW own the interface#
Sometimes the right answer is not to route at all. If the DAW needs exclusive low-latency access to your interface, give it the interface and use Routling for everything else, or close Routling's device while tracking.
ASIO devices are usually exclusive - Routling and the DAW cannot both hold the same interface directly.
Sample rate#
Routling and the DAW must agree. A mismatch means the DAW refuses the device or resamples, adding latency and quality loss.
Set both to 48 kHz unless a project needs otherwise. Change Routling's rate from the device menu.
Latency#
Live monitoring through a DAW means the round trip is: interface in → Routling → Virtual ASIO → DAW plugins → back. Each stage adds delay.
If you are playing an instrument and it feels late:
- Lower Routling's buffer size.
- Lower the DAW's buffer size.
- Bypass lookahead plugins in the DAW while tracking.
- Or monitor directly through Routling - mic → FX Module → headphones - and let the DAW record without being in the monitoring path.
That last option is usually the right one. See Latency and Buffers.
Related#
- Virtual ASIO - the node in detail
- Routling I/O - the stereo alternative
- Latency and Buffers - the round trip
ASIO® is a registered trademark of Steinberg Media Technologies GmbH, registered in Europe and other countries.