> 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-inputchannels.md).

# \&inputchannels

Audio capture device to select N-number of audio channels; force mono or stereo capture

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Aliases

* `&channelcount`
* `&ac`

## Options

Example: `&inputchannels=6`

| Value             | Description                                 |
| ----------------- | ------------------------------------------- |
| `1`               | Audio capture device set to mono; 1 channel |
| `2`               | Audio capture device set to 2 channels      |
| `6`               | Audio capture device set to 6 channels      |
| (integer value X) | Audio capture device set to X channels      |

## Details

`&inputchannels=N` tells the audio capture device explicitly to select N-number of audio channels.

Setting [`&stereo=0`](/advanced-settings/audio-parameters/stereo.md) will set `&inputchannels=1` by default.

If using [`&proaudio`](/advanced-settings/audio-parameters/and-proaudio.md) you want want to disable stereo-audio capture, particularly if you are using an XLR to USB microphone preamp that has two channels, but only one microphone connected.

For example, if a guest joins and you can only hear them in the left or right channel, either add [`&mono`](/advanced-settings/audio-parameters/mono.md) to the view-link or add `&inputchannels=1` to the respective guest invite-link.

### Mono-specific alias

If looking for a memorable parameter to set a guest's audio input to mono (1-channel), [`&monomic`](/advanced-settings/audio-parameters/and-monomic.md) is the same as `&inputchannels=1`. This was added in VDO.Ninja v22.

## Related

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

{% content-ref url="/pages/-MZdv4RF\_FXSg\_0rR1eJ" %}
[\&mono](/advanced-settings/audio-parameters/mono.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZX2aBA5UfmoqedHAu5" %}
[\&stereo](/advanced-settings/audio-parameters/stereo.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-inputchannels.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.