Record one app's sound in OBS on Mac: check the capture path first
You want a demonstration to contain one app's playback and your narration. Before adding another virtual audio device, check which OBS source owns each sound. Capturing a microphone, capturing an application and hearing your headphones are three different parts of the setup.
This guide gives you a small source inventory and a verification sequence. It is useful when a demo unexpectedly contains other desktop sounds, has a doubled voice, or saves without the app audio you heard. Use your own non-sensitive test material rather than a real meeting or private notification.
Match the instructions to OBS and macOS
The official OBS macOS desktop audio guide documents a macOS Audio Capture source in OBS Studio 30 and later on macOS 13 or later, with a choice of all desktop audio or a particular application. It documents a different Screen Capture route for OBS 28 and 29 on macOS 13 or later.
Record your OBS and macOS versions first. Use the documented source for that combination and choose the intended application in its available properties. Do not install an older guide's extra routing software simply because its screenshots look familiar.
OBS also documents macOS Screen Capture as able to capture audio on macOS 13 and later. That source's picture and audio behaviour needs its own inspection. Permission to capture does not decide which sources you included in a scene.
Give each intended sound one owner
Before a sample recording, fill out this source map:
| Intended sound | Where to inspect | What to write down |
|---|---|---|
| One application's playback | The selected app-audio source properties | App name and capture scope |
| Your narration | The intended microphone source | Exact input device and whether it is enabled |
| A second capture of either sound | Other scene sources and global audio settings | Any overlapping route that needs inspection |
| Your listening copy | Headphone output and monitoring choices | What you hear, separately from what is saved |
OBS's Audio Sources reference warns that adding a scene audio device already selected globally can cause an echo effect. Inspect the overlapping routes before changing microphone gain or blaming Bluetooth.
Do not remove an unfamiliar source blindly. Note its name and state so you can restore the scene. If a source serves another scene, make the narrowest change appropriate for this test.
Make a sample that can expose the wrong scope
Use a short piece of audio you own in the chosen app. Keep unrelated private apps and notifications out of the recording environment. If you deliberately compare another app, use another harmless sound you own and note whether you expect it to be excluded.
- Write the intended result: chosen app only, or chosen app plus narration.
- Inspect source properties, enabled states and any duplicate global device capture.
- Record a brief sample with a recognisable app sound and a separate spoken phrase if narration is intended.
- Stop, locate the saved file and play it outside the recording preview.
- Record which intended sounds are present, which unwanted sounds are present, and anything you cannot determine.
The saved sample is the useful handoff evidence. A moving meter or audible headphones alone does not establish its contents. Likewise, one successful sample is not a promise that a different app, scene or protected source will behave the same way.
Use the result to narrow the next change
If other app sounds are present, inspect the selected capture scope and additional sources. If the voice is doubled, inspect overlapping microphone paths and monitoring. If app playback is missing, check the exact chosen source and the saved sample before adding more routes.
Keep one result per change. A note such as “app sound present, narration absent in the saved sample” gives the next investigation a clear target. If an app restricts capture, respect that restriction and consult its documentation.
Download the one-page OBS source checklist for your recording notes. It contains blank observation fields, not a prescribed scene or tested configuration.
For the broader recorder-versus-microphone distinction, see the Mac screen-recording audio guide. For a microphone that changes after reconnecting headphones, use the input observation log. SoundBuddy does not configure OBS sources or record app audio.
Before the full demo: verify the saved sample contains exactly the sources you intended, then retain that scene and source note with the project.