> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/guides/share-obs-virtual-camera-and-audio.md).

# Share OBS Virtual Camera and audio

Share an OBS scene and audio, choose a fixed Virtual Camera output, and switch between players without losing their voices.

Send **OBS Virtual Camera** for video and **VB-CABLE** for audio. This Windows walkthrough also covers fixed scenes and switching between two players. For the basic setup, see [Publish from OBS into VDO.Ninja](https://docs.vdo.ninja/guides/publish-from-obs-into-vdo.ninja.md).

## 1. Prepare the sending OBS scene and audio

Select the scene you want to share. Avoid capturing the VDO.Ninja preview inside that scene.

Follow the [audio setup](https://docs.vdo.ninja/guides/share-obs-audio-with-vdo-ninja.md#1-install-the-cable-and-keep-your-headphones-as-the-normal-output): install VB-CABLE, set OBS's **Monitoring Device** to **CABLE Input**, then enable monitoring for the sources to send.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-6fbab45641574338cc505e53a6ee2899c02cff9f%2Fadvanced-audio-properties.png?alt=media" alt="Advanced Audio Properties with Game Audio monitoring enabled and Discord and Microphone monitoring off"><figcaption><p>Example: send game audio while keeping voices out of the cable. Monitor Off does not remove voices from OBS's own stream or recording.</p></figcaption></figure>

OBS 32.2 calls this **Monitoring Enabled**; older versions use **Monitor and Output**.

## 2. Choose what Virtual Camera shows

Click the **gear beside Start Virtual Camera** in OBS's Controls dock.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-9437edb7d2f31184cd6a2577c20725bd6a8da3e0%2Fvirtual-camera-settings-button.png?alt=media" alt="OBS Controls dock with an arrow pointing to the gear beside Start Virtual Camera" width="330"><figcaption><p>Use this gear to choose the camera picture. Image: <a href="https://obsproject.com/kb/virtual-camera-guide">OBS Project</a>.</p></figcaption></figure>

| Output Type           | What viewers see                                             |
| --------------------- | ------------------------------------------------------------ |
| **Program (Default)** | The current Program output; follows scene switches           |
| **Preview**           | Your Studio Mode preview, including edits before Transition  |
| **Scene**             | The scene chosen in Output Selection, independent of Program |
| **Source**            | Only the source chosen in Output Selection                   |

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-1376c10420574ec5695abbac3457baf9752d78de%2Fvirtual-camera-program.png?alt=media" alt="OBS Virtual Camera dialog with Program Default selected" width="398"><figcaption><p>Program follows normal scene changes. In Studio Mode, click Transition to change Program.</p></figcaption></figure>

### Keep one scene on the camera

Set **Output Type → Scene**, then choose your scene in **Output Selection** and click **OK**. Use **Source** for a single camera or capture instead.

**The camera mode does not choose the audio.** The cable receives active, monitored sources; changing Program can stop a scene's audio even when Virtual Camera still shows its picture. Keep the required audio sources active and check the receiver after switching.

Choose the mode before the session: a change may require restarting Virtual Camera.

## 3. Start Virtual Camera and select both devices in VDO.Ninja

Click **Start Virtual Camera**. Open this publishing link with your own unique, unguessable stream ID:

```
https://vdo.ninja/?push=YOUR_UNIQUE_STREAM_ID&webcam&proaudio=1
```

Select the devices shown, check the preview and audio meter, then click **START**.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-d27c7c2b79870c2ff71ff96ec70b21ada85f977d%2Fvdo-camera-and-audio.png?alt=media" alt="VDO.Ninja with OBS Virtual Camera and CABLE Output selected" width="494"><figcaption><p>For game audio only, select CABLE Output without also selecting your microphone.</p></figcaption></figure>

Keep OBS and the publishing tab open. Give the receiver the matching link:

```
https://vdo.ninja/?view=YOUR_UNIQUE_STREAM_ID&proaudio=1
```

Use the same password on both links if you add one. [`&proaudio=1`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.md) preserves stereo and avoids voice processing; use headphones for conversation.

## 4. Add the feed to the receiving OBS

Create a **Friend Game** scene. Add a **Browser Source**, paste the view link, and enable **Control audio via OBS**.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-89767fcd3ed024a5ade3b93e215473fd0db8ec53%2Fobs-receive-audio.png?alt=media" alt="OBS Browser Source with a view URL, Width 1920, Height 1080, and Control audio via OBS enabled"><figcaption><p>Use your own view link. Width and Height size the browser canvas, not the incoming capture.</p></figcaption></figure>

Leave these two options unchecked to keep the feed connected between scenes:

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-bf1c240f0903d908afc23c4a7d0ee6b0077efb8c%2Fobs-keep-connected.png?alt=media" alt="Shutdown source when not visible and Refresh browser when scene becomes active are unchecked"><figcaption><p>Keep the page loaded. Page permissions can stay at their normal read-access setting.</p></figcaption></figure>

Click **OK** and use **Transform → Fit to Screen** if needed. For local listening, monitor this source to headphones on the receiving computer. Do not also play a second copy through captured desktop audio.

## 5. Switch between your game and your friend's game

Have your friend send **game audio only**. On the receiving computer, capture your microphone and Discord separately, and build these scenes:

| Source                                  | My Game | Friend Game  |
| --------------------------------------- | ------- | ------------ |
| Your game capture and application audio | Include | Exclude      |
| Friend's VDO.Ninja Browser Source       | Exclude | Include      |
| Your microphone                         | Include | Add Existing |
| Discord application audio               | Include | Add Existing |

Use the same existing voice sources in both scenes, or nest a shared **Voices** scene in both. After adding separate application captures, disable global **Desktop Audio** to avoid duplicate or unwanted game sound.

Switch scenes to change games; in Studio Mode, use **Transition**. Use **Cut** for an immediate handover rather than briefly mixing both games during a fade.

Keep the unwanted game out of the active scene, including nested scenes. Covering it with an image does not silence it. Make a short recording while speaking and switching both ways: only the selected game and both voices should remain audible.

## Change a camera or cable while publishing

Open VDO.Ninja's bottom **gear**:

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-81c8848e9de6840126a1cf39228581c5632f0c66%2Fvdo-settings-button.png?alt=media" alt="VDO.Ninja bottom control bar with the settings gear highlighted" width="284"><figcaption><p>Change devices without making a new stream link.</p></figcaption></figure>

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-28beb68c455326ff9699d3a6da1ee0d3a6a0bba4%2Fvdo-change-devices.png?alt=media" alt="Live VDO.Ninja settings showing Video Source, Audio Sources, and Audio Output Destination" width="485"><figcaption><p>Video Source and Audio Source(s) choose what you send. Audio Output Destination chooses where you listen.</p></figcaption></figure>

For a scene or game change, keep VDO.Ninja on **OBS Virtual Camera + CABLE Output** and make the change in OBS.

## Troubleshooting

| Problem                                      | Check                                                                                                                            |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Picture works but sound is missing           | Follow the [audio route](https://docs.vdo.ninja/guides/share-obs-audio-with-vdo-ninja.md): CABLE Input, monitoring, CABLE Output |
| Camera is missing or shows the wrong picture | Start it before opening VDO.Ninja; check the gear's Output Type and Output Selection                                             |
| Both games are audible                       | Remove duplicate captures, global Desktop Audio, and unwanted nested game sources                                                |
| Voices disappear or double                   | Reuse voice sources in both receiving scenes; exclude voices from the friend's cable feed                                        |
| Returning to a scene reloads the feed        | Disable Browser Source shutdown and refresh-on-activation                                                                        |

For direct publishing through OBS's streaming output, see the [Ninja OBS Plugin](https://docs.vdo.ninja/guides/using-ninja-obs-plugin-with-vdo.ninja.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdo.ninja/guides/share-obs-virtual-camera-and-audio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
