How to Troubleshoot an OBS Audio Mixer That Is Not Working

Identify the symptom and environment

Start with what has stopped working and when. For example, the Audio Mixer may be absent from the main window, a capture source may show no movement on its level meter, or the meter may move while a recording or stream remains silent. Note whether this happens with one input device, one output device, or all audio in OBS.

Record the environment before changing anything. This includes the operating system version, OBS version, the selected audio input device and output device, the sample rate in use, and whether the problem appears during a video call, a local recording, or a live session. If the issue appeared after a driver update, device change, or OBS update, include that detail because it points to a smaller set of likely causes.

Isolate where the fault occurs

Check whether the sound reaches the operating system before involving OBS. In the operating system sound settings, look at the input level while speaking into the microphone or playing audio through the source. If the system shows no input level, the problem is upstream of OBS: the hardware, connection, driver, or operating-system permission.

If the operating system shows normal levels, open OBS and compare the relevant meter in the Audio Mixer. A source that is inactive or muted can sit at the bottom of the mixer and still be easy to miss. Try a different source only to separate causes: for example, add another capture source or select another installed input device if one is available.

Output problems need the same separation. If a desktop audio source is absent but a microphone source works, the issue is likely in source selection or that output device. If OBS meters move but the final recording is silent, check where monitoring is routed rather than assuming the microphone or capture source is broken.

Try reversible fixes in order

Move from the cheapest checks to broader changes. First open the OBS audio settings relevant to your version and confirm the correct devices are selected for desktop audio, microphone, or the specific capture source. A device that is disconnected or disabled may still appear in a list and fail silently.

Next check whether the source is muted, its volume is at zero, or its track selection is empty. In many versions of OBS, a source can be assigned to one or more tracks; if the source is not assigned to the track being recorded or streamed, it will not appear in that output even when the meter moves.

Look at the sample rate setting in OBS and compare it with the device setting in the operating system. A mismatch can cause a source to show as active but produce no usable audio. If background noise or unrelated system audio is being captured, review which output device is selected as a capture source instead of changing encoding settings immediately.

If permissions are relevant to your operating system, confirm that OBS or the browser used for a web-based tool has permission to use the microphone. Browser permission prompts can remain open behind the main window, making the page appear selected when audio access is still blocked.

For persistent connection problems with an external device, disconnect and reconnect it, try another port or cable if available, and restart OBS after the operating system recognizes it. Avoid installing unknown driver downloads or broadly disabling system security controls as a first fix.

Confirm the result

Return to the original symptom and reproduce the same action that failed. If the Audio Mixer was missing, confirm it is visible and reacts when the source plays sound. If a capture source was silent, make a short test recording using the same tracks, sample rate, and output settings that were active when the issue occurred.

Check both the mover and the result. A meter that moves is useful but does not prove the signal is on the selected recording track. Play back the test recording and confirm the intended source is audible at a reasonable input level without relying on an unrelated source or excessive gain.

Keep the test short and reversible. Do not use a factory reset, delete profiles, or change the recording format and frame rate while verifying audio unless those settings were part of the original problem. If the symptom is gone under the original conditions, stop there.

If the problem remains

Keep the observations that pointed to a specific layer. Note whether the operating system detected the device, whether other apps could use it, whether a second capture source worked in OBS, and whether meters moved without audio reaching the recording. These details help distinguish a missing permission, wrong track assignment, or faulty connection from a damaged device.

Do not treat silence in OBS alone as proof of failed hardware. If the device works in another app, the remaining investigation is usually in OBS settings, track routing, or the interaction between OBS and the operating system audio stack. If the device also fails in other apps or is not recognized by the operating system, contact device support or a local repair service with the observed behavior.