> 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/let-guests-see-your-obs-scene.md).

# Let guests see your finished OBS scene

Let VDO.Ninja guests watch the finished OBS scene without a hall-of-mirrors effect or an audio feedback loop.

Use this when you bring guests into OBS with VDO.Ninja and want them to watch the finished scene in their room.

Using **Live Studio** at `/studio/`? Follow [Return OBS video to guests in Live Studio](https://docs.vdo.ninja/guides/live-studio-obs-return.md) for its Director button and guest invite controls.

{% hint style="success" %}
**The short version:** Put the clean VDO.Ninja Scene link in OBS, send the OBS picture back as the director's camera, and give guests a link containing `&broadcast`.
{% endhint %}

![Guests join the room, OBS loads the clean Scene link, OBS Virtual Camera becomes the director's video, and that video returns to guests whose links use broadcast mode. The director stays out of the Scene link.](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-f0afdd338a9289ae96f3328a446e7ac95cd33b92%2Fobs-flow-return-loop.svg?alt=media)

## What you need

* A VDO.Ninja room and its Director's Room
* OBS with the guests added as a Browser Source
* OBS Virtual Camera
* Headphones for everyone who speaks

## 1. Use the clean Scene link in OBS

The OBS Browser Source should use the room's **Scene** link, not a guest link or the Director's Room:

```
https://vdo.ninja/?scene&room=YOUR_ROOM
```

Scene links leave the director out by default. Keep it that way: do not add `&showdirector`, leave **The director will be performing as well, appearing in group scenes** unchecked when you create the room, and do not add the director's return to the layout OBS captures. Otherwise OBS captures its own picture over and over.

## 2. Choose what the guests should see

In OBS, click the **gear beside Start Virtual Camera**.

<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 with an arrow pointing to the Virtual Camera settings gear" width="330"><figcaption><p>Use this gear to choose the return picture. Image: <a href="https://obsproject.com/kb/virtual-camera-guide">OBS Project</a>.</p></figcaption></figure>

Choose **Program** for the live output, or **Scene** and a dedicated **Guest Return** scene without private producer notes. Click **OK**, then **Start Virtual Camera** before you select it in VDO.Ninja.

## 3. Use the director as the return video

1. Open the Director's Room: `https://vdo.ninja/?director=YOUR_ROOM`
2. Click **enable director's microphone or video**.
3. Select **OBS Virtual Camera** as the camera.
4. Select your normal microphone, or no microphone for a video-only return.

Give guests a room link containing `&broadcast`:

```
https://vdo.ninja/?room=YOUR_ROOM&broadcast
```

Guests then see the main director's video instead of every guest's video. They still hear one another.

{% hint style="warning" %}
Do not send the full OBS audio mix back to guests; they would hear themselves with a delay. Let VDO.Ninja carry the microphones and use Virtual Camera for the picture.
{% endhint %}

## 4. Optional: send the return through Meshcast v2

In a small room, the direct return has the least delay. But the director uploads one copy of the return per guest, so upload and CPU load grow as guests join. Meshcast takes one copy and sends it to everyone. Add `&meshcast` to the director link:

```
https://vdo.ninja/?director=YOUR_ROOM&meshcast
```

The guest and OBS links stay the same, and VDO.Ninja connects to Meshcast for you. `&meshcast` uses the current Meshcast service (v2); older links with `&meshcast2` still work. Meshcast adds a little delay.

## Link sets

| Link     | Small room, direct          | Larger room, through Meshcast  |
| -------- | --------------------------- | ------------------------------ |
| Director | `?director=YOUR_ROOM`       | `?director=YOUR_ROOM&meshcast` |
| Guest    | `?room=YOUR_ROOM&broadcast` | `?room=YOUR_ROOM&broadcast`    |
| OBS      | `?scene&room=YOUR_ROOM`     | `?scene&room=YOUR_ROOM`        |

Each link starts with `https://vdo.ninja/`. If the room has a password or other options, use them on all three links.

## Prevent echo and feedback

* Every speaker wears headphones.
* VDO.Ninja carries the conversation microphones; Virtual Camera carries the picture.
* Only one path carries music, clips or other program sound.

If guests must hear sound from OBS, send them a return that leaves out their microphones (a mix-minus). See [Return OBS clips and music to the main room](https://docs.vdo.ninja/guides/room-audio-obs-meshcast-and-private-talk.md#4-return-obs-clips-and-music-to-the-main-room). Make a test recording and ask each guest to confirm they do not hear a delayed copy of themselves.

## Other ways to share the return

[Send an OBS return feed to guests](https://docs.vdo.ninja/guides/send-an-obs-return-feed-to-guests.md) covers:

* a separate return publisher that guests select with `&broadcast=RETURN_ID`, which keeps the director's own camera separate;
* your own WHIP/WHEP server, or a stream that is already on one;
* a YouTube, Twitch or Meshcast player shared with **Share Website** (mute it, because its audio bypasses echo cancellation);
* screen-sharing an OBS projector window.

## Quick fixes

| Problem                             | What to check                                                                                                                               |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| The picture repeats inside itself   | Remove the director's return from the layout OBS captures. Make sure the Browser Source uses a `?scene&room=` link without `&showdirector`. |
| Guests still see individual cameras | Their invite must contain `&broadcast`, or `&broadcast=RETURN_ID` for a separate return publisher.                                          |
| Guests see no OBS return            | Start OBS Virtual Camera, enable the director's video, and select OBS Virtual Camera in VDO.Ninja.                                          |
| Guests hear themselves delayed      | Stop sending the full OBS audio mix. Use headphones and keep one audio return path.                                                         |
| A shared webpage causes echo        | Mute the webpage player or use headphones. Prefer the director or Meshcast return.                                                          |
| The return has too much delay       | In a small room, remove `&meshcast` and test the direct return.                                                                             |

## Related guides

* [Publish from OBS into VDO.Ninja](https://docs.vdo.ninja/guides/publish-from-obs-into-vdo.ninja.md)
* [`&broadcast`](https://docs.vdo.ninja/advanced-settings/video-parameters/broadcast.md)
* [`&meshcast`](https://docs.vdo.ninja/advanced-settings/meshcast-parameters/and-meshcast.md)
* [How to capture an application's audio](https://docs.vdo.ninja/guides/audio.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/let-guests-see-your-obs-scene.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.
