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

# \&micpanning

Pan your microphone left or right before sending

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

## Aliases

* `&mpan`

## Options

Example: `&micpanning=120`

| Value                | Description                         |
| -------------------- | ----------------------------------- |
| (no value) \| `true` | Enable mic panning at center (`90`) |
| `0–89`               | Pan left (`0` = hard left)          |
| `90`                 | Center                              |
| `91–180`             | Pan right (`180` = hard right)      |

## Details

* Publisher-side effect: downmixes the mic to mono, applies gain trim to avoid clipping, then pans to stereo in the outbound WebAudio pipeline.
* WebAudio required: [`&noaudioprocessing`](/advanced-settings/audio-parameters/noaudioprocessing.md) (`&noap`) disables outbound processing; mic panning will not engage if set.
* Live control:
  * Local Settings shows a “Mic Pan” slider when mic panning is enabled.
  * Directors can adjust per guest via the advanced audio panel.
  * Also controllable via API messages (e.g., `requestChangeMicPanning`).
* Safari/iOS: uses a PannerNode fallback internally; same range and behavior.

## Related

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

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