How to Connect Xlr Interface to Pc for Streaming: Step-by-Step Guide (2026)

Connecting an XLR microphone through an audio interface is the single biggest upgrade most streamers can make. A condenser or dynamic mic on a proper interface gives you cleaner preamps, real gain control, and latency low enough to monitor your voice in real time. This guide walks you through the full process: physically wiring the interface, configuring Windows so OBS Studio sees it, setting gain levels, and troubleshooting the problems that trip people up most often. By the end, your XLR mic will be live in OBS with direct monitoring enabled and no audible lag.

Prerequisites: a Windows 10 or 11 PC, OBS Studio 30 or newer installed, and an XLR microphone with its cable. Plan for about 30 minutes total, most of which is software configuration rather than wiring.

Before You Start

Gather everything before you plug anything in. Half of failed setups come from missing one small item, like a power cable or a USB port that can’t deliver enough current.

Step-by-Step

Step 1: Connect the Microphone to the Interface (5 minutes)

Plug the female end of the XLR cable into your microphone and the male end into Input 1 on the interface. The connector only seats one way; push until the latch clicks. If you’re using a condenser mic, locate the 48V switch (labeled “48V” or “Phantom”) on the interface’s top or rear panel and flip it on after the mic is connected. Never connect or disconnect an XLR cable with phantom power already engaged — it can produce a loud pop and, rarely, damage the mic. Dynamic mics like the Shure SM7B or MV7 need phantom power off. Mute your speakers or wear headphones before switching 48V on, just in case.

Step 2: Connect the Interface to the PC (2 minutes)

Plug the USB cable into the interface and then directly into a USB port on the rear panel of your PC — rear ports are soldered to the motherboard and provide more stable power than front-panel headers. Avoid USB hubs unless the interface’s manual explicitly supports one. The interface’s power LED should light within a few seconds. Wait 30 seconds for Windows to finish installing its default driver before proceeding.

Step 3: Set the Interface as the Windows Default Device (3 minutes)

Right-click the speaker icon in the system tray and choose Sounds, then open the Playback tab. Find your interface (it appears by its model name, e.g., “Scarlett 2i2” or “Volt 2”), right-click it, and select Set as Default Device. Then open the Recording tab, right-click the interface’s input, and choose Set as Default Device there as well. Click OK.

On Windows 11, you can instead go to Settings > System > Sound, and under “Choose where to play sound” select your interface from the dropdown, then under Input select it again.

If you game while streaming, consider leaving your gaming headset as the default playback device and routing only OBS to the interface — more on that in Step 5.

Step 4: Install the Manufacturer’s Driver (5 minutes)

Many interfaces work with Windows’ generic USB audio driver, but the manufacturer’s ASIO driver unlocks lower latency and multi-channel routing. Download the driver package for your exact model from the manufacturer’s support page, run the installer, and reboot when prompted. After rebooting, confirm it appears in Device Manager: press Win + X, choose Device Manager, expand Sound, video and game controllers, and verify your interface is listed without a yellow warning icon.

Step 5: Configure OBS Studio (7 minutes)

Open OBS Studio and go to File > Settings > Audio. Under Global Audio Devices, leave Desktop Audio set to your normal output (headset or speakers) and set Mic/Auxiliary Audio to your interface’s input — it will appear as the model name, sometimes with “Analog 1 + 2” or “(Input 1)” appended. Click Apply, then OK.

Back in the main window, find the Audio Mixer panel. Click the gear icon on your mic’s fader and choose Filters. Add these three, in this order:

1. Noise Suppression — choose the RNNoise option; set it first in the chain so it cleans audio before other filters process it.
2. Noise Gate — set Close Threshold around −48 dB and Open Threshold around −40 dB as a starting point in a typical room.
3. Compressor — Ratio 3:1, Threshold −18 dB, Attack 6 ms, Release 60 ms, Output Gain 0 dB.

Right-click the mic source in the mixer and enable Advanced Audio Properties; set Sync Offset to 0 ms initially and ensure “Monitoring Off” unless you need OBS to send the mic back to a specific output.

Step 6: Set Gain and Enable Direct Monitoring (5 minutes)

Turn the interface’s gain knob for Input 1 fully counterclockwise, then speak at your normal streaming volume — not a whisper, not a shout — while slowly raising the gain. Watch the level meter on the interface (or the LED ring, depending on the model) and aim for peaks that light the highest green segment without touching the red. As a rough target, OBS’s mixer should show your voice peaking around −12 to −6 dB. If your interface has a Direct Monitor switch, turn it on and put on headphones plugged into the interface’s headphone jack — you’ll hear your own voice instantly, with no lag, which makes it far easier to judge your levels than listening to the OBS monitor path.

Verify It Worked

In OBS, look at the Audio Mixer: speak into the mic and the fader meter should move in real time. If it doesn’t, right-click the mixer area, choose Advanced Audio Properties, and confirm the correct device is assigned to “Mic/Aux.” Next, record a 30-second test clip: click Start Recording, talk normally, stop, then play the file back (default location: Videos folder). Listen for clarity, consistent level, and the absence of hum, hiss, or robotic artifacts. Finally, run a short test stream set to Private on your platform and check the recording afterward — this verifies the audio survives the encoder, not just the local mix.

Mistakes to Avoid

Hum or buzz on the mic input.
What causes it: ground loops, usually from the PC and another powered device (monitor, laptop charger, audio interface) sharing ground through different outlets, or from cheap unshielded XLR cables.
How to check: unplug everything except the interface and mic, then listen on headphones. Reconnect devices one at a time until the hum returns.
What to do: plug the interface and PC into the same power strip, swap in a shielded XLR cable, and avoid routing the XLR cable parallel to power cables. If the interface has a ground-lift switch, flip it.
How to undo: revert the ground-lift switch and restore your original power arrangement if the hum changes or gets worse.

OBS shows no signal from the mic.
What causes it: OBS grabbing the wrong input device, or Windows updating the driver and renaming the device.
How to check: right-click the speaker icon > Sounds > Recording and confirm the interface shows a moving level meter when you speak. If Windows sees it but OBS doesn’t, the assignment is wrong.
What to do: in OBS, go to File > Settings > Audio, reselect the interface from the Mic/Auxiliary dropdown, click Apply, and restart OBS.
How to undo: set the Mic/Auxiliary device back to Default to restore the previous routing.

Crackling or dropouts during gameplay.
What causes it: USB bandwidth contention or insufficient buffer size, especially with the interface sharing a hub or a USB 3.0 port adjacent to other high-bandwidth devices.
How to check: open your interface’s control panel, locate the buffer size or “Safe Mode” setting, and try increasing it from 64 or 128 samples to 256 or 512 samples. If the crackling stops, it was buffer-related.
What to do: move the interface to a rear-panel USB port on a different controller, close background apps that poll USB heavily, and set buffer size to 256 samples or higher.
How to undo: set the buffer back to its original value if monitoring latency becomes noticeable while recording instruments.

Condenser mic produces no sound or very low output.
What causes it: phantom power off, a dead switch, or a mic that requires more current than the interface provides.
How to check: confirm the 48V LED on the interface is lit and that the mic is a type requiring phantom power — dynamic mics sound normal without it, condensers go silent.
What to do: turn 48V off, wait 10 seconds, then back on with the mic already connected. If it stays silent, test the mic on a different interface to isolate whether the mic or interface is at fault.
How to undo: switch 48V back off before unplugging the mic.

FAQ

Do I need phantom power for a dynamic XLR mic?

No. Dynamic microphones like the SM7B generate their own signal and don’t use 48V. Leaving phantom power on won’t usually harm a modern dynamic mic, but it’s good practice to keep it off. Some dynamic mics with built-in active electronics (certain USB/XLR hybrids) do benefit from it — check the mic’s manual.

Can I use my interface for both game audio and my mic?

Yes, and it’s a common setup. Set the interface as the Windows default playback device so game and app audio routes through it, then in OBS set Desktop Audio to the same interface and Mic/Auxiliary Audio to its input. If you’d rather keep game audio on a headset, set OBS’s Desktop Audio to the headset and only the mic through the interface.

Why do I hear an echo of my own voice?

This almost always means two monitoring paths are active at once — for example, OBS’s “Monitor and Output” setting plus the interface’s direct monitoring. In OBS, right-click the mic source, choose Advanced Audio Properties, and set Audio Monitoring to Monitor Off. If you still hear yourself, mute the mic channel in your headset’s sidetone control or disable “Listen to this device” in Sounds > Recording > Properties > Listen.

What sample rate and buffer size should I use for streaming?

Set 48 kHz in both the interface’s control panel and OBS (File > Settings > Audio > Sample Rate) — mismatched rates cause crackling and pitch artifacts. A buffer size of 256 samples is a solid middle ground for streaming: low enough that voice monitoring feels immediate, high enough to avoid dropouts while a game loads. Drop to 128 only if you also record instruments and need tighter latency; raise to 512 if your CPU is maxed during gameplay.