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

# \&noheadphones

Optimizes audio settings for guests using external speakers without headphones

Sender-Side Option! ([`&push`](https://docs.vdo.ninja/advanced-settings/setup-parameters/push.md))

## Aliases

* `&nhp`

## Options

Example: `&noheadphones`

This parameter takes no value. Adding it to a guest link enables the no-headphones audio profile.

## Details

`&noheadphones` is a convenience parameter for setups where guests are using external speakers and microphones without headphones, such as panel shows or in-studio multi-guest setups.

It forces the following defaults:

* **Echo cancellation**: ON
* **Noise suppression**: ON
* **Auto gain control**: ON
* **Voice isolation**: ON (if not already set)
* **Noise gate**: ON (if not already set)

This overrides [`&proaudio`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.md) or [`&stereo`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.md) disabling of echo cancellation, noise suppression, and auto gain control. Individual parameters like `&aec=0` can still override if needed.

### When to use

Use this when guests cannot wear headphones and are using external speakers. Without `&noheadphones`, a common problem is cascading echo: Guest A speaks, their audio plays through Guest B's speakers, Guest B's mic picks it up and sends it back, creating a feedback loop.

### Example guest link

```
https://vdo.ninja/?room=YOURROOM&password=YOURPASS&noheadphones&mediasettings
```

### Physical setup tips

Even with `&noheadphones`, some physical setup improvements help:

* Keep speaker volume as low as practical
* Position the microphone close to the speaker's mouth
* Point speakers away from microphones
* Prefer directional or dynamic microphones over wide-pickup condensers

### Advanced: combining with other features

* Add [`&noisegate=4`](https://docs.vdo.ninja/advanced-settings/audio-parameters/noisegate.md) to duck non-active speakers' microphones (more aggressive than the default gate)
* Use [`&noisegatesettings`](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-noisegatesettings.md) to tune gate sensitivity
* The director can use [`&mixminus`](https://docs.vdo.ninja/advanced-settings/other-parameters.md#mix-minus-and-mixminus) for N-1 routing to prevent self-return loops

## Related

{% content-ref url="/pages/-MZXM6dWB7twWeP1l2Va" %}
[\&echocancellation](https://docs.vdo.ninja/advanced-settings/audio-parameters/aec.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZXOdpBtFnhgcwPvIQW" %}
[\&denoise](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-denoise.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mj8Z0VEEeXvU7RMwuTI" %}
[\&noisegate](https://docs.vdo.ninja/advanced-settings/audio-parameters/noisegate.md)
{% endcontent-ref %}

{% content-ref url="/pages/tGoy09fN91prKCjzOlc7" %}
[\&proaudio](https://docs.vdo.ninja/advanced-settings/audio-parameters/and-proaudio.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/noheadphones.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.
