1. Map each sound to one capture path
Make a three-line checklist: microphone from the intended input device; game or application audio from one chosen capture route; music from the player or media source you actually use. A visible game picture is not proof that its sound is captured. Name the mixer entries so that another operator can tell which source belongs to which sound.
- Avoid capturing one microphone globally and again inside the scene.
- If desktop audio already includes the game and player, check before also adding separate captures.
- Use only music you are authorized to include in the broadcast.
2. If a meter stays still, check the device before the mix
Mute the other sources and speak into the intended microphone. If its meter does not respond, reselect the device by name, check its hardware mute and confirm that the operating system allows the app to use it. On macOS, review OBS microphone permissions; screen or application capture may also need the corresponding permission. For game or music audio, confirm the application is playing to the device your capture route actually uses.
- Reconnect a headset or USB interface, then check that the saved device is still correct.
- Changing the default system device can change a previously working route.
- Test the next source only after the first signal is identifiable.
3. Balance voice against the programme, without clipping
Check the mixer mute buttons and faders while playing the real programme. Keep voice clear over game and music, leave headroom for sudden loud sounds and avoid peaks reaching 0 dBFS, where digital clipping can occur. A fader showing 0.0 dB is a gain setting; it is not the same reading as the signal peak on the meter. Listen as you adjust rather than matching every source’s meter height.
- Begin with microphone and music separately, then test them together.
- Reduce the offending source if it distorts; a downstream fader cannot repair an already clipped input.
- Do not copy one fixed volume percentage to different microphones and computers.
4. Separate headphone monitoring from stream delivery
Open Advanced Audio Properties and check what each source sends to the output as well as what it plays to your monitoring device. A monitoring-only route can be audible to the operator without entering the stream mix. Also inspect the audio track selected for streaming and whether the required sources are assigned to it. Separate recording tracks are useful for editing, but an ordinary player typically plays one selected track at a time.
- Keep a complete mixed track for an easy playback check.
- Use separate tracks only when you can identify and test them.
- Local headphone sound and the viewer’s sound must be checked independently.
5. Find echo by removing one path at a time
Use headphones, mute the desktop or application capture temporarily and repeat one short phrase. If the repeated sound disappears, inspect duplicate captures or a monitored signal being captured again. If it remains, check the microphone, room speakers and any voice-chat software. Avoid leaving your own audience page audible on the production computer: its delayed playback can return to the outgoing mix.
| Symptom | First check | Proof after the change |
|---|---|---|
| No meter movement | Device selection, hardware mute and app permission | That source alone moves the expected meter |
| Headphones work, output is silent | Monitoring mode and the selected stream track | A recording of the mixed track contains the source |
| Delayed duplicate voice or music | Duplicate capture, speakers and the audible viewer page | One phrase is heard once in the recording |
| Sound only on one side | Source channels and mono/stereo routing | Both headphones reproduce the intended mix |
6. Repeat the check inside each OBS instance
When TKLive manages several OBS instances, give every account’s instance its own identifiable audio checklist. Separate windows do not guarantee that shared microphones, desktop devices and monitoring routes are configured differently. Test one instance first, then add the next and listen for an unintended second capture. Change only the affected instance after confirming its account and current scene.
- Keep instance names aligned with the account and programme.
- Recheck audio after copying a scene collection or connecting a new device.
- Keep the settings of an already verified output as the comparison baseline.
7. Record, listen, then verify the LIVE output
Record a short local sample: introduce the programme, trigger an actual game sound and play a permitted music section. Stop and listen back, first checking that the selected playback track contains the complete mix. If the recording is correct but the audience result differs, check the supported LIVE connection and the receiving tool’s audio settings. TKLive can organize the OBS instance and stream preparation; final sound still needs this source-to-viewer check.
- Test speech during loud game and music moments, not only silence.
- Listen for missing sound, distortion, echo and obvious lip-sync mismatch.
- Save the source names, output track, app version and a description of the failing step for support.
FAQ
Frequently asked questions
Start here for common questions about purchasing, access and system requirements.
Why can I hear music but my TikTok viewers cannot?
Your headphones may be receiving a monitoring-only route, or the music may be absent from the selected stream track. Check a recording of the complete mix, then the receiving LIVE route.
Does a game capture source always include game audio?
Do not infer audio from a moving game picture. Check the configured capture route and its mixer meter; options depend on the OBS version, operating system and source type.
Why does a recording contain my voice but no music?
Check which recording track the player selected and whether that track includes music. For a simple test, record one complete mix rather than judging a multitrack file from an arbitrary track.
Will turning every volume control to 100% fix quiet sound?
No. It can produce clipping or an unbalanced mix. Identify the quiet source and its input gain, then adjust against the real programme while listening.
REFERENCES
References
Content reviewed: October 18, 2026 · TKLive product team