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

# \&scenelinkcodec

Reference for the \&scenelinkcodec URL parameter in VDO.Ninja including behavior examples and related options.

#### **Description**

Appends a codec parameter to scene invite links generated by the director, allowing codec preference to be set for all guests joining through those links.

#### **Director-Side Option**

This parameter is primarily designed for iframe API usage to control codec selection for scene participants.

#### **Usage**

* **`&scenelinkcodec=h264`** - Adds `&codec=h264` to scene links
* **`&scenelinkcodec=vp8`** - Adds `&codec=vp8` to scene links
* **`&scenelinkcodec=vp9`** - Adds `&codec=vp9` to scene links
* **`&scenelinkcodec=av1`** - Adds `&codec=av1` to scene links

#### **Examples**

```
https://vdo.ninja/?room=roomname&director&scenelinkcodec=h264
https://vdo.ninja/?room=roomname&director&scenelinkcodec=vp9
```

#### **Details**

* Automatically appends `&codec=` parameter to generated scene links
* Affects all scene invite links created by the director
* Codec name is automatically converted to lowercase
* Intended primarily for iframe API implementations
* Does not affect existing connections, only new invites

#### **Technical Implementation**

When set, the parameter:

1. Stores the codec preference as `&codec=value`
2. Appends this to any scene invite URLs generated
3. Ensures consistent codec usage across all scene participants

#### **Use Cases**

* Forcing specific codec for compatibility reasons
* Ensuring consistent codec across all participants
* Automated scene management via iframe API
* Testing different codecs across sessions

#### **Notes**

* This is a niche parameter mainly for advanced/API usage
* The specified codec must be supported by participants' browsers
* Final codec negotiation still depends on browser capabilities
* Consider bandwidth and CPU implications of codec choice

#### **Related Parameters**

* [`&codec`](https://docs.vdo.ninja/advanced-settings/video-parameters/codec.md) - Sets codec for individual connections
* [`&scene`](https://docs.vdo.ninja/advanced-settings/mixer-scene-parameters/scene.md) - Specifies scene to view
* [`&director`](https://docs.vdo.ninja/advanced-settings/director-parameters/director.md) - Enables director mode
* [`&preferaudiocodec`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-preferaudiocodec.md) - Sets preferred audio codec


---

# 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/and-scenelinkcodec.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.
