If a YouTube Live replay has no sound after you switch videos in OBS, first establish whether the silence is in OBS monitoring, the live stream, the saved replay, or more than one of them. Those are separate outputs, so silence in one does not prove that the others were silent too.
Start with the Audio Mixer while the affected video plays, then test each output on its own. A moving mixer meter is useful evidence that audio has reached OBS’s mixer; it is not proof that the chosen monitoring device, stream track or replay contains it.
Locate where the silence occurs
Write down what you can actually hear before changing settings. Is the OBS monitoring output silent? Could someone listening to the live stream hear the video at the time? Is it only the saved replay that lacks audio? If the live broadcast has ended, you may not be able to check its sound in real time, so treat the replay as a separate observation rather than a complete record of what OBS did.
For a controlled check, use a short, known video with audible speech or music, and switch to it in the same way that caused the problem. Keep the test private or unlisted if you do not want to publish a troubleshooting broadcast. Listen through OBS monitoring if it is enabled, check the live output using a separate device or browser, and then play the saved replay after YouTube has finished processing it. Note the time of the switch and where sound disappears.
Do not change several settings between those checks. If you alter source properties, tracks and monitoring at once, a successful test will not tell you which path was responsible. A simple note such as “mixer moves; monitoring silent; live audible; replay not checked” is more useful than a general report that OBS has no sound.
If YouTube Studio reports that it is not receiving data, that is a different symptom from a stream carrying video but no audible programme. The distinction is explained in this guide to YouTube Live showing no data while OBS is streaming. Keep the connection state and the audio test separate while troubleshooting.
Read the relevant Audio Mixer meter
In OBS, play the affected source and watch the meter for the source you expect to carry its sound. OBS’s Audio Mixer guide describes the mixer controls and monitoring. If the meter moves in time with the video, audio is reaching that mixer channel. If it stays still, investigate the source’s audio settings or whether the source is producing sound before changing YouTube settings.
Use a known audible moment rather than a quiet opening frame. Check whether the source is muted and whether its fader is at a level that can be heard. If there are several sources in the mixer, identify the one belonging to the switched video; activity from a microphone or another scene source does not establish that the video audio is present.
A meter is a checkpoint, not an end-to-end test. It does not show that audio is routed to the track OBS sends to YouTube, nor that the selected monitoring device works. The replay adds another stage: the stream audio track must be included in what YouTube receives and saves. Therefore, a moving meter alongside a silent replay narrows the search to later in the path, but it does not name the cause.
If the meter is inactive, test the file outside OBS or play a different known-audible file through the same source. That helps distinguish a silent or incompatible file from an OBS source configuration issue. Keep the scene and other audio sources unchanged so you know which meter you are observing.
Confirm the source type and audio selection
Check whether the video is an OBS Media Source or a VLC Video Source. Their controls differ, so do not follow settings for one while using the other. For a Media Source, open its properties and confirm that it points to the intended file. Then inspect what happens when the source is hidden and shown again during a switch.
OBS documents the Media Source options “Restart playback when source becomes active” and “Close file when inactive” in its Media Sources guide. The latter closes an inactive file to free memory, and OBS notes that showing it again can involve a brief delay. These options are useful diagnostic leads: observe whether the new video starts and whether its audio meter begins moving. Their presence is not proof that either setting caused this incident, and toggling them without a focused test can obscure what changed.
For a VLC Video Source, check the selected audio track in that source’s properties. OBS states that this source requires VLC, and that 64-bit OBS requires 64-bit VLC. If the video picture appears but its meter is inactive, the selected track and installation are worth checking. Do not assume the VLC source is at fault solely because the issue began after a video switch; establish whether the relevant meter responds first.
| What you observe | Next check | What it establishes |
|---|---|---|
| Expected source meter does not move | File playback, source type and source audio selection | Whether the source is supplying audio to the mixer |
| Meter moves, OBS monitoring is silent | Monitoring device and monitoring assignment | Whether the local listening path is selected and audible |
| Meter moves, live output is silent | Stream track assignment and a separate live check | Whether the mixer signal reaches the broadcast path |
| Live output has sound, replay does not | Replay playback and YouTube’s saved audio result | That the live and saved outputs differ in this test |
Treat each row as a branch, not a diagnosis. The same visible symptom can have different causes depending on source type and the output that failed. The table helps you choose the next check without changing unrelated settings.
Trace the audio track and routing
When the source meter moves but an output is silent, inspect where that source is routed. In the source’s advanced audio properties, confirm which audio track or tracks include it. Then compare that assignment with the track selected for streaming in OBS’s output settings. If the source is excluded from the streaming track, local monitoring may work while the live programme receives no audio from it.
Do not infer the track assignment from the fact that the picture is streaming. Video and audio are distinct parts of the output, and the picture alone does not tell you which audio track is being sent. If you record locally as well as stream, note which track is used by each output; a recording that has sound does not automatically prove the stream track was configured the same way.
Change one assignment at a time, then repeat the test. Use the same video, wait for a clear audible passage, watch the corresponding meter and check the particular output that was silent. If you cannot identify the relevant track, take note of the settings before changing them so you can restore the original configuration.
The aim is to follow the signal from source to mixer to destination, not to maximise the number of enabled tracks. Extra tracks can make later checks harder if you are unsure which one carries the programme. For an always-on channel built from prerecorded videos, a consistent playlist and scene plan also make transitions easier to inspect; see this guide to automating a Telugu video playlist for continuous YouTube Live.
Separate monitoring from broadcast output
OBS monitoring is for listening locally. A silent monitor can point to a monitoring-device choice or assignment even when audio is reaching the stream. Conversely, hearing audio in your headphones does not prove that the source is included on the streaming track. Choose the monitoring device deliberately and check whether the source is set to the intended monitoring behaviour, but use the live output as its own test.
If the mixer meter moves and only local monitoring is silent, check that OBS is set to the device you are actually listening through. Confirm that the device is available to the operating system and that its output is not muted. Avoid buying or replacing hardware unless a focused test identifies a device problem; the symptom alone does not support a hardware recommendation.
If monitoring works but the live stream is silent, return to stream routing and track selection rather than repeatedly changing the monitoring device. If both are silent while the source meter moves, check each path independently: confirm the monitor assignment and separately confirm the streaming track. A single “audio works” indicator cannot stand in for both.
YouTube’s live control room or a separate playback device can help you check the broadcast, but ensure you are listening to the live output rather than the local OBS monitor. A delayed player or a muted browser tab can confuse the test. Note which playback source you used and whether the video had reached the switched segment before concluding that the stream was silent.
Test the switch as a repeatable event
Once you have a baseline, reproduce the transition deliberately. Start with a source whose meter moves, switch away, then switch back or move to the next video in your normal sequence. Watch whether the expected source becomes active, whether playback restarts or resumes, and when its meter begins responding. A picture appearing before the audio meter moves may indicate a brief source reactivation delay; it does not by itself prove a fault.
For a Media Source, compare the behaviour with its activation options in mind. If “Close file when inactive” is enabled, OBS may need a short time to reopen the file when shown again. If “Restart playback when source becomes active” is enabled, playback may begin again on activation. Record the observed timing and meter behaviour before adjusting either option, then make one change and repeat the same sequence.
Check the outgoing source as well as the incoming one. A transition can leave the wrong source audible, mute the intended source, or make it appear that the new video is silent when the active audio belongs elsewhere. Watch the mixer labels and meters during the change rather than relying on the preview picture alone.
If the channel uses a playlist or repeated rotation, test more than one transition type: for example, the normal next-video switch and a return to a source already used. Keep the test short and controlled. The useful outcome is a record of which source is active, which meter responds and which output contains sound—not a guess based on one overnight run.
Compare the live output with the saved replay
When possible, listen to the live stream during the segment and then inspect the saved replay at the same point. These checks answer different questions. Sound in the live output but not in the replay means the outputs differed in your test; it does not show whether OBS monitoring was silent. A silent live check and a silent replay still do not identify the exact point in OBS where the signal stopped.
Let the replay become available and seek to a moment after the video switch, then compare it with a moment before the switch. Check that the player itself is not muted and that you have reached the right point. If the replay has sound before the transition but not after, note the boundary and repeat a controlled test before changing settings. If the entire replay is silent, that is a broader observation, but the mixer and routing checks remain relevant.
A user report in the OBS issue tracker describes a particular VLC-source audio problem in OBS 32.0.2, including local audio and mixer activity while the stream lacked audio. It is an anecdotal report, not confirmation of a general or current OBS defect, and it does not prove that your replay has the same cause. Check your own source type, version and output evidence before treating an issue report as an explanation.
If you cannot compare the live output because the stream has ended, do not fill that evidence gap with a conclusion. Use the replay to establish what the saved output contains, note that live sound was not checked, and run a short controlled test if you need to separate the two. Keeping those observations explicit makes any later support request more useful.
Choose a stable workflow for your channel
For a channel that switches among prerecorded videos, a repeatable source setup reduces uncertainty. Use clear source names, keep the intended audio track consistent, and test the transition you actually use. If several videos are played from a playlist, verify the first transition and a later one rather than assuming that a successful opening proves every reload behaves identically.
If you are building an always-on regional music channel, plan the video rotation and audio checks together; this Marathi music channel guide covers the broader channel workflow. For an OBS-based setup, keep a short written record of source type, relevant track, meter response and output checked. That turns “no sound” into a reproducible report rather than a reason to reset unrelated settings.
A continuous channel also has an operating trade-off: with OBS on your own computer, the computer and the local playback setup need to remain available for the broadcast. If keeping that machine running is the particular pain point, StreamNeo turns an uploaded video into a YouTube live stream without requiring your computer to stay on; it does not remove the need to check that your source file and channel are ready.
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
Does a moving OBS meter prove that the replay will have sound?
No. It shows that audio is reaching the mixer, not that the streaming track receives it or that the saved replay contains it. Check the live output and replay separately.
If OBS monitoring is silent, was the YouTube stream silent too?
Not necessarily. Monitoring and stream output are separate paths. Check the live stream or saved replay directly before concluding that either was silent.
Should I change “Close file when inactive” after switching videos?
First observe whether the source reloads and whether its meter responds after it becomes active. OBS notes that closing an inactive file can cause a brief delay when it is shown again, but that setting is only a diagnostic lead, not a confirmed cause in your case.
What should I check first with a VLC Video Source?
Check that the intended audio track is selected and that VLC is installed in the version matching OBS’s architecture. Then watch the source’s mixer meter and follow the same separate checks for monitoring, live output and replay.