> 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/api-and-midi-parameters/midiout.md).

# \&midiout

Broadcast MIDI commands to a remote computer's virtual MIDI device

General Option! ([`&push`](/advanced-settings/setup-parameters/push.md), [`&room`](/advanced-settings/setup-parameters/room.md), [`&view`](/advanced-settings/mixer-scene-parameters/view.md), [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md))

## Aliases

* `&midipush`
* `&mo`

## Options

Device indices start at 1, where an index of 0 implies "all". You can also select a device by its exact, URL-encoded name. You can refer to [`https://vdo.ninja/midi`](https://vdo.ninja/midi) for a list of available MIDI devices.

Examples: `&midiout=2` or `&midiout=MidiPipe%20Output%201`

<table><thead><tr><th width="275">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>0</code></td><td>listen to all MIDI input devices</td></tr><tr><td>(integer value; for example, <code>1</code>)</td><td>MIDI input device index, starting at 1</td></tr><tr><td>(exact device name)</td><td>the MIDI input device with that name</td></tr></tbody></table>

## Details

Allows for sending of MIDI signals to a remote computer. Mirrors even the channel ID.

Device names must match exactly and should be URL encoded. If no device matches the name, the name is ambiguous, or an index is out of range, no MIDI input is selected and a warning is written to the browser console.

The remote device must use [`&midiin`](/advanced-settings/api-and-midi-parameters/midiin.md) to accept the signal and a peer connection is needed for the signal to take place.

You can disable the video and audio of VDO.Ninja, but still have a basic data-only peer-connection, but using `&videodevice=0&audiodevice=0` or [`&novideo`](/advanced-settings/video-parameters/and-novideo.md)[`&noaudio`](/advanced-settings/audio-parameters/noaudio.md).

{% hint style="danger" %}
If testing locally, beware of feedback loops, where the MIDI output is fed back into the MIDI input, causing high CPU usage and a lot of MIDI messages. If testing locally, use two MIDI devices and explicitly select the input and output MIDI devices to avoid these feedback loops.
{% endhint %}

## Related

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

{% content-ref url="/pages/-Mc\_UOSBkF5dmJtHVpoX" %}
[\&midiin](/advanced-settings/api-and-midi-parameters/midiin.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/api-and-midi-parameters/midiout.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.