# Triggering Overview

The MVP supports multiple ways to trigger video and lighting clips. You can use any combination of these methods simultaneously -- the last trigger received wins.

***

## Trigger Methods at a Glance

| Method           | Input                     | Video Clips                 | Lighting Clips                 | Clip Range            |
| ---------------- | ------------------------- | --------------------------- | ------------------------------ | --------------------- |
| **MIDI Notes**   | USB, DIN, or Network MIDI | Note 0-99 on video channel  | Note 0-99 on lighting channel  | 0-99                  |
| **MIDI CC #110** | USB, DIN, or Network MIDI | Value 1-99 on video channel | Value 1-99 on lighting channel | 1-99 + blackout (100) |
| **USB Keyboard** | USB-A keyboard/keypad     | Keys 1-0, Q-P, A-L, Z-M     | Shift + same keys              | 1-36                  |
| **Timecode**     | LTC audio or MTC MIDI     | Timeline-driven             | Timeline-driven                | Full show             |

***

## MIDI Note Triggering

The most common method. Your DAW, controller, or show system sends a MIDI note on the configured channel.

| Note           | Action                                              |
| -------------- | --------------------------------------------------- |
| **Note 0**     | Blackout (video goes black / DMX all channels to 0) |
| **Notes 1-99** | Trigger the clip assigned to that note number       |

**Key details:**

* The **video MIDI channel** (default: 1) and **lighting MIDI channel** (default: 3) are configurable in their respective settings pages
* **Note On** starts playback; note duration is irrelevant
* Stopping your DAW does **not** stop the MVP -- send Note 0 (blackout) to explicitly stop playback

> *DAW-specific setup:* [*Ableton*](/5.-triggering/daw-computer-triggering/ableton-live-setup.md) *|* [*Pro Tools*](/5.-triggering/daw-computer-triggering/pro-tools-setup.md) *|* [*Logic Pro*](/5.-triggering/daw-computer-triggering/logic-pro-setup.md) *|* [*Other DAWs*](/5.-triggering/daw-computer-triggering/other-daws-general-guide.md)

***

## MIDI CC Trigger Mode

An alternative to note triggering is using Control Change messages.&#x20;

* Uses **CC #110**
* Values 1-99 = trigger clip, value 100 = blackout
* Must be enabled in [System Settings](/6.-configuration/system-settings.md)

> *Details:* [*MIDI CC Trigger Mode*](/5.-triggering/midi-cc-trigger-mode.md)

***

## USB Keyboard Triggering

Any USB keyboard or numeric keypad connected to the MVP's USB-A ports can trigger clips.

* Number row (1-0) = clips 1-10
* QWERTY rows = clips 11-36
* **Shift** + key = lighting clips

Always enabled, no configuration needed.

> *Details:* [*USB Keyboard Triggering*](/5.-triggering/usb-keyboards-hid.md)

***

## Timecode Playback

For timeline-based show playback synced to SMPTE timecode.

* **LTC**: Audio timecode via 3.5mm input
* **MTC**: MIDI timecode via USB, DIN, or Network MIDI
* Supports continuous sync, variable speed, and transport control (MMC)

When timecode is active, manual triggers (MIDI notes, keyboard, CC) are suppressed.

> *Details:* [*Timecode Overview*](/4.-timecode-setup/timecode-overview.md) *|* [*Timeline Editor*](/4.-timecode-setup/the-timeline-editor.md)

***

## Hardware Controllers

MIDI controllers (USB or 5-pin DIN) can trigger clips directly without a DAW.

* Any class-compliant MIDI device works
* Multiple controllers can be connected simultaneously

> *Details:* [*Hardware Controller Setup*](/5.-triggering/hardware-controllers.md)

***

## Network MIDI (RTP-MIDI)

Send MIDI triggers wirelessly over Ethernet or Wi-Fi using the RTP-MIDI protocol.

* Works on Mac natively (Audio MIDI Setup)
* Works on Windows via free rtpMIDI app
* The MVP advertises as "MVP" on the network

> *Details:* [*Network MIDI (RTP-MIDI) Setup*](/5.-triggering/network-midi-rtp-midi-setup.md)

***

## Wiring Diagrams

Depending on your production needs, your setup will look like one of the following diagrams:

**Scenario A: Video Playback Only**

* Signal Chain: Computer → MVP → HDMI Display

<figure><img src="https://support.4cast.world/~gitbook/image?url=https%3A%2F%2F972130380-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJy0o1OGq5vpGIjXyRxmH%252Fuploads%252FxilLqdqTaBTllKK94bOW%252Fimage.png%3Falt%3Dmedia%26token%3Df7b3877a-775a-4a34-ba23-b7aa7ec48baf&#x26;width=768&#x26;dpr=3&#x26;quality=100&#x26;sign=4d3d7a3b&#x26;sv=2" alt=""><figcaption></figcaption></figure>

**Scenario B: Lighting Playback Only**

* Signal Chain: Computer → MVP → Ethernet → ArtNet Node → DMX Fixtures

<figure><img src="https://support.4cast.world/~gitbook/image?url=https%3A%2F%2F972130380-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJy0o1OGq5vpGIjXyRxmH%252Fuploads%252FLzxYnzZRumYKcSZHu4An%252Fimage.png%3Falt%3Dmedia%26token%3D41088a35-4adf-479c-b7d5-d6fbb0ae437f&#x26;width=768&#x26;dpr=3&#x26;quality=100&#x26;sign=81f50f63&#x26;sv=2" alt=""><figcaption></figcaption></figure>

**Scenario C: Video + Lighting Playback**

* Signal Chain: Computer → MVP → HDMI & Ethernet

<figure><img src="https://support.4cast.world/~gitbook/image?url=https%3A%2F%2F972130380-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FJy0o1OGq5vpGIjXyRxmH%252Fuploads%252F3wpaMu4wGUpuo6Mdhnae%252Fimage.png%3Falt%3Dmedia%26token%3D2abb25fd-f073-4261-abd0-b5aed59136ee&#x26;width=768&#x26;dpr=3&#x26;quality=100&#x26;sign=7eedeb6c&#x26;sv=2" alt=""><figcaption></figcaption></figure>

### Scenario D: Standalone (No Computer)

* Signal Chain: MIDI Controller → MVP → HDMI & Ethernet

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

***

## Trigger Priority and Interaction

* **All methods are active simultaneously** -- MIDI notes, CC, keyboard, and timecode can all be connected at once
* **Last trigger wins** -- if two triggers arrive at the same time, the most recent one takes effect
* **Timecode overrides manual triggers** -- when timecode is actively driving playback, manual triggers (MIDI notes, keyboard, CC) are suppressed to prevent conflicts
* **When timecode stops**, manual triggers resume automatically

***

## Slot Switching During Performance

You can switch between configuration slots (A-E) during a live show using **MIDI CC #119**:

| CC #119 Value | Slot   |
| ------------- | ------ |
| 10            | Slot A |
| 20            | Slot B |
| 30            | Slot C |
| 40            | Slot D |
| 50            | Slot E |

Video and lighting slots switch independently -- send CC #119 on the video channel to switch video slots, or on the lighting channel for lighting slots.

> *Details:* [*Configuration Slots (A-E)*](/6.-configuration/configuration-slots.md)

***

## Related Pages

* [Video Configuration](/2.-video-setup/video-configuration.md) -- Assign video clips
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration.md) -- Assign DMX clips
* [MIDI Reference](/8.-reference/midi-reference.md) -- Complete CC and note reference card
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard.md) -- Monitor triggers in real time


---

# Agent Instructions: 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:

```
GET https://support.4cast.world/5.-triggering/triggering-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
