> 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/activespeaker.md).

# \&activespeaker

Auto-hides remote guests videos when added, if those guests are not speaking actively

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

* `&sas`
* `&speakerview`

## Options

Example: `&activespeaker=1`

| Value                   | Description                                                                             |
| ----------------------- | --------------------------------------------------------------------------------------- |
| `1` \| (no value given) | will only show one speaker at a time; the loudest or last-loud speaker                  |
| `2`                     | will show whoever is talking; mixed together; if no one is talking, just shows yourself |
| `3`                     | the same as `1`, but it will not switch to show audio-only sources (just video only)    |
| `4`                     | the same as `2`, but it will not switch to show audio-only sources (just video only)    |

In all four cases, if someone else is talking/active, your local preview will become a [mini-preview](/advanced-settings/video-parameters/and-minipreview.md) in the top right.

If you want the active speaker to become larger while other guests remain visible, use [`&activehighlight=2`](/advanced-settings/mixer-scene-parameters/activehighlight.md) or `&activespeakerfeatured` instead.

### Customize the delay on switching

By default, the active speaker switches fairly quickly, typically within a few hundred milliseconds of a louder speaker taking over. You can add a fixed added delay, which works with modes 1 and 3, which will delay how long it takes before a switch between speakers is made

`&activespeakerdelay`=2000, where 2000 is a value in milliseconds.

This will not impact modes 2 or 4

## Related

If looking to add a green box around active speakers, or make it just easier to see who is talking, please considering using \&meterstyle instead.

{% content-ref url="/pages/-MZN\_8Vi5yo7zBDLWI-U" %}
[\&meterstyle](/advanced-settings/design-parameters/meterstyle.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/SY52pPRCXvGfQIWjS8eI" %}
[\&motiondetection](/advanced-settings/mixer-scene-parameters/and-motiondetection-alpha.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/activespeaker.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.