> 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/active-speaker-highlight-and-talking-indicators.md).

# Active speaker, Highlight, and talking indicators

Feature the current speaker with active-speaker switching, Highlight, fixed solo sources in OBS, and talking indicators.

## Quick choice

| Goal                                                      | Use                                                                  |
| --------------------------------------------------------- | -------------------------------------------------------------------- |
| Show only the current speaker                             | `&activespeaker=1` or `&activespeaker=3` on a scene/view link        |
| Show everyone who is talking                              | `&activespeaker=2` or `&activespeaker=4`                             |
| Make the current speaker larger while others stay visible | `&activehighlight=2` or `&activespeakerfeatured`                     |
| Feature one guest by hand                                 | The director's **Highlight** button                                  |
| Custom OBS layout with fixed guest boxes                  | A large `&activespeaker` source plus separate `&solo` sources        |
| Green border or dot when someone talks                    | `&meterstyle=2` or `&meterstyle=3`; `&meterstyle=4` for your own CSS |
| Feature social chat messages                              | Social Stream Ninja (separate from guest video)                      |

## Automatic active speaker

Add `&activespeaker` (aliases `&speakerview`, `&sas`) to a viewer, room or scene link:

```
https://vdo.ninja/?room=ROOMNAME&scene=0&activespeaker=3&cleanoutput
```

| Mode | Shows                                                    |
| ---- | -------------------------------------------------------- |
| `1`  | One speaker at a time, including audio-only sources      |
| `2`  | Everyone currently talking, including audio-only sources |
| `3`  | One speaker at a time, video sources only                |
| `4`  | Everyone currently talking, video sources only           |

For most OBS layouts, use `3` or `4` so audio-only guests don't replace the video.

To stop rapid switching when people interrupt or laugh, add `&activespeakerdelay` (aliases `&speakerviewdelay`, `&sasdelay`) in milliseconds. In modes `1` and `3` it slows switching away from the current speaker; in modes `2` and `4` it keeps a speaker on screen that long after they go quiet.

```
https://vdo.ninja/?room=ROOMNAME&scene=0&activespeaker=3&activespeakerdelay=1200
```

{% content-ref url="/pages/-MZHeaXqdR9WQuzFCjZc" %}
[\&activespeaker](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/activespeaker.md)
{% endcontent-ref %}

{% content-ref url="/pages/C3wiMCwjXsgCwbWDJQUr" %}
[\&activespeakerdelay](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/and-activespeakerdelay.md)
{% endcontent-ref %}

## Automatic Highlight of the speaker

`&activehighlight=2` keeps everyone in the scene and makes the current speaker larger, using the secondary Highlight layout. `&activespeakerfeatured` is an alias.

```
https://vdo.ninja/?room=ROOMNAME&scene=0&activehighlight=2&cleanoutput
```

`&activehighlight=1` uses normal Highlight instead, which focuses on the speaker more fully.

* On its own, `&activehighlight` doesn't hide guests who aren't talking. Combined with `&activespeaker`, the usual hide/show behavior applies.
* It follows video-capable speakers, like `&activespeaker=3`, so audio-only sources don't take over.
* `&activespeakerdelay` works here too.
* The link must receive and process guest audio, so don't add `&noaudio` or `&noap`.

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

## Large speaker plus smaller guests in OBS

For exact positions, crops or per-guest filters, build the layout in OBS:

1. Add one large Browser Source with the automatic speaker view:

   ```
   https://vdo.ninja/?room=ROOMNAME&scene=0&activespeaker=3&cleanoutput
   ```
2. Add each guest as a smaller Browser Source using their solo link, with `&noaudio` so audio isn't duplicated:

   ```
   https://vdo.ninja/?view=GUESTID&room=ROOMNAME&solo&cleanoutput&noaudio
   ```

Replace `GUESTID` with the guest's stream ID; permanent IDs make this reusable between shows. Don't add `&noaudio` to the active-speaker source, since switching needs its audio levels. To keep it out of your mix, mute it in OBS instead.

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-eb3562fbb44382f73d0407266a7ee2350a9ddaa4%2Factive-speaker-layout-mock.png?alt=media" alt="Mocked OBS layout with a large active speaker and smaller fixed guest boxes"><figcaption><p>Mocked example: a large active-speaker source with fixed solo sources in OBS.</p></figcaption></figure>

{% content-ref url="/pages/C3Rjc1ablPEGKifNC2Y1" %}
[Active speaker layouts in OBS](https://docs.vdo.ninja/guides/active-speaker-layouts-in-obs.md)
{% endcontent-ref %}

{% content-ref url="/pages/0B2hIACeLpYnQexPND6Z" %}
[\&solo](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/and-solo.md)
{% endcontent-ref %}

## Manual Highlight

In the director room, press **Highlight** on a guest to feature them in scene outputs and room views that follow Highlight.

* Use a normal scene link for the OBS program: `https://vdo.ninja/?room=ROOMNAME&scene=0&cleanoutput`
* Hold `Ctrl` (Windows/Linux) or `Cmd` (macOS) while pressing **Highlight** to make the guest larger instead of replacing the layout.
* Add `&ignorehighlight` to a viewer or scene link that shouldn't follow Highlight.

### Mute follows Highlight

To make the highlighted guest the only unmuted guest, add `&highlightmute` (aliases `&hmute`, `&mutefollowhighlight`, `&mfh`) to the director link:

```
https://vdo.ninja/?director=ROOMNAME&highlightmute
```

You can still mute and unmute by hand, but the rule applies again the next time Highlight changes.

{% content-ref url="/pages/XdHazgMGdrbggiYIJscB" %}
[\&highlightmute](https://docs.vdo.ninja/advanced-settings/director-parameters/and-highlightmute.md)
{% endcontent-ref %}

## Talking indicators

```
https://vdo.ninja/?room=ROOMNAME&scene=0&meterstyle=2&cleanoutput
```

| Mode            | Shows                                                                               |
| --------------- | ----------------------------------------------------------------------------------- |
| `&meterstyle=1` | A VU-style meter                                                                    |
| `&meterstyle=2` | A green border around a talking guest                                               |
| `&meterstyle=3` | A small green dot when a guest talks                                                |
| `&meterstyle=4` | No built-in meter; adds `data-loudness` and `data-speaking` attributes for your CSS |
| `&meterstyle=5` | Pulses an audio-only avatar or background image while speaking                      |

<figure><img src="https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-823aec482da1458feafcbf21373aa86989005c89%2Ftalking-indicators-meterstyle-mock.png?alt=media" alt="Mocked talking indicators with a green border, dot, and audio meter"><figcaption><p>Mocked example: a green talking border, dot, and meter-style loudness feedback.</p></figcaption></figure>

For custom CSS, `data-speaking` is easier than raw `data-loudness`. `0` means quiet, `1` speaking quietly and `2` speaking loudly.

```css
video[data-speaking="2"] {
	outline: 6px solid #00ff66;
	outline-offset: -6px;
}

video[data-speaking="1"] {
	outline: 3px solid #99ffbb;
	outline-offset: -3px;
}
```

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

## API-driven switching

`&activehighlight=2` covers most featured layouts. For custom rules, a parent page, Companion or a script can decide who is loudest and update the layout using:

* `getLoudness` or `&pushloudness` reports guest loudness to a parent page.
* The `layout` API applies a custom layout object or switches predefined layouts.
* The `soloVideo` API action toggles Highlight for a guest.

{% content-ref url="/pages/ffAYMCMlMio4qiqqdJhS" %}
[IFRAME API Basics](https://docs.vdo.ninja/guides/iframe-api-documentation/iframe-api-basics.md)
{% endcontent-ref %}

{% content-ref url="/pages/PXjivO1rOxoewycX9ieZ" %}
[\&layouts](https://docs.vdo.ninja/advanced-settings/director-parameters/and-layouts.md)
{% endcontent-ref %}

## Featured chat messages

Featured YouTube, Twitch and other chat messages come from Social Stream Ninja, not from `&activespeaker` or Highlight.

{% content-ref url="/pages/2pGU9TxBaXEy72kvDG33" %}
[Social Stream Ninja](https://docs.vdo.ninja/steves-helper-apps/social-stream-ninja.md)
{% endcontent-ref %}

## Troubleshooting

If the active speaker never switches:

* Make sure the link receives audio, and remove `&noap`; loudness features need audio processing.
* Try `&meterstyle=2` to confirm VDO.Ninja detects who is talking.
* Use `&activespeaker=3` if audio-only sources take over the scene.

If it switches too quickly, add `&activespeakerdelay=1000` to `2000`, or use manual Highlight for full control.


---

# 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/active-speaker-highlight-and-talking-indicators.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.
