ASIO4ALL Device Aggregation and Clock Sync
ASIO4ALL can present selected audio channels from several Windows devices to one ASIO host. That can give a DAW access to a separate input and output, but keeping two devices aligned for an entire recording depends on how their sample clocks are synchronized.

In this guide
What ASIO4ALL device aggregation does
ASIO4ALL device aggregation lets one ASIO host use channels from more than one Windows audio device at the same time, for example a USB microphone for input and your built-in headphone output for playback. It works, but two separate devices only stay aligned over a long recording when their sample clocks are synchronized. Without a shared clock, drift can cause clicks, gaps and timing errors.
A DAW normally talks to one ASIO driver at a time. ASIO4ALL v2 sits on top of the existing WDM drivers and can present selected inputs and outputs from several devices as a single driver. That flexibility is one of the main reasons home producers and podcasters use it, and this guide explains how to set it up, what to expect and how to test it.
Typical reasons to combine devices
- Recording with a USB microphone while monitoring through the computer's headphone jack.
- Using a USB headset output alongside a separate input device.
- Adding a second set of inputs for a short, simple session.
Build the smallest useful device list
Start small. Every device you enable adds channels, and every extra device adds another clock that may not match the others. A short list makes channel names easier to identify in the DAW and makes problems easier to isolate.
Step by step
- Select ASIO4ALL v2 as the driver in your DAW's audio settings.
- Open the ASIO4ALL control panel from the DAW and switch to advanced mode.
- Expand the device entries to see the available inputs and outputs.
- Enable the recording input and the listening output you plan to use.
- Leave extra webcams, display audio outputs and unused interfaces disabled for the first test.
- Return to the DAW, assign the input to a track and the output to the master bus, then play and record a short test.
The publisher's advanced configuration page explains the control panel in more depth.
Tip: Disable monitors that carry audio over HDMI or DisplayPort unless you actually listen through them. They add channels to the list and can make it harder to find the output you want.
How aggregated channels appear in your DAW
Once several devices are enabled, the DAW sees one combined list of inputs and one combined list of outputs. The names usually reflect the underlying Windows devices, but the exact labels depend on the host.
When the channel list changes
Enabling or disabling an item can change the number and order of channels the DAW sees. If the track list still shows the previous channels, reopen the DAW and assign the new inputs and outputs again. Some hosts only rebuild their channel list when the audio engine restarts.
- Note which device each input belongs to before you start recording.
- Re-check input assignments in saved projects after changing the device list.
- Rename tracks after their source so a later change is easy to spot.
| Setup | What it gives you | Main risk |
|---|---|---|
| USB mic in, built-in headphones out | Recording and monitoring without a dedicated interface | Two separate clocks over long takes |
| Single device, input and output | The simplest and most stable path | Limited channel count |
| Two interfaces sharing a digital clock | More inputs with a common timing reference | Needs equipment that supports clock selection |
| Two unrelated USB devices for recording | Extra inputs on paper | Drift between recorded tracks |
Understand how clock drift sounds
Two devices set to 48 kHz can run at slightly different physical speeds. Over time, one device supplies or consumes more samples than the other. With enough drift, the streams can fall out of alignment or produce intermittent clicks, gaps and dropped audio.
Why it often goes unnoticed at first
The difference is tiny in any single second, so a quick sound check usually sounds fine. The effect builds over minutes. That is why a setup that passes a 30-second test can still cause trouble halfway through a long podcast or live take.
Drift is not the same as a fixed offset
A take that lands the same distance late every time is a constant offset, which is a latency question. A take that starts aligned and gradually moves out of alignment is drift. The two need different fixes, so it pays to know which one you have.
Watch out: Clicks from drift can sound similar to buffer-related crackles. If the noise appears even with a single device, look at the buffer and system load first, using the crackling guide.
Test for the length of the session
A brief sound check verifies that signal passes. If the actual job is a long take, run a longer rehearsal at the planned sample rate, buffer and channel count. Listen to the start and end of the saved file, not just the beginning.
A simple drift test
- Set the project to your planned sample rate and buffer size.
- Feed the same reference signal, such as a clap or click, to inputs on both devices.
- Record for as long as your real session will run.
- Place a marker at the first reference sound and another at the last.
- Compare how the alignment between the two tracks changes from the first marker to the last.
If the tracks line up at both ends, the setup is holding together. If the gap grows, you are seeing drift. The publisher's troubleshooting page is a useful reference when results are inconsistent.
What to do when drift returns
If drift comes back, reduce the setup to one device with the inputs and outputs you need, or use hardware with documented clock synchronization. For many podcasters, a USB microphone with its own headphone output avoids aggregation altogether; see the USB microphone guide.
Latency compensation is a separate tool
A constant recording offset is a separate measurement. ASIO4ALL's latency compensation adjusts the reported timing and cannot make two separate clocks run at the same rate. The publisher notes it uses the largest respective compensation value across devices in a multi-device setup. The latency compensation guide walks through measuring it, and the publisher's latency compensation page has the reference method.
Note: Write down the devices, sample rate, buffer and channel assignments of any setup that passes a long test. That record makes it quick to restore after an update or a change of hardware.
Buffer size and a pre-session checklist
Combining devices asks Windows and ASIO4ALL to keep several streams moving together, so a buffer that is stable with one device can be too tight with two. If you hear crackles only after enabling a second device, raise the buffer one step and test again before changing anything else.
Know what the buffer costs you
Buffer time is samples divided by sample rate, multiplied by 1000. At 48 kHz, 128 samples is about 2.7 ms, 256 samples about 5.3 ms and 512 samples about 10.7 ms. For a spoken-word session where nobody plays an instrument live, a larger buffer is often a sensible trade for stability. For live monitoring of an instrument, start low and step up only as far as you need.
Before an important recording
- Disable every device the session does not need.
- Confirm all enabled devices run at the project sample rate.
- Check input and output assignments in the DAW after any change.
- Run a rehearsal as long as the real take and check both ends of the file.
- Keep a single-device fallback ready in case drift or dropouts appear.
A few minutes spent on this list is cheaper than discovering misaligned tracks after a guest has gone home.
Frequently asked questions
Yes. ASIO4ALL device aggregation can present inputs and outputs from several Windows devices to one ASIO host. Long recordings stay aligned only when the devices share a clock.
Each device has its own clock, and two clocks set to the same rate can still run at slightly different speeds. USB alone does not synchronize them.
No. Latency compensation shifts recordings by a fixed amount. Drift changes over time, so it needs a shared clock or a single-device setup.
Enabling or disabling devices in ASIO4ALL changes the number and order of channels. Restart the DAW's audio engine or reopen the DAW and reassign inputs and outputs.


