# \&cutscene

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

## Aliases

* `&lowbitratescene`

## Options

Example: `&cutscene=ObsSceneName`

| Value            | Description               |
| ---------------- | ------------------------- |
| (OBS scene name) | The name of the OBS scene |

## Details

You can use the IRL-related command called `&cutscene` to specify an OBS cut scene to switch to when the bitrate drops below a threshold and return to the original scene when the bitrate recovers. (assuming the cut scene is active; it won't switch back from a scene that isn't the cut away scene)

The default bitrate threshold is 300-kbps, but you can use the existing [`&bitratecutoff=N`](/advanced-settings/settings-parameters/and-bitratecutoff.md) option to specify a custom one. Using `&cutscene` with [`&bitratecutoff`](/advanced-settings/settings-parameters/and-bitratecutoff.md) will override the behaviour of [`&bitratecutoff`](/advanced-settings/settings-parameters/and-bitratecutoff.md)'s other features. It won't start triggering until the bitrate has hit at least the threshold once. to use:

```
https://vdo.ninja/?push=XXX
https://vdo.ninja/?view=XXX&controlobs&bitratecutoff=300&cutscene=FML&remote
```

You can of course use this with [`&controlobs`](/advanced-settings/settings-parameters/and-controlobs.md)[`&remote`](/advanced-settings/settings-parameters/remote.md), to have the publisher change the scenes dynamically, and see what the current OBS scene is (if still connected).

{% hint style="warning" %}
Note that the OBS browser source needs the permissions to be set to high, to give VDO.Ninja permissions to change scenes.
{% endhint %}

{% hint style="warning" %}
Do not set the OBS browser source to "Shutdown" when not visible, as this will prevent things from being able to switch back.
{% endhint %}

When using `&cutscene` on a room scene, it won't trigger due to a director being in the room with no video, unless they are using [`&showdirector`](/advanced-settings/director-parameters/and-showdirector.md). `&cutscene` wasn't intended really for a group scene; just a solo link or view link, but this fix makes it at more usable with a group scene.

## Related

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

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

{% content-ref url="/pages/-MZX0aUm-36CtnkhYT1y" %}
[\&remote](/advanced-settings/settings-parameters/remote.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/settings-parameters/and-cutscene.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.