> For the complete documentation index, see [llms.txt](https://academy.showcockpit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.showcockpit.com/showcockpit-for-windows/tutorials/protocol-conversion/osc-to-midi.md).

# OSC to MIDI

1\. Add the Required Elements

![](/files/-LuZre05DAOf_l7qWNle)

On the Elements section, click the Add button to add the required elements to the project:

* External Control > OSC > Generic OSC
* External Control > MIDI > MIDI Output

Click the toggle buttons on the the elements to enable them.

2\. Configure OSC Inputs

Double-click the Generic OSC element and add your OSC controls to the Inputs list:

![](/files/-LuZu-hr6Zke2Z_dNwI6)

* Name: name identifier of your control
* Address: the OSC address
* ValueIndex: in case the message carries more than one value, select which one to take (zero-based)
* Range: min and max values for internal normalization
* Type: button, fader or encoder
* Note: Name and ValueIndex must be unique (no duplicates)

3\. Map OSC controls to MIDI Output

Open the Mapping section and select the desired MIDI Output functions. Start by selecting the MIDI Output element on the left list (functions). Select a desired output (Note On, Control Change, etc.) and tune the parameters.

![](/files/-LuZuLOxLu4jWamflZaq)

Finally select the Generic OSC on the right list (controls) and assign the previously selected MIDI Out function to one of your controls.

{% hint style="info" %}
In case your previously mapped controls do not show up, you can click the **Refresh** button to reload the controls list.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.showcockpit.com/showcockpit-for-windows/tutorials/protocol-conversion/osc-to-midi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.