To use NVIDIA Broadcast with OBS, first choose your physical microphone and camera in Broadcast and enable the effects you need. Then select Broadcast’s virtual microphone or camera in OBS; OBS receives the processed feed, while Broadcast handles the effects.
This two-stage route is the part that is easy to muddle. If OBS is pointed at the physical microphone or webcam instead, it can bypass Broadcast’s processing. The steps below keep each app’s role clear and give you a way to check the result before recording or going live.
Check that your PC and Windows setup are supported
Start with the requirements on NVIDIA’s Broadcast product page. At the time of writing, NVIDIA lists a GeForce RTX 2060, Quadro RTX 3000, TITAN RTX or higher GPU, at least 8 GB of RAM, and 64-bit Windows 10. Its driver requirements list NVIDIA Studio Driver R570, Game Ready Driver R570, or NVIDIA RTX Enterprise Driver R570 and above. NVIDIA recommends an Intel Core i5 8600 or AMD Ryzen r5 2600 or higher, and notes that internet connectivity is needed during installation. Requirements can change between app versions, so check the current page before buying hardware or diagnosing a machine that does not meet the list.
The key point is that Broadcast is an RTX app, not a generic audio filter that OBS can supply on its own. NVIDIA’s FAQ identifies OBS Studio as a supported receiving app and says GTX graphics cards are not supported for the Broadcast app. That means having OBS installed, or having a camera and microphone that work in Windows, does not by itself establish that Broadcast will run on the PC. If the GPU is unsupported, treat that as a compatibility issue rather than a missing OBS setting.
Install or open NVIDIA Broadcast using NVIDIA’s current download and setup instructions. Complete any required setup before opening OBS, then connect the microphone or camera you intend to use. If you have several devices, give yourself a moment to identify the actual one you want: a USB headset microphone and a webcam microphone, for example, may both appear as available inputs. Selecting the wrong physical device in Broadcast leads to the wrong feed later, even if OBS is configured correctly.
For a channel that also relies on a continuous media loop, keep this camera-and-microphone setup separate from the content playback path. OBS can have media sources and capture devices in the same scene, but they serve different purposes. For looped content, see the practical notes on OBS media-source settings; the device route in this guide applies to live camera and microphone input.
Select the physical inputs in Broadcast first
Open NVIDIA Broadcast and find its input controls. Choose the real microphone as the microphone input and the real webcam or camera as the camera input, depending on which you plan to use. These are hardware sources: the microphone and camera connected to your computer, before Broadcast has applied any effects.
Do this selection in Broadcast, not in OBS. Broadcast uses the physical input as the source it processes and exposes a corresponding virtual device for another application to receive. In OBS, you will choose that virtual device in a later step. The simple sequence is physical device into Broadcast, then Broadcast virtual device into OBS.
If you want only processed audio, configure the microphone input and leave camera setup for later. If you want a processed camera as well, configure both. There is no need to add a camera source just because Broadcast is installed, or to route a microphone through Broadcast if you do not want its effects. Keep the device path as narrow as your use requires.
When the input list contains similar names, test one device at a time. Speak into the microphone or move in front of the camera and look for the relevant input activity in Broadcast. A headset may expose both a microphone and playback device; choose its microphone as the input, not its speakers. Likewise, if a laptop has a built-in camera and a USB camera, verify which image you see before moving on.
This first-stage check helps separate a hardware problem from an OBS problem. If the microphone or camera is unavailable in Broadcast, changing OBS settings will not make it appear there. Check that the device is connected and available to Windows, then reselect it in Broadcast. Once the correct physical input is shown there, continue to effects.
Enable only the effects you need
Choose effects in Broadcast according to the problem you are trying to solve. For audio, that might mean reducing background noise or room echo; for video, it might mean changing or softening the background. The exact set of effects depends on the current app version and device support, so use the controls present in your installation rather than relying on an older screenshot or list.
Turn on an effect and listen to or inspect the result before enabling another. NVIDIA’s setup guide cautions that running multiple effects increases GPU use and recommends enabling only the effects you need. More processing is not automatically better: for a devotional stream recorded in a quiet room, for example, a strong noise filter may make a steady harmonium or a soft voice sound unnatural. The sensible setting is the one that addresses a real issue without damaging useful parts of the sound or image.
Avoid applying the same type of processing twice. If Broadcast is filtering microphone noise, turn off similar noise removal in OBS or another audio-processing layer while you test. Two filters may alter the sound in ways that are hard to diagnose, and the second pass does not necessarily improve it. If the result is too thin or clipped, switch off the duplicate filter first and compare again.
There can also be GPU trade-offs when video effects and audio effects run together. Keep the scene and effects as simple as your broadcast needs, particularly if the PC is also encoding the stream. This is not a claim that any particular combination will fail; it is a reason to check the actual OBS preview and audio on your own machine. If a desired combination is unavailable in Broadcast, follow the app’s current supported combinations rather than trying to create an equivalent effect in OBS by guessing.
For normal Windows listening, keep your actual headset or speakers as the Windows output device if you want to hear system audio without routing it through Broadcast. NVIDIA’s guide advises against setting NVIDIA Broadcast Speakers as the default output for that use case. This output choice is separate from the microphone and camera path into OBS.
Choose Broadcast’s microphone in OBS
After the physical microphone is selected in Broadcast and its effects are set, open OBS and go to Settings > Audio. Under Mic/Auxiliary Audio, choose Microphone (NVIDIA Broadcast). The exact device label may be rendered slightly differently by Windows or an app version, but you are looking for Broadcast’s microphone device, not the name of the physical microphone.
This is the second stage of the route. OBS is not installing Broadcast or applying its effects; it is receiving the virtual microphone that Broadcast exposes in a supported Windows setup. If you instead choose the physical USB microphone in OBS, the signal can go straight to OBS and skip Broadcast’s processing. Keep the physical device selected in Broadcast, and the Broadcast-labelled device selected in OBS.
If you already have a microphone source in your scene, inspect its properties as well as the global settings. An existing source may still be pointed at the physical mic even after you change a global Mic/Auxiliary Audio setting. Avoid capturing the same microphone through both a global device and a separate source unless you deliberately need both; duplicated inputs can sound like an echo or cause confusing meter readings.
Use a short recording or a private test before relying on the route for a live session. Speak at the normal distance and volume you expect to use, then listen back through headphones. A meter moving only confirms that OBS receives audio; it does not tell you whether the effect sounds natural, whether the device is clipping, or whether the room noise has been reduced enough for your purpose.
If you are also capturing music or application sound in OBS, keep those sources distinct from the Broadcast microphone. This makes it easier to balance voice against playback and to locate the source of an unwanted sound. The guide to capturing application audio in OBS covers that separate path.
Choose Broadcast’s camera in an OBS scene
To use Broadcast’s processed video, add a Video Capture Source to the OBS scene. In the source’s device selector, choose Camera (NVIDIA Broadcast). Do not choose the physical webcam here if your goal is to use Broadcast’s camera effects; doing so can bypass the processed camera feed just as selecting a physical microphone can bypass processed audio.
Check that the source appears in the scene and that its preview shows the intended camera image. If you have multiple scenes, remember that each scene can have its own source arrangement. A camera source configured correctly in one scene will not necessarily be present in another. Use a clear source name such as “Broadcast camera” if that helps you distinguish it from a direct webcam source, but the device selection itself is what determines the feed.
You can use the Broadcast camera without using the Broadcast microphone, or the microphone without the camera. For instance, a channel may need a processed presenter voice but no on-screen presenter, while a small business may use a camera with a simple background effect and retain its regular audio chain. Set up only the source that belongs in the scene.
If the camera preview is black or frozen, first check that the physical camera is selected and active inside Broadcast. Then confirm the OBS source is set to the Broadcast camera device. Close another application that may be using the physical camera, if necessary, and reopen or refresh the OBS source. Do not assume that installing a virtual-device app makes its devices available on every operating system: this workflow is for supported Windows setups described by NVIDIA.
Test levels, sound and video before going live
With the route configured, make a deliberate test in OBS. Speak at the distance you plan to use, pause, and make a normal movement in front of the camera. Watch the audio meter and the video preview, then listen to a short recording if you can. The aim is to confirm both routing and quality: OBS should receive the intended microphone and camera, and the processed result should still sound and look acceptable.
Listen for signs that the processing is too aggressive. A voice that loses consonants, a room that seems to pump between silence and speech, or a background effect that cuts off hair or hands may mean the effect needs adjustment or should be disabled. These are practical observations, not proof of a specific technical fault. Change one setting at a time so you can tell which change affected the result.
Check the ordinary audio balance too. If a presenter is speaking over music or a bhajan track, make sure the voice remains understandable without making the playback unexpectedly loud. For a continuous stream, keeping the audio and video source setup distinct is useful when changing a playlist or replay. If you later need to replace material in a running loop, refer to adding videos to a running 24/7 stream, rather than altering the Broadcast input route.
A local test does not verify every part of a live broadcast. OBS’s preview confirms what it is receiving before you send it, but streaming involves additional settings such as encoder load and output bitrate. If your picture quality is the concern, use a separate bitrate guide such as YouTube 720p live-streaming bitrate guidance, and confirm the current platform requirements. Do not change Broadcast effects to solve a problem that belongs to stream output configuration.
For an always-on channel, consider whether a live camera and voice are needed throughout the day at all. A computer running OBS with camera effects is a different operating arrangement from playing a prepared video continuously, and it needs someone to maintain the inputs and review the scene. If the specific pain is keeping your own computer on merely to carry a prepared file, StreamNeo removes that computer-from-the-broadcast burden: you upload the file, provide the YouTube stream key, and the channel runs from the cloud. It is YouTube-only, so it is not a replacement for this OBS camera workflow.
Troubleshoot which device OBS is using
When the result is wrong, trace the route in order instead of changing several settings at once. First ask whether Broadcast sees the intended physical input. Next check that the intended effect is enabled there. Then inspect the OBS source or Settings > Audio to confirm it uses the matching Broadcast device. Finally, verify the OBS meter or preview. This sequence identifies whether the fault is at input selection, processing, hand-off, or the scene.
| Symptom | First check | Next step |
|---|---|---|
| OBS receives no microphone audio | Confirm the physical mic is selected in Broadcast and responds there | Choose Microphone (NVIDIA Broadcast) in OBS, then recheck the meter |
| OBS audio is present but unprocessed | Check whether OBS is using the physical mic directly | Select Broadcast’s microphone device and avoid duplicate filters |
| Camera preview is missing | Confirm Broadcast can see the physical camera | Refresh the OBS Video Capture Source and select Camera (NVIDIA Broadcast) |
| Sound is muffled or unnatural | Review the enabled Broadcast effects and any OBS filters | Disable duplicate processing and test one effect at a time |
| A device name is absent | Recheck Windows and Broadcast input availability | Confirm the app and operating system are supported, then restart the receiving app |
The table is a starting point, not a diagnosis of every Windows or driver fault. Device names and menus can change, and a camera may be held by another application. If a device disappears after sleep or a cable change, check it in Broadcast again before treating OBS as the source of the problem. Reopening OBS can help it refresh the devices available to it, but it will not correct a wrong physical input selected upstream.
If the desired Broadcast devices do not appear at all, verify the supported system requirements on NVIDIA’s current page and make sure Broadcast itself opens correctly. Do not assume that an OBS plugin or setting can create those devices on an unsupported machine. NVIDIA’s own FAQ and setup guide are the right references for current compatibility and effect behaviour; consult them again if an update has changed a device label or menu.
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
How do I use NVIDIA Broadcast with OBS?
Select the physical microphone or camera in NVIDIA Broadcast, then enable the effects you want there. In OBS, select Broadcast’s virtual microphone under Settings > Audio, or add a Video Capture Source and choose Broadcast’s camera. Test the meter and preview before going live.
How do I set NVIDIA Broadcast as my OBS mic?
In OBS, open Settings > Audio and set Mic/Auxiliary Audio to Microphone (NVIDIA Broadcast). First make sure the actual microphone is selected as Broadcast’s input; choosing the virtual device in OBS is the receiving step, not the physical-input setup.
Does OBS apply NVIDIA Broadcast effects?
No. Broadcast applies its effects to its selected input and exposes a virtual device for a supported receiving app such as OBS. OBS must use that device to receive the processed feed; choosing the original physical device can bypass Broadcast.
Can I use NVIDIA Broadcast outside Windows or without an RTX GPU?
Do not assume these virtual devices are available outside NVIDIA’s supported Windows setup. NVIDIA’s current FAQ says GTX GPUs are not supported for the Broadcast app; check the live requirements page for supported hardware, operating systems and drivers before troubleshooting.