NVIDIA Broadcast lets Streamlabs Desktop use processed microphone audio or camera video through virtual Windows devices. For audio, select Microphone (NVIDIA Broadcast) in Streamlabs; for camera effects, add a video capture source and select Camera (NVIDIA Broadcast).
You can set up either route on its own or use both. Check NVIDIA’s current Windows, GPU and driver requirements first, then test the virtual devices and your scene before starting a live broadcast.
What Broadcast changes in Streamlabs
Broadcast takes a physical microphone or camera as its input, applies the effect you choose, and presents the result as a virtual device for supported applications. Streamlabs must select that virtual device to receive the processed signal. If you select your physical microphone directly in Streamlabs, its audio bypasses Broadcast’s microphone processing.
Think of the route as two steps: choose the physical input and effect in Broadcast, then choose the corresponding NVIDIA Broadcast device in Streamlabs. For example, if your microphone is connected to your PC, select it in Broadcast and enable the desired audio effect. Then direct Streamlabs to Microphone (NVIDIA Broadcast) rather than to the microphone’s original name.
The camera route is separate. Setting Broadcast as the microphone does not add a camera to your Streamlabs scene, and adding the Broadcast camera does not change your microphone selection. Decide which signal you need to process before configuring either application.
| Route | Configure in NVIDIA Broadcast | Select in Streamlabs | What to check |
|---|---|---|---|
| Microphone only | Physical microphone and desired audio effect | Microphone (NVIDIA Broadcast) in audio settings or an audio input source | Speak and confirm the processed input registers once |
| Camera only | Physical camera, desired camera effect and resolution | Camera (NVIDIA Broadcast) as a video capture source | Confirm the picture appears at the matching resolution |
| Both | Configure each input and its effect | Select the virtual microphone and add the virtual camera source | Test audio and video separately before testing the full scene |
This setup changes how Streamlabs receives your inputs; it does not replace the work of checking your stream’s content, connection or YouTube settings. If your goal is a video loop rather than a camera-led production, see how to make a YouTube live stream from a podcast video archive. That is a different workflow from routing a live microphone or camera through Broadcast.
Check Windows and hardware compatibility first
NVIDIA Broadcast’s virtual devices are for the described Windows setup. Do not assume the same devices or workflow are available on another operating system. Before downloading the app, compare your PC with NVIDIA’s current Broadcast system requirements. Requirements and feature support can change, so rely on the live NVIDIA information rather than an old list or a retailer’s product description.
The NVIDIA setup guide reviewed for this article lists Windows 10 64-bit, at least 8 GB of RAM, an internet connection for installation, and a GeForce RTX 2060, Quadro RTX 3000, TITAN RTX or higher GPU. Its regional guide also lists driver 570 or above. Treat these as version-sensitive figures, not a permanent guarantee: verify the GPU, operating system and driver details on NVIDIA’s current pages before installing or buying hardware.
A compatible-looking GPU name alone does not settle every question. Check whether the GPU in your exact PC appears in NVIDIA’s current requirements and whether the particular effect you want is supported. If the PC does not meet the stated requirement, do not plan on an unsupported workaround; choose another workflow or consult NVIDIA’s current support information.
Also check the practical basics before installation: you can sign in or download from the official source, your Windows account can install software, and the physical microphone or camera works in Windows. If a device is already missing or unusable before Broadcast enters the picture, setting up a virtual device is unlikely to clarify where the original problem lies.
A new GPU is not automatically necessary if your existing system qualifies. Equally, buying one based on an older guide is risky because the requirements can change. For always-on channels, separate the production choice from the input-effects choice: an ongoing stream may use a prerecorded loop or another production method and may not need your PC’s camera and microphone online at all. This guide to running a 24/7 YouTube stream with a prebuilt cloud streaming service covers that distinct operational decision.
Install and configure Broadcast
Download Broadcast from NVIDIA’s official site and follow its installation process. Once installed, open the app and choose the physical input you want it to process. NVIDIA’s Broadcast setup guide describes configuring the source and effects in Broadcast itself. The order matters: Streamlabs can only select a useful processed input after Broadcast has a source and the relevant effect configured.
For an audio-only setup, select the physical microphone in Broadcast, then enable the effect you intend to use. Avoid turning on processing just because the option exists; listen to the result with your actual voice and room conditions. Noise reduction or other processing may alter the sound, and no effect guarantees that every unwanted sound disappears or that every voice will sound natural.
For camera processing, choose your physical camera in Broadcast and configure the desired effect there. Set the camera resolution in Broadcast before adding or adjusting its Streamlabs source. NVIDIA’s directions put effect and source configuration in Broadcast; Streamlabs is where you select the virtual camera for the scene.
If Streamlabs is already open, close and reopen it after installing Broadcast if the virtual device does not appear in its device lists. This is a reasonable first check for a newly installed device, not a universal remedy. If it remains absent, confirm the installation and Windows permissions, then consult current NVIDIA or Streamlabs support rather than trying undocumented changes.
Select the Broadcast microphone in Streamlabs
There are two common ways to route the processed microphone. NVIDIA’s Streamlabs-specific instructions use Settings > Audio, then select Microphone (NVIDIA Broadcast) in Mic/Auxiliary Device 1. Streamlabs also documents using an Audio Input Capture source and selecting the same NVIDIA Broadcast microphone there. Labels and layouts can vary as the application changes, so use the route available in your current version.
If you use global audio settings, open Streamlabs’ settings, choose Audio, and set the microphone input to the NVIDIA Broadcast device. If your scene instead uses an Audio Input Capture source, add or edit that source and choose the Broadcast microphone from its device list. Do not leave the physical microphone selected for the same role while also adding the processed device as a second input unless you specifically intend to mix both signals.
Test before going live. Speak at a normal distance and volume while watching Streamlabs’ audio meter. Then listen to a local recording or use a private test method available to your channel, checking for a clear voice, clipping, silence, unexpected room sound or a second copy of the audio. A moving meter tells you that audio is reaching Streamlabs; it does not tell you that the sound is pleasant or that the correct microphone is being processed.
If the meter stays still, check the path one link at a time: the physical mic is selected in Broadcast, the effect is enabled if wanted, and Streamlabs is using the Broadcast virtual microphone rather than the raw input. Check Windows microphone permissions and Streamlabs’ microphone access as well; Streamlabs’ getting-started guide includes permission checks. If the device still fails, use the current support guidance for your exact application versions rather than assuming one cause.
This is particularly useful when an otherwise correct channel setup fails because the wrong input was chosen. It is also separate from YouTube stream-key problems: if your broadcast connects but YouTube rejects the key, use the channel-specific checks in this stream-key troubleshooting guide, rather than changing audio devices at random.
Optional: add the Broadcast camera to a scene
You do not need a camera source for microphone processing. If you want Broadcast’s camera effects, add a Video Capture Source or Video Capture Device to the relevant Streamlabs scene, then choose Camera (NVIDIA Broadcast) as its device. The source name can differ slightly between versions, but it is the capture source that receives camera video.
Set the camera resolution in Broadcast and make the Streamlabs capture source match it. Streamlabs notes that a mismatch can prevent the camera from displaying correctly. If the source is black or absent, verify that the Broadcast camera is selected, that the camera is available to the app, and that Windows and Streamlabs have camera permission. These checks are supported by the documented workflow; they are not a promise that every black-screen cause is resolved by them.
Keep the virtual camera source in the scene where you need it. If you have a starting scene, a camera scene and a standby scene, check each one where the camera is expected. A working preview in one scene does not mean another scene has the same source or visibility settings.
For an audio-only channel, leave the camera path out. Fewer active sources make it easier to identify which device is carrying the signal, and you avoid changing a working microphone configuration just to test a camera effect. You can add the optional camera later and verify it independently.
Match resolution and test the complete scene
Resolution is an explicit part of the camera route. First set the desired supported resolution in Broadcast. Then open the Streamlabs video capture source properties and use the same resolution. If the source does not appear, return to these two settings and compare them before changing unrelated scene or output settings.
Test the microphone and camera independently, then together if you use both. With the microphone, speak and check the meter and playback. With the camera, confirm the preview appears and looks as intended. With both enabled, check that the selected scene displays the expected picture while the audio meter responds to your voice. This catches a common mix-up: a correctly routed mic does not prove that the camera source exists, and a visible camera does not prove that processed audio is selected.
Before a real broadcast, review the scene you will actually use, not only a test scene. Confirm the right microphone device is selected, the camera source is visible if needed, and the correct scene is active. If you stream a fixed video loop rather than a live scene, these effects may not be part of that broadcast’s signal path. StreamNeo can remove the need to leave a personal computer running for a file-based 24/7 YouTube broadcast, but it is YouTube-only and does not replace a live Streamlabs camera-and-microphone production.
For other forms of continuous video, the source and delivery method matter as much as the scene. A Linux-based file loop has different setup requirements; see how to loop a video on YouTube Live with FFmpeg on Linux if that is the workflow you are considering.
Choose the smallest working route
You do not have to use both virtual devices. Choose microphone-only if you want audio processing and do not need a processed camera. Choose camera-only if the picture needs Broadcast effects but your microphone should remain on its existing path. Choose both only after each route works on its own.
This keeps troubleshooting grounded. If audio stops after adding a camera, you can compare the audio route with its earlier working state rather than assuming the two devices are one combined setting. If a camera fails after changing resolution, check the matching values first. Record the device selections and resolution that worked so you can restore them if a later Streamlabs or driver update changes the available options.
For a channel that runs unattended, a live PC-based scene also brings a separate operational requirement: the computer, Streamlabs, inputs and connection need to stay available. Broadcast effects address processing inputs, not the wider problem of keeping a live channel going when your workstation is off. If that distinction affects your choice, compare the production workflow before spending time on effects.
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
Can I use only the NVIDIA Broadcast microphone in Streamlabs?
Yes. Configure the physical microphone and audio effect in Broadcast, then select Microphone (NVIDIA Broadcast) in Streamlabs’ audio settings or an Audio Input Capture source. You do not need to add a camera source for this route.
How do I add NVIDIA Broadcast’s camera?
Add a video capture source to the Streamlabs scene and select Camera (NVIDIA Broadcast). Set the resolution in Broadcast and match it in the Streamlabs source; check camera permissions and device selection if the image does not appear.
Why is a Broadcast device missing from Streamlabs?
Check that Broadcast is installed and configured with the intended physical input, then confirm Streamlabs has microphone or camera permission as appropriate. Verify you are looking in the correct audio setting or scene source. If it remains missing, consult current NVIDIA or Streamlabs support because the documented checks do not cover every cause.
Will Broadcast work on any Windows PC?
No. NVIDIA lists specific operating system, GPU, driver and other requirements, and these can change. Check NVIDIA’s current system requirements and feature support for your exact PC before installing or buying hardware.