If a YouTube gaming rerun has no audio, first establish whether the silence affects only your player or is present in the archived stream on more than one device. If the archive is silent everywhere, use OBS’s mixer meter to find whether the break is before OBS, inside its mixer, or in the output sent to YouTube.
Do not assume that a silent archive can be repaired after the event. The safer approach is to identify the failed part of the capture path, correct it, and make a local recording before the next live stream.
Check whether the silence is only on your side
Start with the simplest possibility: the audio may be present, but your current playback path is muted or sending sound somewhere unexpected. Open the YouTube player’s speaker control and check the device volume. If you are using a browser, check the browser tab and system output device as well. A phone, tablet, television, or Bluetooth headset may have its own volume or mute state.
Play the archive on another device, preferably using a different connection and browser or app. If another viewer can check it, ask whether they hear the game, the microphone, both, or neither. This separates a local playback problem from a problem in the produced stream.
If the archive has sound on another device, there is no reason to change OBS yet. Check the original player, selected output device, browser permissions, and headphones. If the archive is silent on several devices, treat the problem as a capture or output issue rather than a YouTube player issue.
The word “rerun” can describe two different situations. It may mean the replay of a finished livestream, or it may mean a prerecorded gaming video being sent through a live stream again. The checks below apply when the audio is missing from the produced stream. YouTube’s archive guidance is relevant specifically to completed live broadcasts, so keep that distinction in mind when deciding what evidence to check.
Play game audio and watch the OBS mixer meter
With the game actively producing sound, look at the relevant source in OBS’s Audio Mixer. You are not trying to judge how loud the YouTube archive sounds at this point. You are checking whether OBS is receiving any signal at all.
If the game source’s meter does not move while a sound effect or menu sound is playing, the signal has probably not reached that source. Look upstream: the wrong application may be selected, the game may be routed to another output, the console may be sending an unsupported format, or the capture card may not be receiving audio.
If the meter moves, the game audio has reached OBS. The next checks are different. Look for a muted source, a very low fader, or an output configuration that does not include the track being sent to the stream. A moving meter does not by itself prove that viewers will hear the audio, but it tells you not to begin by replacing a cable or changing the game’s output.
Also establish which sources are affected. If the microphone meter moves but the game meter is silent, concentrate on game capture, application routing, console output, or the capture card. If the microphone and game are both silent, check the selected sources and overall output configuration before investigating a single game.
OBS documents the mixer’s meters, mute controls, faders, and monitoring controls in its official audio mixer guidance. The labels and layout can vary with the installed version, so use the controls shown in your own OBS window rather than following a screenshot blindly.
If the meter is silent, check the source and system routing
A silent meter means OBS is not receiving audio from the source you are watching. The correct fix depends on the source type and operating system.
For a PC game on Windows, confirm that OBS is capturing the game application you actually opened. OBS’s Application Audio Capture guide describes application-specific capture on Windows 10 version 2004 or later and Windows 11. Depending on your OBS version, you may use an Application Audio Capture source, or enable “Capture Audio (BETA)” in the properties of a compatible Game Capture or Window Capture source. Keep that wording tied to the version that displays it, because capture options can change.
Check the game’s own audio output as well. A game can be playing normally while sending sound to a monitor, USB headset, or another device that OBS is not capturing. Windows volume controls can also route individual applications separately from the general desktop output. The important question is not whether your ears hear the game, but whether the same output is available to the OBS source you selected.
Avoid capturing the same sound through two routes without checking the result. OBS warns that when Application Audio Capture sources are in use, Desktop Audio should be disabled to avoid duplicated sound or echo. If an application is not compatible with the chosen capture method, OBS describes routing it through a virtual audio cable and adding that cable as an Audio Input Capture source. Treat this as an advanced Windows workaround, not as the first thing to buy or install.
On macOS, use instructions that match both OBS and macOS. OBS says that OBS Studio 30 with macOS 13 Ventura or later can use the macOS Audio Capture source for desktop or selected application audio. The macOS Screen Capture Source can also capture audio. OBS versions 28 and 29 on macOS 13 or later use the Screen Capture Source for this purpose, while older macOS versions may require additional software for desktop-audio capture. Confirm the current support notes for your installed versions before changing the setup.
If you are using a console and capture card, check the console’s audio output before changing OBS. Elgato’s official audio troubleshooting guidance describes capture devices that accept stereo PCM and do not accept bitstream, Dolby Digital 5.1, DTS, Dolby Atmos, or other surround formats listed by the manufacturer. The applicable setting may be called Linear PCM, stereo, or uncompressed, depending on the console.
These are not universal console instructions. The correct menu depends on the console generation, capture device, and connection. On documented PlayStation configurations, Elgato recommends Linear PCM. On documented Xbox configurations, it recommends stereo or uncompressed output. On Switch, it says Surround can prevent some sounds being captured correctly and recommends Stereo if Automatic fails.
Headphones can also change what reaches HDMI. Elgato documents cases where a headset connected to a PlayStation controller or a Switch headphone port stops game audio being sent over HDMI. If the game is audible in the headset but the capture card’s meter is silent, inspect that routing before assuming the capture card has failed.
If the meter moves, check mute and fader state
When the meter moves, work through the mixer rather than changing the source. First check the source’s mute button. It is easy to mute a game source while adjusting the microphone and then forget that the state remains active.
Next, check the fader. A source can show activity but be set so low that the resulting stream is effectively silent. Raise it carefully while listening to a local monitor or test recording. Do not use the microphone as the reference for game volume: a loud microphone can hide a very quiet game track.
Then check audio monitoring. Monitoring determines what you hear through OBS and is not identical to what is sent to YouTube. A monitoring change can make you hear or stop hearing a source without changing the broadcast mix. Use it to diagnose the route, but still verify the output in a recording.
If the microphone is present in the archive and the game is not, do not reduce the microphone simply to make the mix appear balanced. The game source may be muted, routed to a different output, or excluded from the track used by the stream. If both sources appear in OBS but only one reaches the archive, move to the output and track checks below.
It is useful to write down what each meter does while the problem is present:
| What you observe in OBS | Most likely area to check first | What not to assume |
|---|---|---|
| Game meter does not move | Game source, application routing, console output, or capture-card input | That YouTube removed the game audio |
| Game meter moves, but archive is silent | Mute, fader, output track, or stream configuration | That the capture hardware needs replacing |
| Microphone moves, game does not | Game capture path or game-specific routing | That all OBS audio is broken |
| Neither microphone nor game moves | Selected sources, system routing, or overall audio configuration | That a single source is at fault |
| Audio works on another device only | Player, browser, device, or selected output | That the archive itself is silent |
Verify output and track configuration
A source can be visible and active in the mixer without being assigned to the audio output used by the live stream. Open the relevant OBS output or audio settings and check how tracks are configured. Do not copy a track number from somebody else’s setup: the correct track depends on your own output configuration and which track the stream is using.
Confirm that the game source is selected for the track intended for the broadcast. If you use separate tracks for recording and streaming, it is possible for the local recording to contain the game while the stream track contains only the microphone, or the reverse. That is why a meter check alone is not enough.
Also check whether you are testing the live output or a recording output. OBS can be configured with different audio selections for each. A recording that sounds correct does not automatically prove that the live stream track is correct, and a silent recording does not necessarily describe every possible output. Compare the settings for the destination you actually care about.
If you changed tracks, sources, or monitoring, make a fresh short recording and play the file in a media player. This checks the produced file rather than only the controls on screen. It is especially useful when a viewer reports silence but your local monitoring sounds normal.
You can also review the stream settings in YouTube before going live. YouTube’s encoder settings and live-stream guidance recommends testing with audio and movement similar to what the real stream will contain, then monitoring stream health and messages during the event. The test should use the same game, capture method, microphone, and output path where possible.
For other stream settings, the blog’s guide to using a YouTube stream key with a gaming VOD in India may help with the broadcast side, but it will not replace checking the audio path in OBS.
Match the checks to your operating system and capture setup
There is no single audio menu that applies to every gaming rerun. Separate your setup into one of these practical paths before making changes: Windows PC game capture, macOS application or screen capture, or console capture through a device.
On Windows, decide whether you are capturing application audio directly or capturing a general desktop output. Direct application capture can prevent unrelated sounds from entering the broadcast, but it must target the correct game window and be supported by the installed OBS version. Desktop capture may be simpler for some setups, but it can include notifications or duplicate a separately captured application source.
On macOS, check the OBS and macOS versions first. A source available in a newer version may not exist in the same form in an older installation. macOS permissions can also affect screen and audio capture. If the source exists but remains silent, revisit the selected application and the system output rather than assuming the source is configured correctly.
With a console, identify where the audio is supposed to travel: console to HDMI, HDMI to capture device, capture device to OBS, and then OBS to the selected output track. A headset connected directly to the controller or console can change that path. A surround or bitstream setting can also be unsuitable for a device expecting stereo PCM.
If you are using an Elgato device on Windows, it may be captured when the device is added through the relevant source. On macOS, Elgato’s instructions can require an Audio Input Capture source with the named capture device selected. Follow the instructions for the actual model and operating system, rather than treating a Windows example as a macOS rule.
Do not buy a new capture card, cable, headset, or mixer merely because a rerun is silent. The evidence you have gathered should point to a missing source, incompatible format, routing problem, or output assignment first. Hardware replacement becomes a separate decision if the device fails an appropriate test after the signal path has been checked.
If the technical setup is stable but the real problem is keeping a prerecorded channel running after the computer is shut down, the guide to keeping a YouTube live stream running without a PC in India covers a different operating model. It does not remove the need to verify that the uploaded file itself contains the intended audio.
Test with a local recording before going live
A short local recording is prevention, not a promise to restore an existing silent archive. Record the same game scene, microphone arrangement, capture card, and OBS output configuration that you plan to use for the next broadcast. Include normal game sound, a spoken microphone check if you use one, and a transition or menu that makes the audio change obvious.
Stop the recording and listen to the resulting file from start to finish, or at least through every part of the planned audio path. Use the media player and headphones or speakers you normally use for checking files. If the recording contains no game audio, return to the OBS meter and source checks. If it contains game audio but the live stream does not, compare the recording and stream track assignments.
YouTube also recommends a pre-stream test with representative audio and movement, followed by monitoring during the event. A test that contains only a silent loading screen or a microphone check will not reveal that game audio disappears when the game starts. Use the actual capture conditions for a useful test.
Keep the local recording when it is practical, particularly for a long rerun or a channel that needs a repeatable workflow. It gives you a copy to inspect if the live archive later sounds wrong. It is not a guarantee that YouTube will accept, preserve, or reconstruct every part of a broadcast.
There is also an archive-duration consideration. YouTube says live streams under 12 hours can be automatically archived, while streams longer than 12 hours may not be captured at all. That statement concerns whether a live stream is captured, not whether audio failures are recoverable. For long broadcasts, a local recording is therefore a sensible backup rather than an optional diagnostic.
If you regularly loop prerecorded content, you can also review the blog’s explanation of how a repeated playlist affects a 24/7 YouTube stream. The audio checks remain the same: verify the file, verify the capture path, and verify the produced output before relying on the live channel overnight.
For a channel where the computer should not remain on after the file is prepared, StreamNeo removes the repeated manual capture step by turning an uploaded video into a YouTube live stream, but you should still listen to the source file before uploading it.
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
Can YouTube restore sound to an existing silent gaming archive?
Do not rely on that. The official guidance reviewed for this problem explains archiving and prevention, but does not promise that missing audio can be reliably restored in YouTube Studio. Keep a local recording and correct the capture path before the next broadcast.
Why does OBS show game audio but the YouTube replay has none?
The source may be muted, set too low, or assigned to a different output track from the one used by the stream. Compare the stream and recording track configuration, then make a short recording and listen to the produced file.
What if only the game is silent but my microphone works?
Focus on the game source, application-specific routing, console output, or capture-card input. On some console setups, a headset connection or unsupported audio format can stop game audio reaching HDMI even though you can hear it locally.
Should I change settings for Windows and macOS in the same way?
No. OBS capture methods and available audio sources depend on the operating system and the versions of OBS and the operating system installed. Use the instructions for your exact setup and confirm the current official documentation before changing a working source.