No Sound From Your Audio Interface? Troubleshooting Checklist

Why is there no sound from my audio interface?

Silence from an audio interface is almost always a selection or level problem, not broken hardware. Microsoft lists the usual reasons for missing sound as the wrong output device, muted volume, audio enhancements interfering, or a driver that is not working.^[1] Interfaces add a few more: a monitor mix knob, a direct monitor button, and separate speaker and headphone levels.

Start with where the sound is missing. That single clue rules out half the list.

Step 1: Is the interface connected and recognized?

Look at the interface's USB light first. On Focusrite's Scarlett Solo 4th Gen it lights green when the computer recognizes the interface, white when it is connected but not recognized, and stays off when it is not connected.^[2] Other brands use similar indicators, so check your manual for what each color means.

1. Check power
   Switch the interface on if it has a power switch, connect its power supply if it needs one, and push the USB plug fully home. Focusrite notes that a loose connector may deliver enough power but no data.^[3]
2. Install and open the control software
   Focusrite says to open its control software at least once with the interface connected, because some of its interfaces will not work until you do.^[3]
3. Allow the driver on a Mac
   macOS can block newly installed third-party system extensions. MOTU's guide explains that if the interface is missing from Audio MIDI Setup or the DAW, you may need to click Allow in the Mac's Security & Privacy settings after installing the driver.^[4]
4. Go direct
   Use the stock cable in another port, no hub or untested adapter.^[3] A Solo 4th Gen needs 900 mA.^[2]

Step 2: Select the interface as your computer's output

Your operating system decides where browser, Spotify and system sounds go, separately from your DAW. If it still points at the laptop speakers or an HDMI monitor, the interface stays silent for everything outside the DAW.

• Windows Open Start → Settings → System → Sound, pick the interface under Output, and make sure the volume is not muted. You can also set it as default under More sound settings → Playback.^[1]
• Windows enhancements If sound is still missing, Microsoft suggests setting Audio enhancements to Off in the device's advanced settings.^[1]
• macOS Choose the interface in System Settings → Sound → Output & Input.^[3] In Audio MIDI Setup you can also select the device, open the Action menu and set it for sound output, and check its sample rate in the Format menu.^[5]

Step 3: Pick the right driver and device inside your DAW

A DAW keeps its own audio device setting, so browser audio working through the interface proves nothing about the DAW. Open the DAW's audio settings and select the interface itself as the output device.

On Windows, choose the interface's ASIO driver. Image-Line tells FL Studio users to pick the native ASIO driver that came with the interface first, or FL Studio ASIO if none exists.^[6] The same manual warns that bridged plugins can steal audio focus and stop playback when the driver is not multi-client; its fix is to deselect Auto close in Audio settings or use FL Studio ASIO.^[6] If the ASIO driver itself misbehaves, work through the Windows ASIO driver troubleshooting guide.

Step 4: Check the output routing in the DAW and interface mixer

If the DAW's master meter moves but nothing comes out, the audio is going to outputs you are not listening to. Most two-channel interfaces send speakers and headphones from outputs 1-2, so route the master there.

In Ableton Live, the list of outputs you can pick depends on the Audio Settings, which you reach through the output chooser's Configure… option.^[7] If channels are disabled there, the master has nowhere to go. Bigger interfaces add their own switches: on MOTU's M6, engaging the 3-4 switch makes the headphone output mirror line outputs 3-4 instead of monitor outputs 1-2.^[4]

Interfaces with a software mixer

Interfaces controlled by an app can mute DAW playback inside that app. In Focusrite Control 2, the Direct tab has faders, mute and solo buttons for the analog inputs and for Playback 1-2, and its final meter shows what reaches your monitor and headphone outputs.^[2] A muted Playback channel or a solo on an input explains silent beats with a working mic. For building separate headphone mixes on purpose, see how to set up a headphone cue mix.

Step 5: Direct monitor and monitor mix knobs

If you hear your microphone or guitar but not the track, a monitor blend knob is usually turned all the way to the inputs. MOTU's M4 has an INPUT MONITOR MIX knob that balances computer playback against live inputs: counterclockwise gives more input, clockwise more computer audio, and MOTU's no-sound checklist says to set it to the center.^[4]

Direct monitoring itself does not mute playback. Focusrite describes it as hearing the inputs without them going through the computer, so without latency and without effects.^[2] If you hear yourself twice, a clean dry signal plus a delayed copy, turn off input monitoring on the DAW track or turn off direct monitor, not both.

Step 6: Cables, speakers, headphones and sample rate

When one output works and the other does not, the fault sits after the interface. Check that the monitors are powered, their own volume knobs are up, and any input selector on the back matches the cable you used.

Cable type matters. Focusrite recommends balanced TRS cables for speaker outputs, since unbalanced connections can bring interference, and warns that headphones with TS or TRRS plugs (common on phone headsets with a mic) are unlikely to work properly; use TRS headphones and a TRS adapter.^[2] For hum and buzz after you get sound back, the cables and ground loop guide goes deeper.

Last, match sample rates. Image-Line recommends that the operating system's output rate and the interface's input and output rates all match, ideally 44.1 or 48 kHz.^[6] If you are still wiring the room, the home studio connection guide shows the full signal path.

No-sound checklist for audio interfaces

Test with a simple source after each step, like a song in the browser and one loop in the DAW, so you know which change brought the sound back.

1. Power and USB
   Interface on, USB light showing a recognized connection, no hub in the way.
2. Operating system output
   Interface selected as the output in Windows Sound settings or macOS Sound settings, volume not muted.
3. DAW device
   Interface selected in the DAW's audio settings, with its ASIO driver on Windows.
4. Routing
   Master routed to outputs 1-2, output channels enabled, nothing muted in the interface's software mixer.
5. Hardware knobs
   Monitor mix centered, speaker and headphone knobs up, direct monitor set on purpose.
6. Speakers and cables
   Monitors powered with their volume up, TRS cables seated, headphones with a TRS plug.
7. Drivers and firmware
   Reinstall the latest driver and control software for your operating system, then restart.