For consistent levels in YouTube reruns, keep commentary and game audio separately adjustable where possible, then balance the game around speech that stays intelligible in both quiet and intense passages. Compare the same kinds of moments between exports, measure loudness and peaks separately, and listen on more than one playback system.
There is no established YouTube-required integrated loudness or true-peak number for gameplay reruns. The aim is a mix that behaves consistently and remains understandable, not a number that guarantees the same perceived level on every device.
Keep commentary and game sound separate
If your recording or editing setup allows it, capture commentary and game audio to separate tracks. That gives you room to change their relative levels after recording without having to undo the original mix. You can lower a burst of game sound beneath a spoken line, for example, without also turning down the voice.
This separation need not mean a complicated studio setup. A recording application may let you route microphone and desktop audio to distinct tracks; an editor may let you import them as separate sources. Check the resulting file rather than assuming the routing worked: solo each track briefly and confirm that the voice is not baked into the game track and vice versa.
Keep the source gains and routing stable from one rerun to the next unless there is a specific reason to change them. If a microphone input was turned up, a game capture attenuated, or a processing effect added, note the change. Otherwise, differences between versions become harder to diagnose because you cannot tell whether the cause was the mix, the source recording or a changed capture setting.
When only a combined recording is available, you can still make useful adjustments, but the choices are narrower. Broad volume changes affect both sources, and processing that reduces loud effects may also pull the commentary down. Treat such a file as a fixed mix: listen for sections where speech is masked, make conservative changes, and compare the result with the original so an improvement in one scene does not damage another.
If you are assembling a rerun from longer clips, transitions are part of the audio too. A sudden change in game ambience or voice level at an edit can be more distracting than a small difference within a scene. The practical checks for a continuous programme are similar to those in a guide to looping videos on YouTube Live: check the joins as well as the material between them.
Set commentary for intelligibility
Begin with the voice, not with a loudness meter. Pick a section where you speak at an ordinary level, then check a softer sentence and a more emphatic one. Can you follow the words without straining, and does the voice still sound natural? If you need to keep raising playback volume to understand the commentary, the balance or recording may need attention.
The microphone source matters. A voice that is distant, noisy or uneven cannot always be fixed by turning it up. Listen for room noise, keyboard clicks, plosives and clipping. If the input is distorted, lowering the track in the editor will lower the distortion along with the voice; it will not restore detail that was lost during recording. For later sessions, adjust microphone position or capture gain and make a short test before recording the full rerun.
Use gentle compression or volume automation only when the voice changes enough to make ordinary listening difficult. Automation can bring a quiet phrase forward or make a sudden shout less abrupt. Compression can narrow the gap between soft and loud words, but too much can make breaths and background game sound surge between phrases. Compare the processed voice with the unprocessed version at a similar playback level; louder often seems better in a quick comparison even when it is not clearer.
Make changes in context. A voice that sounds full when soloed may be hard to understand once music, effects and ambience return. Likewise, strong equalisation to make speech cut through can make it tiring over a long rerun. Aim for clear words at a natural level, then revisit the voice in the busiest passage rather than polishing it in isolation.
Balance game audio around the voice
Once the commentary is understandable, bring the game audio in around it. Start with ordinary gameplay, then check the sections with music, combat, menus or environmental effects. If effects cover consonants or force you to listen harder, reduce the game track or automate the specific passage. A modest adjustment at the troublesome moment can work better than lowering all game audio throughout.
The right balance depends on what the game contributes. In a story-focused playthrough, dialogue and ambient sound may be important; in a competitive match, effects may carry useful context. The voice still needs to be followed, but the goal is not to erase the game. If reducing the game makes the programme feel empty, restore some ambience in quieter stretches while ducking the sound only beneath commentary that would otherwise be masked.
Listen for the moments where voice and game have similar prominence. A sustained soundtrack can mask speech even if no single effect is especially loud. A brief impact can interrupt a sentence despite the average level of the game track seeming low. That is why a single fader setting is a starting point, not a substitute for checking representative scenes.
For a channel that publishes long reruns or a 24/7 programme, save the mix settings that pass your checks. A repeatable template helps you avoid rebalancing from memory each time. If the game, microphone, room or recording chain changes, treat the old template as a starting point and test it again. The same principle applies when preparing a broader YouTube channel format that resembles a TV channel: consistency comes from repeatable decisions, not identical source material.
Compare quiet and intense passages
Build a short reference routine and reuse it for each export. Select moments that represent the full range of the programme: a quiet section, ordinary gameplay, a loud effect or music passage, and a moment when you speak over busy game sound. Keep timestamps or notes so you can find equivalent passages in a revised export or a later rerun.
Listen to the references in sequence, at the same playback setting. Ask the same questions each time: are the words clear, does the game become unexpectedly dominant, does a loud moment sound harsh, and does the transition into the next passage feel abrupt? Comparing like with like is more useful than listening casually to different scenes and trying to remember which version seemed louder.
A simple comparison table can make that routine repeatable:
| Listening point | What to compare | What a mismatch may suggest |
|---|---|---|
| Quiet section | Voice presence and background noise | Voice level varies, or noise becomes noticeable after processing |
| Ordinary gameplay | The usual voice-to-game balance | Source gain or mix balance changed |
| Loud effect or music | Harshness and peak behaviour | A transient overloads, or limiting is too strong |
| Speech over busy sound | Whether every phrase can be followed | Game audio masks speech, or voice processing differs |
| Start, joins and endings | Changes in level or tone | A clip, transition or source has a different mix |
The table is a prompt for listening, not a pass/fail standard. If a moment fails, adjust the part responsible and replay the same reference moments. Do not compensate for one loud effect by raising the whole commentary track if that makes quiet speech too prominent elsewhere.
When you compare separate reruns, compare equivalent material where possible. Different gameplay can naturally have different sound, so a new explosion or soundtrack does not prove that the mix is inconsistent. If the source footage is the same, note changes in gain, processing and export settings. If it is different, judge the voice and the overall listening experience rather than expecting every scene to have identical loudness.
Measure loudness and peaks separately
Meters can help you find changes that your memory misses, but they answer different questions. A loudness meter can compare the overall level of equivalent passages. A peak meter shows brief high points that may overload the signal or prompt harsh limiting. A mix can have moderate overall loudness and still contain a sharp peak; conversely, a controlled peak does not prove the voice is easy to understand.
Use a meter to compare your quiet, ordinary and intense reference passages between exports, rather than hunting for a universal target. If a passage measures differently, return to listening and find out why: perhaps the source gain changed, a compressor is reacting differently, or game music is covering the voice. Measurement helps locate a difference; it does not tell you whether that difference matters to a viewer.
True-peak measurement or a limiter can help catch inter-sample peaks and overloads, but do not set a limiter so aggressively that the mix pumps whenever the game gets loud. Listen for effects that flatten, voice that becomes strained, and background sound that swells after each impact. Leave sensible headroom during editing so that you can make corrections without clipping the export.
The European Broadcasting Union’s R 128 streaming supplement and its production guidance explain loudness and peak concepts for production contexts. They can give you a framework for understanding what your tools display, but they are not a YouTube mandate for gameplay reruns. YouTube’s recommended upload encoding settings list audio codecs, a sample rate and a stereo bitrate recommendation; those are encoding settings, not a commentary-to-game ratio or loudness target.
Check playback in stereo, mono and on YouTube
First listen to the complete export in stereo, not only to short reference clips. Check headphones and speakers if you can. Headphones make detail and placement easier to notice, while speakers reveal a different balance in a room. Neither listening method alone proves that every viewer will hear the same thing, so use both as practical checks rather than guarantees.
Then check mono compatibility. A stereo mix can lose quality or become partly muted when a device sums it to one channel, particularly if left and right contain out-of-phase material. YouTube’s upload audio troubleshooting guidance advises checking that audio is in phase and notes that mono playback can affect what listeners hear. Collapse your mix to mono or use a mono playback check; make sure the commentary remains present and the game does not disappear or become hollow.
After uploading, compare the processed YouTube playback with the local export. A difference may come from playback behaviour, not only your edit. YouTube documents audio enhancements such as volume balancing and voice boost in its video and audio quality guidance. Its viewer volume controls also describe Stable volume and Voice boost. Viewers’ settings and devices can differ, so this check helps you understand a playback path; it cannot reproduce every listener’s experience.
If the uploaded version seems different, check that you are comparing the same section and similar playback settings. Do not immediately remaster the whole file to correct for a viewer-side enhancement you cannot control. Instead, make sure the local mix is clear and free of avoidable peaks, then judge whether the platform playback introduces a problem across several representative passages.
Save the routine with the export
Once a rerun passes the listening and measurement checks, save the source gains, processing choices and export settings alongside the project or in a short note. Record which reference moments you used and any deliberate automation, such as lowering game music under speech. That gives you a practical baseline for the next version and makes it easier to spot an accidental change.
Revisit the baseline when something material changes: a new game with a different sound profile, a different microphone position, altered room noise, or a changed capture and editing chain. Do not change settings just to chase a meter reading if the references already sound clear and controlled. Equally, do not assume a template will fix a new source that is noisier or much more dynamic than the old one.
For a rerun prepared from a recording rather than mixed live, this separation between making the programme and sending it out is useful. A workflow such as streaming prerecorded video to YouTube Live still depends on the source file being ready: a continuous broadcast cannot repair a voice that is masked in the uploaded mix. If your aim is to keep a prepared file playing while your own computer is off, StreamNeo removes the need to leave that computer running, but the audio balance remains your responsibility before upload.
If you are deciding how to run the broadcast as well as how to prepare its audio, compare the operating options before you commit.
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
Should I set a specific loudness target for YouTube gameplay reruns?
No YouTube-required integrated loudness or true-peak target for gameplay reruns is established here. Use loudness and peak meters to compare equivalent passages and catch overloads, then make the decision by listening to speech clarity and the overall mix.
What should I do if commentary disappears during intense gameplay?
First check whether the game effect or music is masking the voice, then lower or automate that part of the game track. If the voice itself varies substantially, use careful automation or gentle compression and replay both quiet and intense reference passages.
Do I need separate tracks for commentary and game audio?
Separate tracks are useful because you can adjust the voice and game independently after recording. If you only have a combined track, listen for masking and make conservative changes; broad processing may affect both sources at once.
Why does a mix sound different on YouTube or in mono?
Playback enhancements and device settings can change what a viewer hears, while mono conversion can expose phase problems in a stereo mix. Compare the upload with your local export and check that the commentary and game remain clear when summed to mono, without assuming every device will sound identical.