# Hardware Controllers
The MVP can be triggered directly by hardware MIDI controllers without a DAW or computer -- perfect for live performances, crew control, and portable setups.
***
## Overview
Any **class-compliant USB MIDI controller** or **5-pin DIN MIDI device** can trigger video and lighting clips on the MVP.
***
## Power Requirements
When operating without a computer (standalone), the MVP needs external power:
1. Connect the included **DC power adapter** to the barrel jack on the rear of the MVP.
2. Connect your MIDI controller.
3. The MVP powers on and is ready to trigger within a few seconds.
> **Note**: When connected to a computer via USB-C (HOST port), the MVP is powered by the USB connection and the DC adapter is not needed. However, some computers may not provide enough USB power for the MVP to run reliably while also powering a USB controller. If you experience issues, connect the DC adapter alongside the USB cable for redundant power. See [Troubleshooting](file:///5753738/8.-Reference/troubleshooting.md) for more details.
***
## Connection Methods
### USB MIDI Controllers
Connect your controller to one of the MVP's **USB-A ports**. The MVP provides power to class-compliant USB MIDI devices.
**Supported inputs**: Up to 2 USB-A ports for controllers, keyboards, or other USB MIDI devices.
### 5-Pin DIN MIDI
Connect a standard MIDI cable from your controller's MIDI OUT to the MVP's **MIDI IN** (5-pin DIN) port on the rear panel.
### Network MIDI (RTP-MIDI)
MIDI controllers that support RTP-MIDI can connect wirelessly via Wi-Fi or wired via Ethernet. See [Network MIDI Setup](/5.-triggering/network-midi-rtp-midi-setup.md) for configuration.
***
## Basic Setup
1. **Connect** your controller to the MVP (USB-A or 5-pin DIN).
2. **Configure clips**: Using a browser on your phone or computer (connected to the same network), navigate to `http://mvp.local` and assign video/lighting clips in the [Video Configuration](file:///5753738/2.-Video-Setup/video-configuration.md) and [Lighting Configuration](file:///5753738/3.-Lighting-Setup/lighting-configuration.md) pages.
3. **Set MIDI channels**: Ensure your controller is sending on the correct MIDI channel:
* **Video channel**: Default is Channel 1 (configurable in Video Configuration)
* **Lighting channel**: Default is Channel 3 (configurable in Lighting Configuration)
4. **Trigger**: Press pads/keys on your controller. Notes 1-99 trigger the corresponding clip. Note 0 triggers blackout.
***
## MIDI Controllers
Any class-compliant USB MIDI controller works with the MVP.
* MIDI notes trigger clips directly (note number = clip number)
* CC messages work if CC Trigger Mode is enabled (see [CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode.md))
* No LED feedback (the controller doesn't know which clip is playing)
Previously tested and confirmed working:
* Novation Launchpad Mini MK3
* Roland SPD-SX
* APC MINI
* Any standard USB keyboard or numeric keypad (via [Keyboard Triggering](/5.-triggering/usb-keyboards-hid.md))
### Akai APC Mini (original and MK2)
Since these controllers are not programmable, the MVP automatically maps the buttons and faders for you:
* **64 pads** (8x8 grid): Mapped to clips 0-63
* **8 faders**: Mapped to Effects Mode controls (CC 48-55) when Effects Mode is enabled
* **8 toggle buttons** (right column): Enable/disable individual effect controls
* **LED feedback**: Pads light up to show which clip is currently playing vs. ready
* Steady LED = clip assigned and ready
* Bright LED = clip currently playing
* Blinking LED = effect toggle active
***
## Standalone Wiring Diagram
***
## Multiple Controllers
The MVP supports **multiple MIDI sources simultaneously**:
* Two USB controllers via the two USB-A ports
* One 5-pin DIN controller
* Network MIDI (RTP-MIDI) devices
* A USB keyboard (via [Keyboard Triggering](broken://pages/6d5872daf5827074a30b1d4c052875b7cdfa381e))
All sources are active at the same time. Any connected device can trigger clips. The last trigger received wins (no priority system).
***
## Tips
* **MIDI note to clip mapping**: Note 1 = Clip 1, Note 2 = Clip 2, etc. Note 0 = Blackout. This is consistent across all trigger methods.
* **Check the Dashboard**: The Input Monitor shows every incoming MIDI event with the device name, which is invaluable for debugging controller issues.
* **Channel mismatch is the #1 issue**: If your controller isn't triggering clips, verify it's sending on the same MIDI channel configured in the MVP's Video or Lighting settings.
* **Controller note numbering varies**: Some controllers number notes starting from 0, others from 1, and the octave naming convention differs between manufacturers. The MVP's Dashboard shows the actual MIDI note number received -- use this to verify your mappings.
* **Slot switching from hardware**: Use MIDI CC #119 to switch between configuration slots A-E during a performance. See [Configuration Slots](/6.-configuration/configuration-slots.md).
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration.md) -- Assign clips and set MIDI channels
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration.md) -- Assign DMX clips
* [USB Keyboard Triggering](/5.-triggering/usb-keyboards-hid.md) -- Use a standard keyboard as a trigger pad
* [CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode.md) -- Trigger clips via CC #110
* [Network MIDI (RTP-MIDI) Setup](/5.-triggering/network-midi-rtp-midi-setup.md) -- Wireless MIDI controllers
* [Triggering Overview](/5.-triggering/triggering-overview.md) -- All trigger methods compared
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots.md) -- Prepare and switch between show configurations
---
# 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/hardware-controllers.md?ask=
```
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.