The primary device is the clock the engine runs on. Everything else is a secondary device, kept in step with it.

The primary: built-in clock or ASIO driver#

Routling starts on its built-in clock, which needs no driver and has no inputs or outputs of its own.

Add your ASIO interface's driver with right-click → ASIO Channels → Add ASIO driver… (or the device menu's Use an ASIO driver…) and it becomes the clock. Its channels are then ASIO Channels, the lowest-latency path in Routling. One ASIO driver runs at a time.

Stop ASIO driver in the device menu goes back to the built-in clock and removes the driver's channel nodes (it asks first). If a driver fails to open, Routling also stays on the built-in clock.

Secondary devices#

Windows devices, App Capture and System Audio, Routling I/O and Network In and Network Out streams each run on their own clock. Routling buffers each one and corrects the drift continuously, so they stay in sync with the primary. That buffer is extra latency:

SecondaryBuffer
Windows devicesPreferences → Devices: ~11 / ~21 / ~43 (default) / ~85 ms
App Capture, System AudioAt least ~85 ms, always
Routling I/OA 10 ms driver chunk plus two engine blocks
Network streamsAdapts to the network

Keep anything you play or monitor live on ASIO channels.

Routling converts each Windows device to its own sample rate, so a device set to a different rate still plays at the right pitch. Setting the device's Default Format in Windows (Sound → device → Properties → Advanced) to Routling's rate skips that conversion.

Missing and renamed devices#

A device that disappears stays on the canvas as a disconnected placeholder and reconnects when it returns. Devices are matched by a stable ID, so Windows renaming one does not break a session. Refresh Devices (right-click the canvas) rescans and reconnects.

ASIO® is a registered trademark of Steinberg Media Technologies GmbH.