Pairing a wireless microphone into a capture card setup sounds harder than it is, but there’s a real catch: most capture cards pass video and HDMI-embedded audio to your PC, while your wireless mic receiver connects separately. The goal of this guide is to get your mic’s audio recorded cleanly alongside your gameplay — whether you capture with an Elgato HD60 X, a EVGA XR1, an AVerMedia Live Gamer, or similar — and end up with a single synced track in OBS Studio or your editor of choice. Total time: about 20–30 minutes.
Prerequisites: a working capture card connected to your PC, your gameplay console or second PC outputting to the card, OBS Studio (any version from 29 onward works fine), your wireless mic system (transmitter and receiver), and basic cabling. We’ll use OBS as the hub because it handles both the capture card feed and a separate mic input, then merges them on export.
Before You Start
| What you need | Why | Optional? |
|---|---|---|
| Wireless mic receiver with analog out (3.5mm TRS or dual RCA) | The receiver’s audio must reach your PC somehow; analog out is the standard path | No |
| 3.5mm-to-3.5mm TRS cable, or RCA-to-3.5mm adapter cable | Connects the receiver to your PC’s line-in or audio interface | No |
| USB audio interface or mixer (e.g., a basic 2-input USB interface) | Onboard PC line-in jacks are often noisy or disabled; an interface gives cleaner gain control | Recommended |
| Fresh AA/AAA batteries or a charged transmitter | Low transmitter power causes dropouts that look like sync or pairing failures | No |
| Headphones plugged into your monitoring device | You need to hear the mic live to verify levels and sync | Recommended |
| USB-C or USB-A cable for the receiver | Some receivers (Rode Wireless GO family, DJI Mic, Hollyland Lark) double as USB audio interfaces | Yes — alternative to analog |
Before touching software, check which connection style your receiver supports. USB receiver/dongles (Rode Wireless ME, DJI Mic Mini, most 2.4GHz phone-oriented kits) are simplest: the receiver becomes a sound card the moment you plug it in. Analog-output receivers need the cable route. The steps below cover both, with the divergence flagged.
Step-by-Step
Step 1: Pair the transmitter to the receiver (5 minutes)
Power on the receiver first, then the transmitter. On most 2.4GHz kits, pairing is automatic once both are charged and within about 3 meters of each other — a solid link LED (usually green or white) confirms it. If yours shipped as separate units or won’t link: on Rode Wireless GO II, swipe to the pair screen, tap the transmitter icon, then hold the pair button on the transmitter for 3 seconds. On DJI Mic, go to Settings → Transmitter Connection and select the transmitter’s serial number. On Hollyland Lark M2, double-press the receiver’s power button to enter pairing, then press the transmitter’s button. Confirm link before moving on — no link means nothing downstream will work.
Step 2: Connect the receiver to your PC (3 minutes)
USB route: Plug the receiver into a USB port directly on your motherboard — not a hub. Windows plays the connect chime and the receiver appears as an audio device.
Analog route: Run the 3.5mm cable from the receiver’s line/headphone output to your interface’s line input, or to your PC’s light-blue line-in jack. Avoid the pink mic-in jack for line-level sources; it applies an aggressive preamp that will clip. On the receiver, set output mode to Mono if it has the option (Rode: swipe to the output screen, set Output Mode → Mono), since a mono mic on a stereo feed half-cancels in some editors otherwise.
Step 3: Set the receiver’s output level (2 minutes)
Most wireless receivers output at fixed line level, but headphone-style outputs have a volume control. Set it to roughly 70–80% as a starting point. If the receiver has a dB readout (DJI Mic shows output gain from -12 to +12 dB), start at 0 dB. Too low and you’ll fight noise floor later; too high and you’ll clip. You’ll fine-tune in Step 5.
Step 4: Add the mic as an audio source in OBS (5 minutes)
Open OBS Studio. In the Audio Mixer panel, click the gear icon on any channel → Filters is not where we start — first make sure the device is selected: go to File → Settings → Audio → Global Audio Devices → Mic/Auxiliary Audio and pick your receiver from the dropdown. USB receivers appear under their brand name (e.g., “Rode Wireless GO II”); analog line-in appears as your interface’s name or “Microphone (Realtek Audio)” — if it’s Realtek, verify in Windows that line-in is enabled: Settings → System → Sound → More sound settings → Recording tab, right-click the device, and enable it if grayed out. Set the device to mono: right-click your mic channel in the mixer → Filters → plus icon → Mono (the simple mono filter, not Downstream mix). Now do the same check for your capture card: Settings → Audio, and if your card isn’t listed under Desktop Audio or a Mic slot, add an Audio Input Capture source, right-click the Sources panel → Add → Audio Input Capture, and select the capture card’s audio device (e.g., “Digital Audio Interface (Elgato HD60 X)”).
Step 5: Set gain and test levels (5 minutes)
In OBS’s mixer, speak at your normal streaming/commentary volume and aim for the meter peaking around -12 to -6 dB, never touching the yellow/red. Adjust using the OBS fader first, then receiver output gain if you’re maxing the fader. Then add two filters, in this order: Noise Suppression (RNNoise mode) and Compressor (ratio 4:1, threshold -18 dB, attack 6 ms, release 60 ms — default OBS values are close enough to start). Say “test, test, one two” and watch for the link LED flickering on your receiver during transmission — flickering at close range usually means RF interference, so try switching the receiver to its backup frequency band in its menu.
Step 6: Sync mic audio with the capture card feed (5 minutes)
Capture cards add 2–4 frames of audio/video latency, and analog mic chains add a little too, so a clap test matters. In OBS, hit Start Recording, clap loudly once on camera, stop after 5 seconds, then drag the file into your editor and count frames between the clap image and the clap waveform. If the mic audio is early, add delay: in OBS, right-click the mic channel → Advanced Audio Properties → Sync Offset, enter a positive value in milliseconds (try +80 ms as a starting guess; 60 fps means one frame ≈ 16.7 ms). Re-record and re-check until offset is under one frame.
Verify It Worked
Do a full 60-second test recording with gameplay running and you commentating. Play it back and check three things: (1) your voice and game audio are both present, (2) your voice doesn’t drop out when you turn your head — dropouts indicate RF range or battery issues, not software, (3) the clap-sync from Step 6 is within one frame. Also right-click your recording file → Properties → Details to confirm both audio channels are embedded in the single file. In OBS’s Settings → Output → Recording, the track count and format (MKV is safest; remux to MP4 via File → Remux Recordings afterward) should show audio track 1 muxed in.
Mistakes to Avoid
Plugging a line-level receiver into the pink mic-in jack. What causes it: color-coding habits. How to check: your meter clips at low receiver volume with a harsh, fizzy distortion. What to do: move the cable to the blue line-in jack, or reduce Windows input level to below 20 and add an attenuator if your interface lacks line inputs. How to undo: simply move the cable back; no settings persist.
Leaving the receiver’s monitoring output routed to your speakers. What causes it: using a headphone-out on the receiver that doubles as a line out while desktop speakers are attached. How to check: you hear an echo of your own voice, or feedback squeal. What to do: mute Windows output for the receiver device in Settings → System → Sound → Output, and monitor through OBS instead (Advanced Audio Properties → Audio Monitoring → Monitor Only on your mic channel, routed to headphones via Settings → Audio → Monitoring Device). How to undo: set monitoring back to Monitor Off.
Fixing dropouts with gain instead of RF placement. What causes it: assuming crackly audio is a level problem. How to check: the link LED flickers or the receiver’s app logs RF drops while the audio meter stays steady. What to do: keep the receiver 1–2 meters from your Wi-Fi router, keep line-of-sight between transmitter and receiver, and switch to a less congested channel in the receiver menu (2.4GHz kits usually offer 2–3). How to undo: revert to Auto channel if a manual channel causes worse behavior in another room.
Recording to MP4 directly. What causes it: wanting an editor-ready file immediately. How to check: n/a — it’s preventive. What to do: set Settings → Output → Recording Format to MKV or Hybrid MP4, and remux after recording. If OBS or Windows crashes mid-recording, an MP4 is corrupted while an MKV survives to the crash point. How to undo: run File → Remux Recordings on existing MKVs.
FAQ
Can I plug my wireless receiver directly into the capture card’s audio-in port?
Some cards (Elgato HD60 X has a 3.5mm analog input; the 4K60 line varies) accept line-in and embed the audio into the HDMI stream. It works, but you lose the ability to adjust mic gain independently in OBS and can’t apply filters to the mic alone. Connecting the receiver to the PC instead gives you per-source control, so treat the card’s audio-in as a fallback.
Why is my wireless mic audio slightly ahead of my game audio in recordings?
The capture card pipeline adds latency to the video/game-audio path, so your direct-connected mic arrives first. Fix it with a positive Sync Offset on the mic channel in OBS’s Advanced Audio Properties, using the clap test from Step 6 to dial in the exact value.
Do I need an audio interface at all?
No — if your receiver has USB audio output, plug it in and skip the interface entirely. An interface only earns its place if your receiver is analog-only, your motherboard’s line-in is noisy, or you want hardware gain control within reach while recording.
Can I record my mic and game audio on separate tracks for editing?
Yes, and it’s worth doing. In OBS, go to Settings → Output → Recording, enable multitrack audio, assign your capture card to track 1 and your mic to track 2 under Advanced Audio Properties (checkboxes labeled 1–6 per source). Editors like DaVinci Resolve and Premiere will then show both as independent tracks, letting you compress game audio without touching your voice.
