Plug the interface into your computer with the cable it shipped with, install the manufacturer’s current driver before you do anything else, then select that driver by name inside your recording software. Skip ASIO4ALL or a generic driver unless your interface genuinely has no dedicated one.
Here is the number worth knowing before you start. A 128-sample buffer at 44.1kHz works out to about 2.9 milliseconds of latency in one direction, the starting point most driver guides recommend for live monitoring.
By the end of this guide, you will know the exact connection order, which driver to pick on Windows and Mac, and how to fix the two most common problems, no sound and crackling audio.
This guide draws on manufacturer documentation and technical driver comparisons. It does not rest on bench testing, so I name the source whenever I share a specific figure.
The Short Version
- Download and install the manufacturer’s current driver before plugging anything in
- Connect the interface with its included USB cable, directly into your computer, not a hub
- Set the interface as your system’s default input and output device
- Open your DAW or recording app and select the interface’s own driver by name, not a generic one
- Set your buffer size to 128 or 256 samples and start recording
The rest of this guide covers why each step matters and what to do when one of them goes wrong.
Why Does Driver Order Matter?
Because plugging in an interface before installing its driver often means Windows loads a generic driver automatically, and that generic driver can keep conflicting with the real one even after you install it correctly.
A detailed 2026 driver guide from iTechGuides states the rule plainly. The manufacturer’s current Windows driver is normally the best first choice ASIO driver for a supported audio interface, ahead of generic options like the Steinberg built-in ASIO driver or ASIO4ALL.
Mac users get this for free in most cases. Audio Technology’s breakdown of CoreAudio confirms it handles exclusive device access and low-latency audio through its own architecture, with no separate driver install required for most class-compliant interfaces.
ASIO vs WDM, What Is the Actual Difference?
Both get audio to your computer. Only one gives you real control over latency.
AudioRecording.me’s technical comparison puts it simply. With an ASIO driver you get to choose exactly how much latency you accept, through the buffer length setting, while WDM just does its best with whatever Windows decides.
That is why every DAW on Windows asks you to pick an audio driver type, and why ASIO is almost always the right choice once your interface’s driver is installed. WDM remains useful mainly as a fallback for interfaces with no ASIO driver of their own.
My take as a musician. If your interface shipped with its own ASIO driver, use it. Reach for ASIO4ALL only when the manufacturer genuinely offers nothing else 🎸
What Buffer Size Should You Use?
Smaller buffers mean lower latency but demand more from your computer. Larger buffers are more stable but introduce a delay you can hear while monitoring.
iTechGuides recommends 64 to 256 samples as a useful starting buffer for live software monitoring or recording, raising it only if clicks, pops, or dropouts appear.
| Buffer size | Latency at 44.1kHz | Best for |
|---|---|---|
| 64 samples | ~1.5 ms | Tracking a performance live, needs a fast computer |
| 128 samples | ~2.9 ms | General recording and monitoring, the common starting point |
| 256 to 512 samples | ~6 to 12 ms | Mixing, or any computer that struggles at smaller sizes |
The math behind the table is straightforward. Buffer time in milliseconds equals samples divided by sample rate, multiplied by 1000, according to iTechGuides’ own formula.
How Do You Connect the Hardware Itself?
Five steps, done in order, avoid almost every common first-time problem.
- Install the driver first. Download it from the manufacturer’s own support page, not a third party mirror
- Restart if the installer asks you to. Skipping this step is a common reason the interface doesn’t appear correctly
- Plug the interface directly into a USB port on your computer. Avoid USB hubs, which can introduce power or bandwidth issues
- Set it as your system default input and output. On Windows, through Sound settings. On Mac, through System Settings, Sound
- Open your DAW and select the interface’s own driver by name in the audio settings, not “Primary Sound Driver” or a generic option
Our Focusrite Scarlett 2i2 review and other interface reviews on the site cover model-specific driver quirks, worth checking if you own one of those exact units.
Why Do I Get No Sound At All?
Almost always one of three causes, checked in this order.
- Wrong driver selected in your DAW. Open your software’s audio settings and confirm the interface’s own driver is chosen, not your laptop’s built-in speakers
- Interface not set as the system default. Check your OS sound settings separately from your DAW settings, both need to point at the interface
- Another app is holding exclusive access. On Windows, an app using WASAPI Exclusive mode can block every other app from using that device, according to Undisclosed Sounds’ driver breakdown. Close other audio apps and try again
Why Does My Audio Crackle or Pop?
Almost always a buffer size set too low for your computer.
iTechGuides’ fix is the standard one. Raise the buffer, moving from 64 to 128, then to 256 samples, testing after each change until the crackling stops.
A real forum report from Gearspace illustrates the tradeoff well. One user found their WDM driver stayed fast and stable at a 2.9 millisecond buffer while their ASIO driver injected an occasional pop or click at the same setting, on the exact same hardware. Neither driver type guarantees stability, your specific computer and interface combination decides the right buffer.
If raising the buffer doesn’t help, close background apps, plug directly into a USB port instead of a hub, and confirm your laptop is on AC power rather than battery, since some systems throttle USB performance on battery.
Interface Shows Up But Sends No Signal, Why?
This is a different problem from no sound at all, and it has a different checklist.
If your DAW sees the interface and the meters still sit dead flat, work through these in order.
- Wrong input selected on the track itself. Most DAWs require you to pick an input channel per track, separate from choosing the interface as your overall driver
- Gain turned all the way down. Check the physical gain knob on the interface, not just software gain
- Phantom power off for a condenser mic. A condenser mic produces no usable signal at all without 48V phantom power switched on
- Front panel input disabled a rear XLR input, or vice versa. Several interfaces share one preamp between a front instrument jack and a rear mic input, and plugging into one silently disables the other
That last one trips up more people than any other item on this list, since the interface gives no warning when it happens. Our Scarlett 2i2 review covers exactly this quirk on that specific model.
Does the Setup Differ Between DAWs?
The core steps stay the same. Only the menu location changes.
Every major DAW, Ableton Live, Reaper, Logic Pro, Pro Tools, Cubase, asks for the same three things in its audio preferences panel. The driver or audio engine type, the specific device by name, and the buffer size.
Sound On Sound’s own driver optimization guide notes that some DAWs, naming Sonar specifically, historically got notably better results from WDM drivers than other software did on the same system. That is the exception rather than the rule today, but it explains why a setting that works perfectly in one DAW can need adjustment when you switch to another on the same computer.
If you record in more than one DAW, check the audio preferences in each one separately rather than assuming a setting carries over.
Should You Connect a Mic Before or After Powering On?
After, specifically for condenser mics.
The safer order is to connect your mic to the interface first, then turn phantom power on afterward, rather than plugging a mic into a channel that already has 48V live. Many interfaces and mics tolerate hot-plugging fine, but the safer habit costs nothing and avoids the rare case where it does not.
Dynamic mics have no such requirement, since they need no phantom power at all.
Which Driver Setup Should You Actually Use?
Match the driver choice to what your interface actually offers.
- Interface has its own ASIO driver (most Focusrite, SSL, Universal Audio, Audient gear). Install and use it, skip everything else
- Interface has no dedicated ASIO driver. Try the Steinberg built-in ASIO driver first, then ASIO4ALL if that doesn’t work
- On a Mac. Most class-compliant interfaces need no separate driver at all, CoreAudio handles it
- Audio crackles at a small buffer. Raise it in steps of 64 or 128 samples until it clears
Haven’t picked an interface yet? Our best 2 channel audio interface guide covers picks that ship with reliable, well-documented drivers.
Did You Know 🤯
On Windows, an app running in WASAPI Exclusive mode can take total control of your audio device, meaning Windows literally cannot send any other sound through that device until the app releases it, according to Undisclosed Sounds.
Audio Interface Setup FAQ
Do I need to install a driver on Mac?
Usually not.
Most class-compliant interfaces work through CoreAudio with no separate driver. Check your specific model’s requirements to confirm.
Can I use a USB hub?
Not recommended.
Plug directly into your computer’s USB port to avoid power and bandwidth issues a hub can introduce.
What’s the difference between ASIO4ALL and a manufacturer driver?
ASIO4ALL is generic.
A manufacturer’s own driver is tuned for that specific hardware and should always be tried first.
Does a smaller buffer always sound better?
No.
A smaller buffer only reduces latency. It demands more from your CPU and can cause crackling if your system can’t keep up.
Why does my interface disappear after sleep?
A common USB power management quirk.
Unplug and reconnect the USB cable, or restart your DAW, to force your computer to redetect it.
So install your driver first, pick it by name in your DAW second, and start recording 🎶
Related Posts
Here is a list of interface posts you can consider as alternatives.
