START HERE
First check a local recording of the same audio mix sent to YouTube. If it is silent, fix capture or track selection in the encoder. If it sounds correct, inspect Live Control Room's current errors and compare viewer playback on another device before changing the microphone.
Test one source at a time
Use your microphone to say a short phrase, then play a permitted sound from the application you want to capture. Keep your speakers low or use headphones so the microphone does not accidentally pick up the application's sound and disguise a missing capture source.
Make a three-column note: source meter moves, local file contains it, YouTube viewer hears it. Check microphone and application audio separately. A test where every source plays at once makes it difficult to know which source you are actually hearing.
Do this in a private test broadcast when possible. An unlisted broadcast is accessible to anyone with its link, so it should not contain private conversations or account details.
If the source meter does not move
Check the named input or application selected in the encoder. A microphone disconnected and reconnected through a dock may no longer be the selected device. An application restarted with a different window can require capture reselection. Test the input outside the encoder with the microphone checker if the problem is speech.
Change one route at a time. If a direct physical microphone works while a virtual input is silent, inspect the application feeding that virtual input. Reconnecting YouTube will not supply audio that never reached the encoder. For OBS desktop sound, use the desktop audio checklist.
If meters move, inspect the streaming mix
A local recording and a stream can use different tracks. In OBS, inspect the streaming audio track in Settings → Output, then the source assignments in Advanced Audio Properties. Confirm each required source belongs to the track being sent. Headphone monitoring is a separate destination and is not proof of stream output.
- Make a short recording that includes the selected streaming mix.
- Stop the recording and select that exact audio track in a capable player or editor.
- Check microphone and game sound separately, including mute and scene changes.
- If another recording track sounds correct but the streaming mix is empty, correct the source assignments rather than the player volume.
Use separate-track recording for editing while retaining a deliberate combined mix for the ordinary live feed.
Read the actual Live Control Room error
YouTube's Live Control Room reports timestamped ingest errors. Confirm you are viewing the same event your encoder is sending to; do not diagnose a scheduled event that is still waiting for its own feed. For the ordinary stereo stream covered here, investigate messages about missing audio, an unsupported codec, or multiple audio streams.
Use your encoder's current YouTube preset, our YouTube Live encoder settings guide, and YouTube's encoder specification to correct the reported mismatch. AAC is a suitable starting point for a conventional stereo RTMPS workflow. Do not export a multitrack editing file directly as though its tracks were a finished live mix.
Take note of the error time before restarting a test. An old warning may describe the previous connection rather than the new settings. Avoid replacing the stream key just because the microphone is missing; a working video connection is evidence that the encoder already reached YouTube.
If the feed is healthy, compare two viewers
Explicitly unmute the YouTube player and its browser tab, then select a known working output device. Check the same timestamp from another device or connection. If just one viewer is affected, work on that player's volume and audio route first. If several independent viewers hear the same silence, keep investigating the sent mix and ingest warnings.
A second listening device should use headphones or be far enough from your microphone to avoid broadcasting the delayed stream back into itself. Mute the check device immediately after listening.
Verify the full show sequence
Repeat the test through your starting, main, and break scenes. Confirm that a source returns after you intentionally mute and unmute it. After ending the test, listen to the saved replay as well as the local mix.
If support is needed, collect the event timestamp, encoder version, selected stream track, current health message, and whether the local mix and second device reproduce the fault. Crop stream keys and account information out of screenshots. This evidence is far more useful than a picture of a moving audio meter alone. Once stream audio is working, check your live YouTube tab or local OBS recording with the live stream loudness & LUFS checker (YouTube Live −14 LUFS preset), and if you also want an on-screen YouTube live chat widget, see the Slippy2 Desktop YouTube chat guide.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.