> 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/audio-parameters/and-channeloffset-1.md).

# \&playchannel

Will play either the left or right audio stream-only for an incoming stereo stream

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))

## Options

Example: `&playchannel=1`

<table><thead><tr><th width="202">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>1</code></td><td>Will play the left audio channel only</td></tr><tr><td><code>2</code></td><td>Will play the right audio channel only</td></tr><tr><td>3-6</td><td>Will play the selected channel</td></tr></tbody></table>

## Details

`&playchannel` will play either the left or right audio stream-only for an incoming stereo stream.

It will play back the selected channel as mono audio, dropping other channels from the playback. `&playchannel=1` is left channel; `2` is right; and if multi channel works for you, then you can target 6 different channels.

This is useful if you wanted to capture the left and right audio channels of a remote guest in OBS in different browser sources, without having to do any fancy audio routing on the studio side.

Both left and right audio channels are still sent; it's just during local playback that the non-selected channels are dropped, so it's not as efficient as local routing, nor will both channel be in exact sync anymore either.

This will not currently work in conjunction with [`&panning`](/advanced-settings/audio-parameters/and-panning.md) of [`&channeloffset`](/advanced-settings/audio-parameters/and-channeloffset.md); and will override those options.

Example usage: <https://vdo.ninja/?view=XXXXXXXX&stereo&playchannel=1>

## Related

{% content-ref url="/pages/-MZdu\_u8Xk\_baYJKhRNH" %}
[\&channels](/advanced-settings/audio-parameters/and-channels.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mc\_o2CAhf-h1\_-c4t3E" %}
[\&inputchannels](/advanced-settings/audio-parameters/and-inputchannels.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdu\_u8Xk\_baYJKhRNH" %}
[\&channels](/advanced-settings/audio-parameters/and-channels.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/audio-parameters/and-channeloffset-1.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.