> 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/advanced-settings/mixer-scene-parameters/view.md).

# \&view

Defines the stream(s) you are receiving, by their stream IDs

Viewer-Side Option! ([`&scene`](/advanced-settings/mixer-scene-parameters/scene.md), [`&room`](/advanced-settings/setup-parameters/room.md))

## Aliases

* `&streamid`
* `&pull`
* `&v`

## Options

Example: `&view=StreamID1,StreamID2`

<table><thead><tr><th width="188">Value</th><th>Description</th></tr></thead><tbody><tr><td>(string value)</td><td>stream ID to view; can be a comma-separated list of IDs</td></tr><tr><td>(no value given)</td><td>in a room, you don't see any other guests including the director</td></tr></tbody></table>

## Details

`&view` defines the stream or streams you are receiving, by their stream IDs.

<https://vdo.ninja/?push=streamid>\
<https://vdo.ninja/?view=streamid>

Optional if you are publishing a stream using [`&push`](/advanced-settings/setup-parameters/push.md).\
If the `&view` parameter is not added, the default behaviour will occur.\
If the `&view` parameter is provided, it will try to play any stream listed.\
If the `&view` parameter is provided, but no values are provided, no streams will play; only publishing will be allowed.

This is useful is you wish to publish a video into a group chat room, but only view video from specific known participants.\
This is also useful if you wish to create ad-hoc group chat sessions without using a group room.\
Videos will auto-load when they are available if not already.

You can use `&view` in a room combined with [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md) or [`&solo`](/advanced-settings/mixer-scene-parameters/and-solo.md) to watch one or more specified video feeds of the room:\
`https://vdo.ninja/?room=roomname&scene&view=streamid1,streamid2`

## Related

{% content-ref url="/pages/yE23sgyptLjxeY1J8LKs" %}
[Multi-Person Chat](/getting-started/multi-person-chat.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXP2U7678vEPo5Yxms" %}
[\&push](/advanced-settings/setup-parameters/push.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdvjAL58404IcgJBTn" %}
[\&scene](/advanced-settings/mixer-scene-parameters/scene.md)
{% endcontent-ref %}

{% content-ref url="/pages/PUw9v1bckPnJqvHKhnoa" %}
[\&include](/advanced-settings/mixer-scene-parameters/and-include.md)
{% endcontent-ref %}


---

# 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/advanced-settings/mixer-scene-parameters/view.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.