SteelSeries Sonar Microphone Not Working: Fixes to Try

How Sonar handles your microphone

SteelSeries Sonar does not record or clean anything by itself. It creates virtual audio devices on your PC and routes sound through them, so apps like Discord, OBS, and games see a Sonar microphone instead of the raw headset input. When the routing is right, everything sounds the same as before; when a link in the chain is missing, the microphone appears broken.

The mixer is the map. Each channel, including Game, Chat, Media, Aux, and Microphone, has its own input and output selection, and Sonar keeps a device list for backup switching when hardware disappears. Most not-working reports trace back to a selection somewhere on that map rather than a dead headset.

Streamer mode adds its own layer: it can route chat and game audio in ways that suit a broadcast but surprise a conferencing app. If microphone behavior changed right after toggling a mode, treat that mode as the first suspect.

Fix checklist, in order

Work through these steps before reinstalling anything:

1. Open the mixer and confirm your headset is selected as the playback device and your microphone as the input device. A missing selection shows as a red frame around the menu, and the official setup guide starts here.
2. Check the Windows defaults. If Sonar shows its yellow banner in the mixer, use the auto-set option it offers; otherwise set the Sonar microphone as the default input in Windows sound settings.
3. Confirm microphone privacy. Windows must allow apps to use the microphone; a privacy toggle turned off makes every app look like the culprit.
4. Check the input level. In Windows recording devices, open your headset's properties and confirm the level is not near zero, since a muted or barely-open gate looks exactly like a broken mic.
5. Update SteelSeries GG, then your audio drivers, then restart. Virtual devices that vanish are usually a driver or service issue, and the support steps walk through Device Manager.
6. Re-test in the app itself. Open the failing app's voice settings and select the Sonar microphone explicitly instead of trusting the default.

Sonar virtual devices not appearing

When the virtual devices are missing from Windows entirely, SteelSeries support recommends updating the audio drivers through Device Manager, restarting the computer, and checking GG again. If they still do not appear after that, the support article asks you to contact SteelSeries directly; there is no user-side fix beyond the driver path.

Mic works in Sonar but not in one app

Different apps pick devices differently. Discord, OBS, and games each carry their own input selection, and some ignore the Windows default entirely. Open the app's audio settings, choose the Sonar microphone, and test with a short recording rather than a live call.

A quick test separates the layers: speak into Windows' microphone properties to confirm the headset itself works, then record a short clip in the failing app. If Windows hears you and the app does not, the problem is a selection; if Windows also hears nothing, revisit drivers and privacy.

Streamer mode and the silence it can cause

A mode that suits gaming can leave a conferencing app without a signal. If the microphone works in a game but not in a call, check whether a different mixer channel or mode is selected for that path, then route the app deliberately. Document the working configuration once you find it; settings survive restarts, and the next troubleshooting session starts from a known state.

When real-time routing is not the answer

Routing decides where audio goes, not how clean it is. A call or stream that is already recorded keeps whatever the file captured, and no Sonar setting can reprocess it later. If the recording carries a steady bed of fan, hiss, or room tone under the voice, a file-based cleanup is the practical path. The same pattern shows up in Discord noise suppression: the setting is live, and the saved recording is a separate problem.

Recordings also differ by capture path. A co-host's local track, the stream archive, and a screen recording each keep a different mix, so before cleaning anything, pick the file with the fewest competing voices, usually one person's local track, and treat the rest as fallbacks.

What the backup device switch changes

When a device disappears mid-session, Sonar's backup switch feature moves that channel to the next device in its list, so a headset that loses USB power can silently hand the microphone over to a webcam or a laptop array. The voice still transmits, but it sounds like the wrong room.

If a call or recording changed character after a replug, open the device list in GG and confirm which device the Microphone channel is actually using. The backup behavior is on by default and can be personalized or switched off when it causes more surprises than saves.

A short test without a call

Live calls add variables: other participants, their processors, and the server's own mix. A local test is cleaner. Record twenty seconds of speech with any recorder while monitoring through the headset, then listen to the file.

If the local clip sounds right but callers still disagree, the problem lives in the app or the call rather than the microphone or the routing, and the fix moves one step down the chain.

Export and clean the recording

The rescue path for a noisy recording is the same one used for any other file:

1. Export the cleanest source. In OBS, prefer a local recording with separate tracks; when a mix blends two voices, ask a co-host for their track.
2. Upload one file to SimpleClean. Up to 500 MB and 15 minutes; audio in WAV, MP3, M4A, AAC, FLAC, OGG, or OPUS, and video in MP4, MOV, MKV, WebM, or AVI.
3. Preview Original against Cleaned across a pause, a consonant-heavy sentence, and the loudest passage, then keep the version that preserves the voice.
4. Re-import or publish the cleaned copy and keep the source recording untouched.

The comparison decides, not the meters

A file that measures quieter but sounds thinner has failed the test, and the original remains the correct choice. One listening pass over the same passages every time keeps the standard stable, and it keeps the decision in your ears rather than in a number.

What cleanup can and cannot fix

A stream recorded with a headset mic in a normal room usually carries a steady bed: PC fans, room tone, and a low hum from the machine. That is the target SimpleClean is built for. Clicks, dog barks, echo, and two people talking at once sit outside a steady-noise pass, and a roomy sound needs acoustic treatment rather than another filter.

For a series, the same light pass on every episode keeps results predictable, and keeping the original recording preserves the option to redo the pass later with different settings.

Prevention for the next session

A few habits keep the routing stable once it works:

• Keep one real-time processor active. Sonar, NVIDIA Broadcast, and Windows enhancements stacked on the same microphone can cancel each other or add echo.
• Save the working routing setup and note which device each app expects.
• Record a local track for sessions you plan to keep, so a clean source exists later.
• Watch for the backup-device switch after unplugging anything; Sonar can route to a different device and the microphone will appear to fail.

Related guides

Virtual audio routing is a recurring theme beyond SteelSeries. Discord's Krisp-powered suppression has its own failure modes, and cleaning remote interview and Zoom recordings covers the meeting-recording side of the same problem.