Start the lecture and watch the meter for the OBS source that should carry its sound. If the meter does not move, OBS is not receiving audio through that source; if it does move, follow the signal onward before changing capture settings.
A moving meter does not prove that viewers can hear the stream. The sound can still be muted, routed to the wrong output, omitted from the stream mix, or lost after OBS sends it. Work through the path in order and note the first check that fails.
Start with the source meter
Open the OBS Audio Mixer while the lecture is playing. Identify the meter beside the source expected to carry the lecture: this might be a media source, an application-audio source, or a desktop-audio input. Watch it while speech or other clearly audible content plays. A quiet passage is not a useful test, so seek to a section where you can hear the lecture on the computer.
If the meter responds to speech, OBS is receiving some audio at that point in the path. That does not mean the signal is audible in the stream, or that its level and routing are suitable. Keep the result in mind and move to the next check rather than rebuilding the capture setup.
If the meter stays still, concentrate on playback and capture. A silent meter is different from a meter that moves while the YouTube stream has no sound: the first suggests an input path problem, while the second points further downstream. OBS describes its input indicator as the place to check whether audio is reaching an OBS audio interface in its Audio Mixer technical details. Interface names can differ between OBS versions, so use the installed version's labels as your guide.
For a 24/7 lecture channel, test with a known audible passage and record when the sound stops if the problem is intermittent. If it fails only after the lecture loops, the computer wakes, or the playback application changes, that timing is useful evidence. A continuous failure and an overnight failure do not necessarily have the same cause.
If the meter is still, check playback first
Before changing OBS, confirm that the lecture itself is playing with sound. Listen on the computer using the application's normal playback controls. Check its pause state, playback position, volume, and whether the selected item is actually the lecture rather than a blank or silent segment. If the source is a playlist, test a segment that should contain speech or music.
Next, check which output device the playback application is using. A browser or media player can send sound to a headset, monitor, or other output while the capture source listens to a different device. The result can be audible through one route yet absent from the OBS source you are watching. Avoid switching every device at once: note the current selection, make one controlled change, then observe the relevant meter again.
Confirm that the source exists and is active in the current OBS scene. If you have more than one scene, select the scene being sent live, not merely the one used for testing. A source hidden, disabled, or absent from the live scene cannot contribute audio through that scene. Also confirm that you are watching the meter for the expected source; desktop audio may be moving while a separate media-source meter is not, or the reverse.
The practical question is not simply “Is there audio on this computer?” It is “Does the exact source that should carry this lecture show movement in OBS?” A computer's general volume meter or a browser's audible playback cannot establish that OBS has captured the same signal.
Match the capture route to the playback source
There is no single capture setting that works for every operating system and playback method. A lecture played in a browser, an OBS media source, and a separate desktop application can follow different audio paths. OBS maintains distinct guidance for application audio, desktop audio and media sources; select the topic that matches your actual source and platform rather than copying a setting for an unrelated setup.
Lecture playing in a browser
If you play the lecture in a browser, determine whether OBS is meant to capture that application's audio directly or capture the computer's desktop output. Those are different routes. Check that the browser is the application selected for capture where applicable, and that the browser is not sending audio to an output device that the chosen capture route cannot hear.
A browser tab can also be silent while other computer audio works. Check the tab and site playback controls, then play a known audible part. If other applications appear on the expected OBS meter but the browser does not, focus on browser-specific capture and output selection. Do not infer that desktop capture is working merely because you hear the lecture through headphones.
Lecture loaded as an OBS media source
If the lecture file is an OBS media source, inspect that source's playback state and its audio settings. Confirm that it is active in the live scene and that the file is not paused or positioned on a silent section. Watch the meter associated with the media source itself.
Do not assume that a media source must appear on the desktop-audio meter. The relevant test is whether the source's own audio reaches its own OBS meter and then the stream output. If the source meter is still, check the source and file path before adjusting the computer's general audio device.
Other applications and operating systems
When a different player or operating system is involved, use the matching OBS capture instructions and check the device or application actually exposed by that platform. Some capture methods are specific to an operating system or OBS version; the available controls are not interchangeable. If a setting described in a guide is absent, do not substitute a similarly named control without confirming that it applies to your route.
Keep a short record of the application, source type, operating system and OBS version when asking for help. Those details determine which capture walkthrough is relevant. A guide for macOS desktop audio, for example, cannot establish the correct steps for a browser on another system. Once a suitable source is configured, repeat the original meter test before moving on.
If you are also checking the wider broadcast chain, the stream-key setup guide for a prerecorded broadcast explains where the YouTube stream key fits. A stream key connects the encoder to the channel; it does not by itself confirm that an audio source is being captured.
If the meter moves, inspect the OBS-side path
When the relevant meter moves, leave capture settings alone for the moment. Check the source's mute control and fader in the Audio Mixer. A muted source or fader set too low can make the signal inaudible downstream even while the meter shows incoming audio. Compare the control state with another source only if you know that source is meant to be audible in the same mix.
Then inspect filters attached to the source and to any relevant mixer channel. A filter may alter or suppress the signal. Disable filters only as a controlled test, one at a time, and restore them if they are not responsible. Changing filters, faders and capture devices simultaneously makes it hard to know which part of the path was failing.
Next test monitoring. OBS lets you choose how a source is monitored through Edit → Advanced Audio Properties; the exact wording and layout may vary by version. Set up the source to be heard through the intended monitoring route, then listen using the selected monitoring device. The OBS Audio Mixer Guide explains source controls and monitoring.
If monitoring is silent, check the selected monitoring device and listen on that device rather than assuming sound should emerge from the computer's usual speakers. Headphones can make this check convenient, but they cannot fix a source that is not captured or routed correctly. If the meter moves and monitoring works, OBS has a hearable path for that source; continue to verify what is sent to the stream.
For a long unattended broadcast, there is a practical difference between being able to hear a test and keeping a playback path running after you leave the computer. If the particular problem is that the lecture stops when your computer is off, StreamNeo removes that specific dependency by letting you upload the file once and run the YouTube broadcast without keeping your own computer switched on. That does not diagnose a silent OBS source, and it does not establish that a given audio route is correct; test the feed before relying on it.
Check the OBS stream output, not only the mixer
A moving meter and successful monitoring are not the final test. Check that the intended audio source is included in OBS's stream output and that its mute and fader state apply to the output you are using. If you work with multiple tracks or output configurations, confirm which one is assigned to the live stream and which is used for recording. A source can be audible in one path and missing from another.
Make a short local recording using the intended scene and listen back. This tests whether OBS has produced a file with the lecture sound, though it does not prove that the live stream uses the same output or track. If the recording is silent, return to the source, routing and output configuration. If it has sound, but the live feed does not, treat that contrast as evidence to examine live output rather than as proof of a particular fault.
The diagnostic comparison is straightforward: note whether the meter moves, whether monitoring works, whether a local recording has sound, and whether the encoder's live output has sound. YouTube recommends checking sound directly in the encoder and reviewing the local archive when troubleshooting stream quality in its live-stream troubleshooting guidance. Follow the signal one test at a time.
| Test result | What it suggests, not proves | Next check |
|---|---|---|
| Lecture plays, but the expected OBS meter is still | The selected capture path may not be receiving it | Playback output, active source, capture selection and platform-specific instructions |
| Meter moves, but OBS monitoring is silent | The source, processing or monitoring route may be wrong | Mute, fader, filters, monitoring choice and device |
| Monitoring works, but local recording is silent | Recording and stream output may use different routing or track settings | Recording configuration and selected audio output or track |
| Local recording has sound, but the live stream does not | Live routing or encoder output may differ from the recording | The source and audio path assigned to stream output; encoder output |
| Encoder output has sound, but a viewer hears none | The issue may be on that viewer's playback or connection path | Compare another device or connection and check YouTube's live information |
These outcomes narrow the search; none identifies the cause on its own. In particular, a local recording with sound and a silent live stream does not establish which OBS output setting is responsible. It tells you to compare the live path with the recording path.
Verify the sound in YouTube Live Control Room
Listen to the encoder's output or the live stream monitoring view available in YouTube Live Control Room, not just OBS's desktop preview. YouTube's guidance asks streamers to check the sound from the encoder when diagnosing poor audio. If that output is silent, the viewer-side problem is already present before you investigate a particular viewer's device.
If OBS's local recording has sound but the encoder output is silent, compare the audio source and output settings assigned to the live stream with those used for recording. Recheck whether the intended source reaches the stream mix, whether it is muted, and whether the live output is using the expected audio path. If both recording and encoder output are silent, return to the earlier capture and routing checks rather than changing YouTube settings at random.
If the encoder output has sound, but the Control Room playback or reports from viewers suggest otherwise, compare what you can hear in the live view with the encoder's own output. Use YouTube's current live information and any available stream-health indicators to see whether the issue is widespread or limited to a particular viewer. YouTube notes that a problem reported by one viewer can reflect that viewer's computer or connection, whereas reports across different viewers can point back towards the encoder. That distinction is a clue, not a guarantee.
For a 24/7 stream, write down when a change occurs and whether it follows a source change, loop boundary, or other playback event. If the feed works during a short test and becomes silent later, repeat the same observations at the point of failure. A one-time successful test cannot establish that an intermittent problem has been fixed.
Confirm what the viewer hears
Once the encoder output is audible, check the public or unlisted live playback from a separate device or browser if practical. Make sure the viewer-side player is not muted and its volume is raised. Confirm that the device is using an output you can hear; a muted tab or a connected headset can make a healthy stream seem silent to the person testing it.
If you can hear the live stream on one device but not another, compare the second device's player, output selection and connection before changing OBS. If multiple viewers on separate devices and connections report silence, go back to the encoder output and Control Room checks. The number or location of reports does not on its own tell you which component has failed, but comparing independent playback paths helps separate a local listening issue from a broadcast issue.
Avoid using the public viewer test as a substitute for the meter and recording checks. It tells you what reaches that playback path, not where the signal disappeared earlier. The sequence matters: source meter, OBS monitoring, local recording, encoder output, then a separate viewer. Each step answers a different question.
If the sound drops only sometimes, keep a simple incident note: the time, what was playing, which meter moved, whether monitoring worked, and whether the encoder output was audible. This is more useful than repeatedly toggling devices without a record. If the signal disappears at a repeatable point, test that point under observation before treating the channel as ready for an unattended run.
For a video-file channel, audio is only one part of keeping a reliable broadcast. The guide to running a prerecorded 24/7 YouTube broadcast covers the stream connection, while the FFmpeg loop setup for a study channel is relevant if your playback method is a playlist on a VPS. If your main concern is handling a long lecture file, see the guide to compressing long videos for YouTube Live. These are different operating contexts, so use the one that matches your actual setup rather than treating them as audio fixes.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Why is my OBS audio meter not moving?
OBS is not showing audio at the source you are watching. First confirm that the lecture is playing an audible passage, then check that the correct source is active and that its capture route matches the browser, media source or other application and your operating system. Do not assume a single capture method fits every setup.
Why does the OBS meter move but the stream have no sound?
The meter shows that audio reaches that OBS source, not that it reaches YouTube. Check mute and fader state, filters, monitoring, and whether the source is included in the stream output. Compare a local recording with the encoder's live output to find whether the sound disappears before or after recording.
Should I change desktop audio settings for a lecture in a browser?
Not without checking how the browser audio is meant to be captured on your operating system. Application capture and desktop capture are different routes, and the appropriate instructions depend on the source and platform. Test the relevant OBS meter after each deliberate change.
How do I tell whether the problem is my viewer or the broadcast?
Check the encoder output in YouTube Live Control Room, then listen to the live stream from another device or connection. If the encoder has sound but only one playback path is silent, investigate that viewer's player, output and connection. If the encoder is silent too, continue tracing the OBS stream path.