> For the complete documentation index, see [llms.txt](https://support.4cast.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.4cast.world/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/pro-tools-configuration.md).

# Pro Tools Configuration

### 1. Create a new MIDI track

Navigate to the TRACK menu in the top bar.  and select NEW.

<figure><img src="/files/wRX0WUhNnmSgWFkt3W3p" alt="" width="208"><figcaption></figcaption></figure>

The "New Tracks" window will open. Set the following settings accordingly.    <br>

<figure><img src="/files/MMdzOPds24SDa6rvhjsU" alt=""><figcaption></figcaption></figure>

Press "Create".

### 2. Route MIDI track to MVP

Navigate to the "Track Output" menu of the newly created MIDI track.  (The area highlighted in the red box in the image below). Open the menu and select MVP from hardware output choices. Select MIDI output channel 1 for video cues or channel 3 for lighting cues.   \ <br>

<figure><img src="/files/zfheap5d54XyJDehS0Yp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Pro Tip: turn the track's MIDI INPUT to NONE to ensure no clips are triggered unexpectedly from other MIDI sources.&#x20;
{% endhint %}

### 3. Arrange MIDI in the track and play it back to the MVP


---

# 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://support.4cast.world/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/pro-tools-configuration.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.