If worship music is audible in the church but missing from the livestream, first find where the signal disappears: before OBS, inside its routing or processing, or after it sends the stream. The OBS Audio Mixer meter is the quickest clue; a flat meter and a moving meter point to different checks.
Do not assume the platform caused the silence, and do not raise gain at random. Follow the signal in order, test the same quiet passage after each change, and confirm the result from a viewer’s device rather than only from the control room.
Locate where worship audio disappears
The sound heard in the room is not necessarily the sound OBS is receiving. A console can send the worship mix to the sanctuary speakers while its USB output, bus, or cable to the streaming computer is muted or routed elsewhere. The broadcast path may also be correct at the input but lost through a muted OBS source, an unassigned track, or processing that cuts quiet material.
Reproduce the problem during rehearsal with a representative song. Include a quiet verse, a louder chorus, and the transition between them. Watch the live input indicator for the relevant source in OBS’s Audio Mixer while the music plays. A meter that stays flat suggests the signal is not reaching that point, or is being removed before the meter; a meter that moves means you should check OBS’s controls and the outgoing stream next.
Pay attention to the live indicator rather than the fading tail of the meter. A peak meter can take a moment to fall after sound stops; that decay is not evidence that music is still arriving. OBS’s Audio Mixer guide explains how to use the mixer to monitor sources. The meter is a diagnostic clue, not proof that viewers can hear the audio.
It helps to think of the route as a chain: playback device or music source, church mixer, connection into the computer, OBS source and processing, encoded stream, and remote playback. Write down what the music comes from and which mixer output feeds OBS before changing settings. If the programme uses a continuous playlist rather than a live band, the same principle applies: first identify the player and its selected output, then follow that output into the streaming path. The OBS guide to running a 24/7 Telugu devotional stream may help if you are also tracing a continuous playback setup.
Check whether OBS receives the input
Start at the source. Confirm that the music is actually playing, that its player is not paused or routed to a different output, and that the level is audible on the device that feeds the mixer. If the music is a computer playback source, check the selected device and its output level. If it comes from an instrument or playback system connected to a console, inspect that channel’s mute, fader, and routing to the streaming output.
Next, check the physical and digital route from the console to the streaming computer. A cable may be connected to an output that carries the room mix but not the broadcast mix. A USB connection may expose more than one device or channel pair; selecting a similarly named input in OBS does not guarantee it is the one receiving the console’s stream mix. If the mixer has a headphone or control-room output, use it to confirm the relevant send before changing OBS.
In OBS, identify the source that should carry the music. It may be a global desktop or microphone input, or a source added to a scene as an audio capture device. Confirm that the selected device matches the console connection and that it is active in the scene where the stream is running. Exact labels differ by operating system, OBS version, and mixer. OBS’s audio sources documentation describes the distinction between global devices and sources added in a scene.
If the input meter remains flat, do not spend time adjusting the stream’s output track yet. Trace the upstream route one link at a time: is there signal at the music source, at the mixer channel, at the mixer’s streaming send, and at the input device? OBS notes that its input meter is positioned after source filters but before the fader. If you suspect a filter is removing the signal, temporarily disable the source’s filters during rehearsal and watch whether the meter responds. Restore settings you need after the test.
Use the device’s own monitor or headphone output if it has one. Listen privately, not through the sanctuary speakers, so a delayed monitor signal cannot feed back into the room. If the music is present at the console’s monitor point but absent in OBS, the fault is likely in the send, connection, device selection, or a filter before the mixer indicator. That observation narrows the search; it does not identify a cause by itself.
Inspect OBS routing and mixer settings
If the OBS meter moves while the music plays, OBS is receiving some audio. Check that the source is not muted and that its fader has not been pulled down. Also check whether the relevant source is assigned to the audio track used for streaming. A source can show activity in the mixer while the stream’s selected track carries other sources or no music at all.
Compare the track assignment in the source or mixer controls with the track selected in the streaming output settings. Do not change several track boxes at once: note the current state, make one adjustment, and repeat the same passage. If a recording is available, check its audio-track configuration as well; recording and streaming can use different tracks, so an audible recording does not automatically confirm the live track.
Check whether the same physical device has been added twice. For example, the mixer’s USB input might be active as a global audio device and also as an Audio Input Capture source in the scene. OBS warns that capturing a device through both routes can create echo. Duplication does not always cause silence, but it makes monitoring harder and can create an audio problem of its own. Keep the route clear enough that you can tell which source is producing the meter movement.
Listen to the source in OBS using headphones, with monitoring routed privately rather than to the sanctuary PA. If monitoring is silent but the meter moves, inspect the monitoring device and its routing separately from the stream track. Monitoring silence and stream silence are not the same test. Conversely, hearing the music in the control room may only mean you are listening to the console, not to the OBS output.
If the church already streams other programme audio successfully, compare the working source’s track assignment and route with the worship music source. Avoid replacing an interface or buying a cable until you have identified a missing connection or incompatible input. A purchase cannot correct a muted console send, a source assigned to the wrong track, or a filter threshold set too high.
Check filters when quiet music cuts out
A useful clue is whether the music disappears only during quiet passages. A noise gate reduces or closes a source when its level falls below a configured threshold. This can be useful for reducing a microphone’s room noise between spoken lines, but a speech-oriented setting can also close on a soft piano, a quiet verse, or the tail of a sustained note.
During rehearsal, bypass the gate on the affected source and replay the same quiet passage. If the music remains audible with the gate bypassed, review the gate’s opening and closing thresholds and tune them against the actual music level. Do not copy a voice setting without testing it: the gate needs to respond to the signal you are processing. OBS’s noise gate documentation explains the filter’s threshold controls.
Check other filters on the same source as well, especially noise suppression intended to reduce background noise on a microphone. Processing designed for speech can alter music, and a filter may make a low-level passage seem to vanish even while louder sections remain. Bypass one filter at a time, replay the same passage, and note the result before changing another. OBS’s noise suppression guide describes that filter’s purpose; it is not a recommendation to apply it to a full worship mix.
A meter can help distinguish an OBS processing issue from an upstream one, but remember that OBS’s input indicator is after source filters. If it is flat while the source should be active, test the filters as well as the input route. For a clean comparison, turn off the suspected filter briefly rather than altering the console, source level, and output track together. Then restore or retune the processing as appropriate and test both quiet and loud passages.
Do not use a large gain increase as a substitute for fixing a gate or suppression setting. Raising gain may make quiet music louder, but it can also raise room noise or cause louder sections to peak. Change one control at a time and listen back for distortion, pumping, or abrupt cut-offs. OBS publishes meter alignment details, but those figures are reference points, not a universal target for every church mix; the aim here is a consistent, intelligible programme path.
Verify the outgoing stream and platform preview
When the meter moves and OBS monitoring sounds right, verify what the stream actually carries. Make a rehearsal recording and listen back to the section where the problem usually occurs. This checks the encoded programme rather than only the direct console feed. OBS recommends monitoring at the device and inside OBS, and recording a normal session for playback; its mixer guidance is a useful reference for those checks.
If available, make a private or unlisted live test and ask someone in another location to listen on a different device. A remote listener checks the route after OBS sends it, including the platform’s playback. Ask them to report whether the music is absent throughout, absent only at quiet moments, or replaced by a platform notice. Keep your own monitoring in headphones or another private output, not through the sanctuary PA, to avoid sending delayed audio back into the room.
If OBS’s meter continues moving and the recording contains music, but the remote live stream has a placeholder, warning, or interruption, inspect YouTube Studio’s live dashboard and notices. YouTube says that “All live streams are scanned for matches to third-party content, including copyrighted content in the form of another live broadcast.” Its copyright guidance for live streams says a live stream may be interrupted when third-party content is identified. That is a separate possibility from an OBS signal-path failure; do not diagnose it unless the dashboard or viewer’s stream behaviour supports it.
If your church has permission to use the music, check the relevant rights-holder and platform procedures rather than assuming a general licence resolves a particular live-stream notice. YouTube notes that licensed content can still be interrupted if the rights owner has not added the channel to its Content ID allowlist. Confirm the applicable licence and channel status with the licensor. Increasing OBS gain will not fix a platform interruption, just as a copyright notice does not explain a flat OBS meter.
Test the full audio path before service
Use a repeatable rehearsal rather than waiting for a service to expose the fault. Play the same song section that previously went silent, including its quietest passage. Monitor once near the source or mixer and once inside OBS, then make a recording or remote test so you can check the stream output. Keep a short note of the source, mixer output, OBS device, track assignment, filters, and result; this gives the next operator a route to verify rather than a collection of guesses.
A simple decision table keeps the checks in order:
| What you observe | Where to investigate first | Useful next check |
|---|---|---|
| Music plays, but the OBS meter stays flat | Before or at OBS input | Confirm source output, mixer send, selected device, connection, and source filters |
| OBS meter moves, but OBS monitoring is silent | OBS monitoring route | Check the monitoring device and private output separately from the stream track |
| Meter moves, but the recording or live stream lacks music | OBS stream or recording configuration | Check mute state and the track assigned to the relevant output |
| Quiet passages vanish but louder sections remain | Source processing | Bypass the gate or suppression filter one at a time and retest the same passage |
| OBS recording has music, but remote live playback shows a warning or interruption | Platform and rights status | Review YouTube Studio notices and the relevant rights-holder procedure |
These are starting points, not definitive diagnoses. A meter that moves tells you audio has reached that indicator; it does not prove the correct track is being encoded or that a remote viewer can hear it. A recording can also use a different track from the live stream. Confirm the stage that fails before you change equipment or conclude that the platform caused the issue.
If an existing mixer already has a suitable USB audio connection, configure that route before considering a separate interface. If the current console cannot provide a compatible signal to the computer, then compare an interface’s input type and count, connection compatibility, operating-system and driver support, and whether it fits the existing mixer. For headphones, consider long-service comfort, closed-back isolation in a noisy control room, wired compatibility, and durability. Neither purchase is a first diagnostic step; identifying the route may show that the problem is a mute, assignment, or processing setting instead.
If you also need a reference for configuring continuous playback in OBS, see how to stream a pre-recorded video as live on YouTube. For a service built around continuous devotional playback rather than a live worship mix, the operational questions differ; this guide to 24/7 devotional streaming alternatives addresses that separate setup. These links are not substitutes for tracing the audio path in your own mixer and OBS scenes.
Where the issue is that a computer must remain on to keep a file-based channel running, rather than a live mixer feed needing diagnosis, StreamNeo can remove the need to leave that computer switched on by running an uploaded video as a YouTube live stream. It does not replace the checks above for a church’s live audio route.
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 does my OBS stream have no audio?
First watch the relevant input in OBS’s Audio Mixer while the programme is playing. If the meter is flat, trace the source, mixer send, connection, selected device, and filters; if it moves, check mute state, track assignment, and the recorded or remote stream.
Why can I hear the worship music in church but not on the livestream?
The sanctuary PA and OBS may receive different outputs from the mixer. Check the mixer’s streaming send and the OBS input, then confirm the stream track and listen from a different device or location.
Why does the music cut out when it gets quiet?
A noise gate or other speech-focused processing may be removing low-level music. During rehearsal, bypass one suspected filter at a time and replay the same quiet passage before adjusting settings.
Can YouTube mute worship music during a live stream?
YouTube says live streams are scanned for third-party content and may be interrupted; licensed music may still require the rights owner to allowlist the channel in Content ID. Check YouTube Studio and the relevant rights-holder procedure, but do not assume a platform action without evidence or use it to explain a failed OBS input.