> 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/setup-parameters/audiodevice.md).

# \&audiodevice

Pre-configures the selected audio device

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

## Aliases

* `&adevice`
* `&ad`

## Options

Example: `&audiodevice=Cable_Output`

| Value                   | Description                                                                                                          |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------- |
| `0`                     | disable audio source automatically; no option to change it during setup is provided.                                 |
| `1` \| (no value given) | auto-select the default audio; no option to change it will be allowed.                                               |
| `Cable_Output`          | will match against "CABLE Output (VB-Audio Virtual Cable). Use any other string to match against other device names. |

## Details

It can be changed after the connection has been established. Useful for helping a remote guest skip-past the complex setup of their camera/audio.\
![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FEswmzJ9ULqYIDEhljEm4%2Fimage.png?alt=media\&token=e8a1c63e-cd4f-4ec3-90f3-69f604f50c70)

You can pass a string name to auto-select an audio device that has a label containing that same string.

You can pass a device ID as well; see [vdo.ninja/devices](https://vdo.ninja/devices) to see the device IDs (specific to VDO.Ninja's domain).

Setting this option to `&audiodevice=0` will also disable the guest's microphone, potentially allowing for guest connections that have no video or audio. You might do this if you needed midi-only transport, hidden IFRAME control, or just to chatting.

{% hint style="info" %}
See [vdo.ninja/devices](https://vdo.ninja/devices) to see the device IDs and device names. DeviceIDs are specific to VDO.Ninja's domain, while device names are not.\
\
This web-based tool will also auto-create links for you, just by clicking on the respective device.
{% endhint %}

There is a toggle in the director's room which adds `&ad` to the guest's invite link.![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FsQkpNYphKul87fS2g7qn%2Fimage.png?alt=media\&token=c95c7707-f0ad-4923-bdf0-266dbebf4874)

### Update in V22

`&audiodevice` can accept multiple audio devices now. `&audiodevice=cam,cable` for example, will select the camlink and virtual audio cable devices as an audio source when joining.

`&audiodevice={device name}` will now also now show the selected audio devices before joining, while `&audiodevice=1` or `&audiodevice=0` will still hide the option to change or see audio devices.

## Related

{% content-ref url="/pages/-MZXVHmvcjUdEV5-Ww3G" %}
[\&nosettings](/advanced-settings/buttons-and-control-bar-parameters/and-nosettings.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXSgRkt23F9uqG-Wsf" %}
[\&videodevice](/advanced-settings/setup-parameters/videodevice.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/setup-parameters/audiodevice.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.