A pop or click during an OBS scene switch usually means an audio device, filter, monitoring route, or source is being started, stopped, duplicated, or resampled at the exact moment the scene changes. The sound may be audible only on the stream recording, only in your headphones, or both. That distinction matters: a clean local recording with a noisy stream points toward routing or monitoring, while a pop baked into every recording suggests a source, driver, or sample-rate problem.
Start by testing with a short local recording rather than going live. Switch repeatedly between two scenes while speaking into your microphone and playing consistent desktop audio. In 2026, OBS Studio still provides enough built-in logging and audio controls to isolate most scene-switch pops without replacing hardware.
Most Common Causes
| Cause | Symptom | Likelihood |
|---|---|---|
| Duplicate audio capture sources | Brief louder click, echo, comb filtering, or doubled audio when a scene changes | Very high |
| Sample-rate mismatch | Sharp click or crackle when an audio source activates; occasional distortion during playback | High |
| Scene-specific audio source starts or stops | Pop occurs only when entering or leaving one particular scene | High |
| Audio monitoring feedback or routing change | Pop is heard in headphones, stream, or both when monitoring changes with the scene | Medium |
| VST, noise suppression, or virtual mixer filter reset | Pop follows a microphone source with filters; may occur after switching back to a scene | Medium |
| USB power, driver, or latency issue | Clicks occur during scene changes and sometimes while gaming or moving windows | Medium |
| Faulty cable, interface, or headset hardware | Pop appears outside OBS or after touching a cable, connector, or volume knob | Low to medium |
Diagnose Step by Step
1. Determine whether the pop reaches the recording
In OBS, click Start Recording, make ten scene switches, then stop the recording. Play the file back through a different player or device if possible. If the pop is not in the recording but is audible in your headset, investigate monitoring, Windows enhancements, your interface’s direct-monitor function, or a virtual mixer. If it is in the recording, continue with source and sample-rate checks.
2. Identify the exact scene transition that triggers it
Create a simple test sequence: Scene A, Scene B, Scene A. Switch using clicks and then using any assigned hotkey. Note whether the pop happens entering a scene, leaving it, or both. A problem limited to one scene nearly always involves a source or filter unique to that scene. Check the Sources dock in that scene for microphone captures, media sources, browser sources with audio, capture-card audio, or nested scenes.
3. Watch the Audio Mixer for duplicate meters
Switch scenes while watching OBS’s Audio Mixer. Your microphone should normally move one meter, not two. Desktop audio, capture-card audio, and Discord output should also appear only once unless you intentionally route them separately. If two meters react to the same sound, mute one temporarily and repeat the recording test.
4. Match the sample rate everywhere
In OBS, open Settings > Audio and note the Sample Rate. Use either 48 kHz throughout or 44.1 kHz throughout; 48 kHz is generally the safer choice for streaming, capture cards, and video workflows. Then open Windows sound settings: press Win + R, type mmsys.cpl, and press Enter. On the Playback and Recording tabs, open each active device’s Properties > Advanced tab and compare its Default Format.
5. Test without filters and monitoring
For the affected source, click the three-dot menu in Audio Mixer and choose Filters. Disable filters one at a time with the eye icon, starting with VST plug-ins, Noise Suppression, Expander, Compressor, and Limiter. Then open Advanced Audio Properties from the mixer’s three-dot menu and set the source’s Audio Monitoring to Monitor Off for testing. Record another series of scene changes after each change.
6. Check Windows and USB behavior
Test the same microphone in Windows Voice Recorder, Discord’s microphone test, or an audio editor while connecting and disconnecting no devices. If clicks occur outside OBS, the problem is lower in the chain. Move a USB microphone or interface directly to a rear motherboard USB port, avoiding front-panel ports, hubs, and monitor USB pass-through. If your interface uses its own control software, confirm its clock/sample-rate setting matches OBS.
Fixes by Cause
Duplicate microphone, desktop, or capture-card audio
What causes it: OBS global audio devices can capture sound at the same time as scene-level Audio Input Capture or Audio Output Capture sources. A capture card may also send game audio through both its video source and a separate audio device source.
How to check: Open Settings > Audio and inspect Global Audio Devices. Then inspect every scene’s Sources dock. Look for the same microphone, speakers, headset, or capture-card audio listed in more than one route. Open Audio Mixer > three dots > Advanced Audio Properties to confirm which sources are assigned to tracks.
What to do: Choose one capture method per device. For scene-specific audio, set unused Global Audio Devices to Disabled in Settings > Audio. For always-on audio, keep the global device and remove duplicate scene-level capture sources. For a capture card, use either the card’s embedded audio or a separate audio capture source, not both.
How to undo: Re-enable the previous global device or add the removed source again through Add > Audio Input Capture or Add > Audio Output Capture.
Sample-rate mismatch between OBS, Windows, and an interface
What causes it: When one device runs at 44.1 kHz while OBS, a capture card, or an interface runs at 48 kHz, Windows or OBS must resample audio. Starting or stopping that stream during a scene switch can create a click.
How to check: Compare OBS > Settings > Audio > Sample Rate with every active device in mmsys.cpl. Also check interface software, virtual mixer software, and capture-card utilities. Do not assume a device follows Windows automatically.
What to do: Set OBS to 48 kHz. In Windows device properties, select a 48 kHz format such as 2 channel, 24 bit, 48000 Hz where available. Set the same rate in your interface or virtual mixer. Close OBS fully and reopen it after changing audio-device formats.
How to undo: Return each device and OBS to its previous rate. If a device works reliably only at 44.1 kHz, use 44.1 kHz consistently across the complete audio chain.
Audio sources that activate only in one scene
What causes it: A scene-specific microphone, browser source, media source, or capture-card source initializes when the scene becomes active. Some drivers and sources emit a transient at activation.
How to check: In the affected scene, right-click each suspect source and select Properties. For media sources, note whether Restart playback when source becomes active is enabled. For browser sources, check whether the source has audio enabled. Test by hiding or muting one source at a time.
What to do: Keep critical microphone and game-audio devices active globally rather than recreating them scene by scene. Use one shared source: create it in a dedicated scene, then add that scene elsewhere with Add > Scene. For media alerts, trim silence from the beginning of the audio file and avoid abrupt starts at full volume.
How to undo: Restore independent sources to individual scenes or re-enable media-source restart behavior if it is required for your production flow.
Filters, VST plug-ins, and aggressive gates
What causes it: A gate, expander, suppression filter, or VST can abruptly open, reset, or receive a discontinuous audio buffer during source activation. Excessive gain feeding a limiter can make the transient more obvious.
How to check: Open the source’s Filters window. Disable one filter at a time and test at least five scene switches per change. Pay special attention to third-party VST plug-ins and multiple stacked dynamics filters.
What to do: Update or remove the filter that reproduces the click. Keep a simple chain while testing: Noise Suppression, Expander, Compressor, Limiter. Avoid setting an expander or gate threshold so close to normal room noise that it repeatedly snaps open. Lower source gain before the limiter rather than using the limiter to control persistent overload.
How to undo: Re-enable filters with the eye icon or restore previous values from your saved OBS profile.
Monitoring and virtual audio routing
What causes it: “Monitor and Output” can send a source through both OBS output and a monitoring device. Virtual cables, mixer applications, and loopback channels can create duplicate routing or a feedback-like transient.
How to check: Open Settings > Audio > Advanced and confirm the Monitoring Device. Then open Advanced Audio Properties and inspect every source’s monitoring mode. If the pop vanishes when all sources are set to Monitor Off, the monitoring route is involved.
What to do: Use Monitor Off for sources that do not need headphone monitoring. Use Monitor Only (mute output) only when you deliberately need a source in headphones but not on stream. In virtual mixer software, route OBS monitoring to a dedicated output rather than back into an OBS desktop-audio capture path.
How to undo: Return the desired sources to Monitor and Output and restore the prior monitoring device.
USB driver, power-management, or hardware interruptions
What causes it: USB audio devices can momentarily lose timing when power management, overloaded hubs, buggy drivers, or unstable cables interrupt the stream.
How to check: Test another USB port and cable. In Device Manager, expand Universal Serial Bus controllers, open each relevant USB Root Hub or Generic USB Hub, and inspect the Power Management tab. Also test with interface control software and motherboard audio drivers updated from the hardware manufacturer.
What to do: Connect the device directly to a rear motherboard port. Disable Allow the computer to turn off this device to save power for the hub serving the audio device when that option is available. Replace damaged or loose USB cables and avoid sharing a hub with high-bandwidth cameras or capture devices.
How to undo: Re-enable the power-saving checkbox or move the device back to its prior port after confirming the issue is resolved.
When to Replace or Reinstall
Reinstall OBS only after testing a fresh profile and scene collection. Create them through Profile > New and Scene Collection > New, add one microphone source, and record scene switches. If the clean setup works, your original collection contains the issue; export or rebuild only the necessary scenes instead of deleting everything.
Reinstall an audio driver when the pop occurs outside OBS, survives a clean OBS profile, and follows the same device. Remove the device in Device Manager, restart Windows, then install the current driver or control software supplied by the device manufacturer. Replace hardware when the click follows the same microphone, interface, cable, or headset across multiple ports and applications, especially if touching the connector reproduces it.
FAQ
Why does the pop happen only on stream and not in my headphones?
Your headphones may be using direct monitoring from an interface, while OBS sends a different processed signal to the stream. Check OBS filters, track assignments, and duplicated output sources. Record locally first; if the recording is clean but viewers hear a pop, inspect your streaming platform’s audio track selection and any external encoder or virtual mixer route.
Can a scene transition itself cause an audio pop?
A visual transition such as Fade normally does not alter audio. The pop usually comes from an audio source becoming active, inactive, duplicated, or reinitialized at the same time. A scene transition can expose the issue, but it is rarely the root cause.
Should every OBS audio device use 48 kHz?
Yes, if your workflow includes capture cards, USB interfaces, game consoles, or video editing. The important rule is consistency: OBS, Windows playback devices, recording devices, interface software, and virtual routing software should use the same rate whenever possible.
Will increasing OBS audio bitrate fix popping?
No. Audio bitrate affects compression quality, not clicks created before encoding. Fix the source routing, sample rate, filters, driver behavior, or hardware connection first. Once the pop is absent in a local recording, your stream output should also be clean.
