OBS audio monitoring lets you hear selected sources locally; it does not, by itself, determine what viewers hear. Choose a monitoring device, set a mode for each source, then trace every capture path and audition a rehearsal recording to catch missing or doubled audio.
For a church service, the right choice depends on whether the source already reaches OBS through a mixer, an interface, or desktop audio. Labels and behaviour can differ with your operating system, OBS version, interface, and mixer, so use the workflow below as a way to test your setup rather than a promise that every menu will look identical.
What OBS audio monitoring does
Monitoring is a local listening route. When you ask OBS to monitor a source, OBS sends that source to a device you choose, such as the headphone output on a computer or an audio interface. This lets an operator hear media playback, a microphone, or another source without relying on the room loudspeakers.
The local monitor route and the programme mix sent to YouTube are related, but they are not the same outcome. A source can be audible in headphones and absent from the stream, or included in the stream while not being sent to the operator’s headphones. The source’s monitoring mode and its other routing determine which result you get.
That distinction matters during worship. A pre-recorded hymn or service video may enter OBS as a media source while the computer’s output is also captured as desktop audio. If OBS monitors the media source through the computer output and captures that output again, it may add a second copy to the outgoing mix. Depending on timing and the paths involved, listeners can hear echo, a hollow sound, or a level jump.
Monitoring is also a practical check: an operator can listen for a silent cue, an unexpectedly loud track, or a channel coming through only on one side. But listening to headphones alone does not establish what the stream contains. Confirm that separately using OBS’s meters and a test recording.
For a church using pre-recorded material, the guide to configuring OBS VLC Video Source is useful context for the playback source itself. Keep the question here narrower: where does its sound go, and which of those routes reach the stream?
Choose the Monitoring Device
In OBS, open Settings → Audio and look for Monitoring Device. Select the output where the operator should hear monitored sources. Depending on the room and equipment, that might be the computer’s headphone jack, the headphone output on an interface, or a mixer or monitor output connected to the operator’s listening point.
Choose an output that can actually be heard during the service. If the operator wears headphones plugged into the interface, selecting the computer’s built-in output may send monitoring somewhere else. If headphones are connected to a mixer, confirm that the mixer is receiving the selected output and that its headphone level is turned up. A device name in a menu is not proof that the audio is physically reaching the intended socket.
Make the selection with the equipment in its normal operating state. Some devices appear or disappear when connected, powered, or selected as the system output; available names also depend on the operating system and drivers. If the intended device is missing, check that it is connected and recognised by the system, then reopen OBS settings. Avoid changing system output devices in the middle of a live service without first confirming what other audio depends on them.
Once selected, test monitoring with a source you can recognise, at a modest headphone level. Speak into a microphone or play a short, known piece of media and confirm that it reaches the operator’s ears. If the source is audible in OBS’s mixer meter but not in the headphones, investigate the monitoring device and physical connections before changing the stream mix.
The OBS Audio Mixer Guide describes the monitoring controls and recommends listening to a recording before going live. Treat that as part of setup, not merely a troubleshooting step after a service has sounded wrong.
Open Advanced Audio Properties
The monitoring mode is set per source in Advanced Audio Properties. In the OBS audio mixer, use the source’s context menu or the mixer controls to open the advanced properties window. The exact route to that window and the labels around it may vary between OBS versions; if the menu differs, look for the advanced audio options associated with the mixer.
Identify the source before changing its mode. A church scene might contain a microphone or mixer feed, a media source, desktop audio, and other devices. Names such as “Audio Input Capture” are not always descriptive enough to tell you what is connected. Rename sources to reflect their actual role, if that can be done without disrupting an existing scene, and test them one at a time.
Advanced Audio Properties also gives you a place to inspect related source settings, including whether a source is assigned to the intended channels. OBS’s standard channel configuration is stereo, but the physical source or routing can still result in audio on only the left or right side. Confirm the sound in headphones and in a recording rather than assuming a visible meter represents a balanced, intelligible mix.
There is another potential duplicate to check before setting monitoring. OBS cautions that capturing the same device both as a global audio device in Settings → Audio and as a scene-specific Audio Input/Output Capture source can cause echo. If you use both approaches, establish whether they are intentional and whether they represent distinct signals. The OBS Audio Sources Guide explains the available source types and platform-specific distinctions.
Select a monitoring mode that fits the route
OBS commonly offers three choices: Monitor Off, Monitor Only, and Monitor and Output. Read them as routing decisions, not as quality settings. A mode should be chosen based on whether the operator needs to hear a source and whether that source is already reaching the outgoing mix by another path.
| Mode | Local monitoring | Included in OBS output by this setting | When it may fit |
|---|---|---|---|
| Monitor Off | No | No additional output route from monitoring | The operator does not need to hear this source through OBS, or another monitoring route is in use |
| Monitor Only | Yes | Not through this monitoring setting | The source is already included in the stream through a separate capture path |
| Monitor and Output | Yes | Yes | The source needs both local monitoring and an OBS output route |
The table describes the purpose of the modes, not a guarantee about every device’s behaviour. Other source settings, system capture, and the equipment path still matter. After choosing a mode, check both the headphone output and a recording made with the actual scene.
Monitor Off is appropriate when OBS should not send the source to the selected monitoring device. It does not mean that the source cannot be part of the stream through its ordinary source route. A microphone can be part of the programme mix without being monitored locally through OBS, for example.
Monitor Only is useful where the source needs to be heard by the operator, but another path already puts the same sound into the stream mix. A common example is computer playback that OBS captures as desktop audio: monitoring the media source locally may be needed, while sending that media source to output as well could repeat the sound. Confirm this on the actual setup; do not assume desktop audio is enabled or capturing the same output.
Monitor and Output sends the source to the operator’s selected monitoring device and includes it in OBS’s output through that source’s route. It can suit a media source that OBS is not otherwise hearing. If a separate desktop or interface capture also contains the same sound, however, the stream may receive both paths.
For a service that uses both live microphones and recorded material, make the decision for each source rather than applying one mode to the whole mixer. The 24/7 devotional stream setup guide covers broader channel preparation; the audio decision still depends on how your particular room and playback sources enter OBS.
Trace the church’s active audio signal paths
Before changing modes, write down the source and destination of each sound. A simple sketch on paper is enough. For example: “pulpit microphone → mixer → interface → OBS input” and “service video → computer playback → OBS media source; desktop audio capture on/off”. Add where the operator’s headphones connect. This makes duplicate routes easier to see than a list of device names alone.
A typical church setup may have several distinct paths:
- Worship microphones and instruments may be mixed at the sound desk and sent as one feed into an interface connected to OBS.
- A pre-recorded video may be an OBS media source, with its sound coming directly into the scene.
- Computer audio may be captured separately as desktop or output audio, depending on the OBS configuration and operating system.
- The operator may listen from the interface, the computer’s headphone output, or a mixer monitor bus.
These are examples, not assumptions about your installation. A mixer may send a separate monitor mix; an interface may route playback to its headphone output; an operating system may expose audio devices differently. Trace what is physically connected and what OBS meters respond to.
To distinguish routes, mute or disable one source at a time during rehearsal and observe the meters. If muting the media source leaves the same music visible on a desktop-audio meter, OBS is receiving another path. If muting desktop audio stops the music while the media-source meter remains active, the media source may still be reaching OBS separately. Restore each source after the test and note the intended arrangement.
Be cautious with global devices and scene-specific captures. If one physical input is selected globally and added again as a scene source, OBS may receive that device twice. Conversely, removing a global device can leave a scene without audio if no other source replaces it. The goal is not to prefer one architecture universally; it is to know which source carries each sound and prevent accidental duplication.
This signal-path check is especially important if you are adapting a computer used for other tasks. The Linux OBS settings guide discusses a platform-specific setup; do not carry its exact device labels over to Windows or macOS. Use the same principle on any system: verify the active capture and playback endpoints in the room where you will operate.
Check for doubled audio in the audience-facing stream
The audience-facing test is a recording, not just what the operator hears locally. With the service scene active, record a representative section that includes speech, music, and a media playback cue. Use the same scene transitions and playback controls planned for the broadcast. Then listen to the recording through a separate playback route, ideally headphones, and check for echo, doubled musical transients, unexpected changes in level, missing content, and left-right imbalance.
If you hear a duplicate, trace it back systematically. First identify whether the sound is entering OBS as a media source, an interface or mixer input, desktop audio, or more than one of these. Then temporarily disable one candidate path and make another short recording. A change in the result helps identify the route; it is safer than toggling several settings together and losing track of which change mattered.
Do not use the headphone monitor alone to diagnose what viewers hear. Its sound may include a local monitoring route that is not in the recording, or the recording may include a route the operator does not monitor. Compare the recording with the meters and the signal-path sketch. When a second capture path is intentionally needed, keep it only if the test confirms that it does not repeat the same programme sound.
Watch the OBS meters while a reader, singer, or musician performs at a representative level. OBS’s technical guide explains that 0 dBFS is the digital maximum and that material at or above that ceiling can clip in a recording or stream. The guide also describes -20 dBFS as an Alignment Level and -9 dBFS as a Permitted Maximum Level in its meter model. These are meter references in OBS’s guidance, not universal loudness targets for every church or platform. Keep peaks below the digital ceiling, and listen for intelligibility and balance rather than trying to make every meter reach a particular number.
A meter shows signal level, but it cannot tell you whether the sermon is clear over music or whether a doubled path sounds distracting. Listen to the recording at a sensible level. If a sound is hard to understand, adjust the mix or source routing and record again; do not assume that a green or active meter means the audience will hear a suitable result.
Verify settings on the actual setup
Rehearse with the operating system, OBS version, interface, mixer, headphones, and scene collection that will be used for the service. A setting tested on a laptop at home may not behave the same after connecting the church interface or changing the system’s output device. Menu names and available device labels can change, and the physical mixer may add a monitor route outside OBS.
Use a repeatable check before going live:
- Confirm the intended monitoring device is selected and connected to the operator’s listening point.
- Play a test source and confirm the expected source meter moves in OBS.
- Listen locally, then verify separately whether the source should be in the stream mix.
- Run through the scene and playback changes planned for the service, watching for a second meter that responds to the same sound.
- Record a short rehearsal and listen to the file before broadcasting.
This is worth doing again after a meaningful change, such as moving the headphones to another output, changing a source from global capture to a scene source, or replacing the interface. Keep a brief note of the chosen mode and the path it is meant to serve. That note helps another volunteer understand why a source is set to Monitor Only rather than changing it to Monitor and Output in an attempt to make the headphones louder.
If maintaining a continuous stream means the church computer cannot stay available as the playback machine, StreamNeo can take an uploaded video and run it as a YouTube live stream without that computer left on. That addresses the specific burden of keeping a local playback machine running, but it does not change the need to prepare the programme audio correctly or verify what the audience will receive.
For any always-on arrangement, rehearse the parts that actually apply: playlist transitions, media playback, scene changes, and the sound in a recording. If the channel includes a live mixer feed, test that feed too rather than assuming a recorded file proves the live route is correct. Keep the official OBS and YouTube guidance close at hand, since device behaviour and platform instructions can change; check the current pages before relying on a remembered label.
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 Monitor Only send the source to viewers?
Monitor Only is intended to send the source to the local monitoring device, not add it to OBS’s output through that monitoring setting. The source may still reach viewers through another capture route, so confirm the recording rather than inferring the stream mix from the mode name alone.
Should a church use Monitor and Output for a pre-recorded video?
Use it when the video’s sound needs to be heard locally and included in OBS’s output through that source. If the same computer audio is already captured elsewhere, a second route may duplicate it; map the paths and test a recording before deciding.
Why can the headphones sound right while the stream recording is wrong?
The headphones may be hearing a local monitoring route that is absent from the outgoing mix, or the recording may contain a capture path that is not in the operator’s monitor. Check the source meters and listen to a rehearsal recording on the actual setup.
Do the OBS labels work the same way on every computer?
No. Device names and behaviour depend on the operating system, OBS version, interface, and mixer routing. Use the labels as a starting point, then verify the real signal paths and the resulting recording.