# Quick Start Guide - Videos
This guide will help you get your MVP up and running in under 5 minutes with Video triggered by MIDI Notes. Please check the GETTING STARTED section for the full MVP documentation.\
\
*Note: For* [*LTC Timecode*](/archive-v12-userguide/4.-ltc-timecode-setup/ltc-timecode-setup)*, MIDI CC, or* [*Lighting*](/archive-v12-userguide/3.-lighting-setup/lighting-configuration) *information, please refer to those guides.*
***
## 1. Connect & Power Up
1. **Unbox**: Open the travel case. You will find the MVP unit, USB cables, mounting screws, and a power adapter.
2. **Connect**: Use the included USB-C cable to connect the MVP 'HOST' Port to your computer.
* ***Note**: The MVP powers on automatically via USB connection.*
3. **Verify**: After a few seconds, the Status Display on your MVP will light up.
***
## 2. Access the Dashboard
1. **Open Browser**: On your connected computer, navigate to `http://mvp.local`.
2. **Connect Wi-Fi**: Once the Dashboard loads, click the Wi-Fi Icon to connect your MVP to the internet. (Required for updating your MVP and downloading Stock Videos).
***
## 3. Upload & Assign Videos
Click the Video Tab in the left-hand navigation menu to open **Video Configuration**.
### Option A: Upload Your Videos
Enable **EDIT MODE**, then drag and drop your video files directly onto the upload box.
* ***Supported Codecs**: H264, H265, MJPEG, VP8, VP9*
* ***File types**: .MP4 .MOV .MKV .MJPG .WEBM .JPG (still image)*
* ***Max Resolution**: 4K (30fps) or 1080p (60fps)*
### Option B: Download Stock Video
Don't have any videos yet? Search through half a million royalty-free videos, and download them directly to your MVP.
1. Click the **Search Stock Videos** button.
2. Type a keyword (e.g., "Ocean," "Hyper Tunnel", "Tiger," "Clouds").
3. Select your resolution and click Download.
### Assign to MIDI
Once uploaded, Use the dropdown menus to assign your videos to MIDI Notes (e.g., C#-2).
***
## 4. Play Your First Clip
#### If using a Laptop (DAW)
1. Open your DAW (Ableton, ProTools, Logic, etc.).
2. In your DAW's MIDI settings, enable MIDI Output to 'MVP'.
3. Create a new MIDI Track.
4. Set the Track Output to MVP.
5. Draw a note on the Piano Roll that matches your video assignment (e.g., C3).
6. Press Play. The video will trigger instantly.
*Detailed Instructions: \[*[*Triggering from a Computer (DAW)*](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering)*]*
#### If using Hardware (Standalone)
1. Connect the included Power Adapter to the MVP.
2. Connect your MIDI Controller to the MVP via 5-Pin DIN or USB-A.
3. Press the corresponding physical key/pad on your controller.
***
## 5. Verify
If you aren't seeing video, check the Status Display on the device or the Dashboard in your browser. It will show you exactly which MIDI note was received and which file is attempting to play.
# What's Included
Congratulations on your new MVP! Let's see what's in the box.
#### In the box
* Travel Case
* Your MVP
* Accessories:
* 1x USB-C to USB-A Cable
* 1x USB-C to USB-C Cable
* 4x M2 Screws (for mounting)
* Power Adapter
#### Device Status Indicators
* Heartbeat LED: Located on the bottom front. Pulses blue to indicate normal operation.
* Status Display: A dedicated OLED screen providing real-time feedback
* MIDI: Shows the last MIDI note received.
* File: Shows the latest triggered video file name. *Note: On first boot, this will display HDMI connection status.*
* ArtNET: Displays the IP address if an Ethernet cable is connected.
# Hardware Connections & Specs
All connection ports are located on the rear panel of the device.
#### 1. Power (USB-C & Barrel Jack)
The MVP is designed to be USB bus-powered via the HOST port when connected to a computer.
* Optional Power Supply: If you are using the MVP without a computer (standalone) or if your computer's USB ports are underpowered, use the included DC power adapter.
#### 2. MIDI Input (5-Pin DIN)
Standard 5-pin MIDI input for connecting MIDI controllers, pedalboards, or any other MIDI equipment directly to the MVP.
#### 3. Ethernet Port
A gigabit connection used for Lighting and network control:
* Art-Net: Outputs lighting data to Art-Net nodes. Up to 16 Universes.
* RTP-MIDI: Allows control of the MVP over a local network (Network MIDI).
#### 4. HDMI Output
Supports video displays up to 4K resolution. Connect this directly to your projector, video wall processor, or monitor.
#### 5. HOST Port (USB-C)
This is the primary connection for computer-based setups. A single USB-C cable handles three functions simultaneously:
* Power: Powers the MVP via USB bus power.
* MIDI: The MVP appears as a class-compliant MIDI device on your computer (no drivers required).
* UI Access: Provides access to the MVP User Interface. Once connected, open a browser and navigate to `http://mvp.local`.
#### 6. USB-A Ports
Connect external peripherals to control the MVP:
* USB MIDI Controllers: All Class-compliant MIDI devices.
* USB Keyboards: Trigger video and lighting cues via keystrokes.
#### 7. Audio In (LTC)
Accepts a Linear Timecode (LTC) audio signal for triggering video and lighting playback to an external timecode source.
#### 8. Storage Space: 100GB
Enough space for more then 10 hours of high quality 4K video or 27 hours of 1080p.
# The User Interface (UI)
Your Control Center.
The MVP features a powerful, built-in web interface that allows you to manage content, configure settings, and monitor performance in real-time. Because the software lives inside the device, you don't need to install any drivers or apps on your computer.
This guide covers how to access the interface and navigate its layout.
## 1. Connect & Power Up
1. **Unbox**: Open the travel case. You will find the MVP unit, USB cables, mounting screws, and a power adapter.
2. **Connect**: Use the included USB-C cable to connect the MVP 'HOST' Port to your computer.
* ***Note**: The MVP powers on automatically via USB connection.*
3. **Verify**: After a few seconds, the Status Display on your MVP will light up.
***
## 2. Access the UI
1. **Open Browser**: On your connected computer, navigate to `http://mvp.local`.
1. **Settings Icons**: Once the Dashboard loads, you'll notice three icons on the top right corner.
* **User Icon**: Opens the MVP Registration dialog box.
* **WIFI Icon**: Opens the WIFI Connection dialog box.
* **Settings Icon**: Provides access to Ethernet Settings, Beta Features, and this support site.
2. **Nav Bar Links**: On the left side of the UI, you can navigate between the Dashboard, Videos, Lighting, and LTC Timecode configuration pages.
Note: You can find details about each of those pages in their respective support docs.
## 3. Network Access
Once you have connected your MVP to WIFI, you can access the MVP UI without connecting USB to your computer. You can even access it from another room.
On your dashboard page, you will see the IP address that your Internet router has assigned to your MVP.
Anytime your MVP is powered on and connected to WIFI, you can use that IP address in your browser
# The MVP Dashboard
The Dashboard is your "Mission Control" for the MVP. It provides real-time monitoring of all system details.
#### Step 1: Connect the MVP's USB-C 'HOST' port to your computer
#### Step 2: Navigate to `http://mvp.local` in your web browser.
#### Dashboard Features:
1. **Playback Status**: Shows what's currently playing and elapsed time.
2. **MVP Version**: Displays current MVP Version and Update Status.
3. **Network Details**: Real-time IP details for both Wi-Fi and Ethernet interfaces.
4. **HDMI Status**: Detects connected display's details and resolution.
5. **Input Monitor**: a scrolling log of all incoming MIDI notes and LTC timestamps (useful for troubleshooting signal chains).
***
# Update Your MVP
We release feature updates and improvements 3–4 times per year. Keeping your MVP up to date ensures you have the latest features and stability improvements.
#### How to Update
1. On the MVP UI, click the Wi-Fi Icon to connect your MVP to the internet.
2. Check for Updates:
* When an update is available, a notification will automatically appear on the Dashboard.
* *Note: MVP's on the older version (1.0.x):* Click the MVP VERSION tab in the bottom-left corner.
3. Click Details to view release notes, then press the Download button. The MVP will request the package from the cloud and begin downloading (this may take a few minutes).
4. Click Apply Update. You will be shown an important warning dialog box. Read the warning, and when you're ready, click PROCEED to begin the update process.
> ⚠️ CRITICAL WARNING: DO NOT power off the MVP during the update process. Once you click "Proceed," be careful not to touch your MVP or the USB cable. Interruption during this process will render the device non-functional.
>
> Wait until the update process is complete and the browser refreshes before touching the device.
# Video Configuration
The Video Configuration page is where you upload content, manage your library, and assign specific video clips to MIDI notes.
* Prerequisite: Ensure you are connected to your MVP and have access to the web interface. *See \[The User Interface (UI)] for instructions.*
Click on the **VIDEOS** link on the left side bar to open the Video Configuration Page.
***
### 1. Global Video Settings
The top control bar contains settings that apply to the entire video playback system.
* **MIDI Channel**: Selects which MIDI Channel (1-16) the MVP listens to for video triggers.
* *Note: The Video and Lighting MIDI channels cannot be assigned to the same number.*
* **Video Mode**: (only visible when BETA FEATURES is enabled)
* Fast Trigger: The default playback mode.
* Effects Mode: Provides MIDI CC access to eight different video effect properties.
* **Loop Mode**:
* Loop: The video repeats indefinitely until a new note is received.
* Freeze: The video plays to the end and then freezes on the last frame. The last frame of the video will remain visible until the next video is triggered.
* Blank: The video plays to the end and then goes black until the next video is triggered.
* **Default Video (On Boot)**: Choose a specific video to play automatically as soon as the MVP powers up. This is perfect for a "Logo Loop" or "Walk-in" visual.
* **Edit Mode (Toggle)**:
* ON: Allows you to change settings and assignments, delete files, etc.
* OFF: Locks the interface to prevent accidental changes during a live performance.
***
### 2 SYNC CHANGES Button
Anytime a change is made to any of the video settings or MIDI assignments, the SYNC CHANGES TO PLAYBACK button will appear.
Pressing this button will make your changes live, immediately. For example, if you assign a new video to a note, and then press the SYNC button, you can immediately trigger that new video.
### 3. Media Library & Uploads
The Right Sidebar is your content manager.
#### Supported Video Codecs and File Types
The MVP supports a wide range of modern video formats.
* **Video Codecs:** H.264, H.265 (HEVC), MJPEG, VP8, VP9
* **File Extensions**: .mp4, .mov, .mkv, .mjpeg
* **Still Images**: .jpg (Images will display until a new note is received)
* **Resolution Limit**: Up to 4K (30fps) or 1080p (60fps).
#### Upload Videos
You can add content to the MVP in two ways:
1. **Drag & Drop**: Drag video files from your computer directly onto the "Upload Videos" box.
2. **Browse**: Click the box to open your computer's file picker.
Once your uploads are complete, the video files will appear in the Unassigned Videos list.
#### Search Stock Videos
Click this blue button to access of over half a million royalty-free videos. You can search by keyword, preview clips, and download them directly to the device.
* *Requires an active Wi-Fi connection.*
Check the Search Stock Videos section for instructions on finding and downloading stock videos.
#### Unassigned Videos
This list shows all video files currently stored on the MVP that are not assigned to a MIDI note.
* **Trash Icon**: Click the trash can next to a file to permanently delete it from the device storage.
* **Free Space**: The storage meter at the top of this section shows your remaining disk space.
* **Video Information**: Click on any filename to view details.
***
### 4. The Video Grid (MIDI Map)
The main area of the screen displays 100 cards, corresponding to the 100 MIDI notes (0–99).
* **The Notes**: Each card represents a specific MIDI note (e.g., `MIDI: C#-2`).
* **Blackout**: Note 0 (C-2) is always assigned to blackout. This will immediately stop video playback and the display will be all black
* **Assignment**: To assign a video, click the dropdown arrow in a card and select a file from your library.
* **Active State**: When a video is playing, its card pulses Green.
* **Removing**: Click the X icon to unassign a video from that note. *Note: This does not delete the file from the device; it only moves it back to the "Unassigned" list.*
* **Video Information**: Click the small filename at the bottom of any card to view details.
***
### 5. Video Slots (Banks)
The MVP features 5 independent memory banks called Slots (A through E). Each slot stores its own unique set of MIDI assignments, allowing you to manage multiple shows or setlists on a single device and switch between them instantly.
#### Accessing the Slots Menu
By default, the MVP uses Slot A. To access the menu:
1. Locate the Slot Name (e.g., "Main Show") next to the "Video Configuration" title at the top of the page.
2. Click the name to open the Slot Dropdown menu.
#### Managing Slots
**Switching & Syncing**: When you select a new slot from the list, a dialog box will appear giving you two options for how to handle the transition:
* **Sync to Playback**: This immediately updates your MVP. All incoming MIDI notes will now trigger the videos assigned in the new slot right away.
* **Not Now** (Background Editing): This loads the new slot into the UI for editing *without* interrupting the live show. The MVP will continue playing triggers from the previous slot (e.g., Slot A) while you arrange the files in the new slot (e.g., Slot B) in the background. You can sync the changes later when you are ready.
#### Advanced: Switching via MIDI CC
You can automate slot changes during a performance using your MIDI controller or DAW. Sending a specific CC Value on CC 119 will instantly load the corresponding bank.
| **Slot** | **MIDI CC Number** | **Value** |
| -------- | ------------------ | --------- |
| Slot A | 119 | 10 |
| Slot B | 119 | 20 |
| Slot C | 119 | 30 |
| Slot D | 119 | 40 |
| Slot E | 119 | 50 |
*Note: Slot changes via MIDI CC happen instantaneously, allowing for seamless transitions between different songs or show segments.*
***
> ⚠️ IMPORTANT: Video & Lighting Slots are Independent
>
> Video and Lighting playback operate completely separately. Switching the Video Slot does NOT automatically switch the Lighting Slot (and vice versa).
>
> When using CC 119 to automate slot changes, you must send the message on the correct MIDI Channel:
>
> * Send CC 119 on the Video MIDI Channel → Switches the Video Slot.
> * Send CC 119 on the Lighting MIDI Channel → Switches the Lighting Slot.
# Search Stock Videos
## Stock Videos Library
*For instructions on connecting to the MVP and accessing the user interface, please refer to the \[*[*The User Interface (UI)*](/archive-v12-userguide/1.-getting-started/the-user-interface-ui)*] guide.*
***
### Overview
The MVP includes direct access to a massive library of over half a million **royalty-free** stock videos. You can search, preview, and download content directly to your MVP.
Prerequisite: Your MVP must be connected to the internet via Wi-Fi to browse and download stock content.
***
### 1. Accessing the Library
1. Navigate to the **Videos** tab on the left-hand sidebar of the MVP UI.
1. Click the blue **SEARCH STOCK VIDEOS** button located on the right-hand column.
***
### 2. Searching & Browsing
Once the dialog box opens, you can find the perfect video for your show. Each search will show up to hundreds of videos to choose from:
* Search Bar: Type any keyword (e.g., "Ocean," "Cyberpunk," "Abstract").
* Filters: Use the dropdown menus to filter by Category, Type, etc.
***
### 3. Preview & Resolution Selection
Click on any thumbnail to open the Preview Window.
* **Preview**: Press the play button to preview the video before downloading.
* **Resolution Selector**: Use the dropdown menu to choose your desired resolution
***
### 4. Naming & Downloading
After selecting your resolution, click the Download button.
1. Name Your File: Enter a custom filename for the clip (the `.mp4` extension is added automatically).
2. Confirm: Click the DOWNLOAD button to save it to your MVP.
The video file will automatically appear in your **Unassigned Videos** List once the download is complete.
# Effects Mode
Effects Mode enables real-time video color and transformation effects, controlled by MIDI CC messages. This turns the MVP from a simple player into a live performance tool for VJs and creative workflows.
> ⚠️ IMPORTANT NOTES
>
> * Resolution: Effects Mode supports video playback up to 1080p 60fps. 4K videos are NOT supported in this mode.
> * Playback Interruption: Switching the Video Mode will immediately stop any currently playing video or lighting cue.
***
### 1. How to Enable Effects Mode
Because this is an advanced feature, it must be enabled in the settings first.
1. Enable Beta Features:
* Click the Settings Cog ⚙️ in the top right corner of the dashboard.
* Select Beta Features.
* Toggle the switch to Enable.
1. Activate Effects Mode:
* Navigate to the **Videos** tab, and enable **EDIT MODE**.
* Use the **Video Mode** dropdown at the top of the page to select **Effects**.
*
```
```
* Confirm the warning dialog to switch modes.
Your MVP is now ready.
***
### 2. MIDI CC Controls
Assign these MIDI CC numbers to knobs or faders on your controller to manipulate video in real-time.
| **Parameter** | **CC Number** | **Description** |
| ------------- | ------------- | ------------------------- |
| Brightness | CC 48 | Adjusts video brightness. |
| Contrast | CC 49 | Adjusts video contrast. |
| Hue | CC 50 | Shifts color hue. |
| Saturation | CC 51 | Adjusts color intensity. |
| Rotation | CC 52 | Rotates the video frame. |
| Scale | CC 53 | Zooms in/out. |
| Position X | CC 54 | Moves video Left/Right. |
| Position Y | CC 55 | Moves video Up/Down. |
#### Default Values
* **Standard Center**: Most effects (Brightness, Scale, Position, etc.) use a default value of **64** (Midpoint).
* **Rotation**: The default value is **0** (No rotation).
***
### 3. Resetting Effects (MIDI Notes)
You can instantly snap an effect back to its default state by sending a specific MIDI Note (on the Video MIDI Channel).
| **Reset Function** | **MIDI Note** |
| ------------------ | ------------- |
| RESET ALL EFFECTS | Note 110 |
| Reset Brightness | Note 111 |
| Reset Contrast | Note 112 |
| Reset Hue | Note 113 |
| Reset Saturation | Note 114 |
| Reset Rotation | Note 115 |
| Reset Scale | Note 116 |
| Reset Position X | Note 117 |
| Reset Position Y | Note 118 |
> ⚠️ IMPORTANT NOTES
>
> * Resolution: Effects Mode supports video playback up to 1080p 60fps. 4K videos are NOT supported in this mode.
> * Playback Interruption: Switching the Video Mode will immediately stop any currently playing video or lighting cue.
# Lighting Configuration
## Lighting Configuration
The Lighting Configuration page is where you record your DMX, manage your DMX library, and assign lighting clips to MIDI notes.
Prerequisite: Ensure you are connected to your MVP and have access to the web interface. See \[[The User Interface (UI)](/archive-v12-userguide/1.-getting-started/the-user-interface-ui)] for instructions.
Click on the LIGHTING link on the left sidebar to open the Lighting Configuration Page.
***
### 1. Global Lighting Settings
The top control bar contains settings that apply to the entire lighting system.
* **MIDI Channel**: Selects which MIDI Channel (1–16) the MVP listens to for lighting triggers.
* *Note: The Video and Lighting MIDI channels cannot be assigned to the same number.*
* **MVP ArtNet Settings**: Displays the current IP Address and Subnet Mask of the MVP's Ethernet port.
* *Note: These settings are read-only here. To change them, go to the Dashboard > Ethernet.*
* **Edit Mode** (Toggle):
* **ON**: Allows you to change assignments, record new clips, and delete files.
* **OFF**: Locks the interface to prevent accidental changes during a live performance.
***
### 2. SYNC CHANGES Button
Anytime a change is made to any of the lighting settings or MIDI assignments, the SYNC CHANGES TO PLAYBACK button will appear.
Pressing this button will make your changes live immediately. For example, if you assign a new DMX clip to a note, you must press the SYNC button before that note will trigger the new clip.
***
### 3. Clip Library & Recording
The Right Sidebar is your content manager for DMX data.
#### Record New Clip
Unlike the Video page where you upload files, the Lighting page allows you to record ArtNet data directly from your lighting console or software.
* Record Button: Click the RECORD NEW CLIP button to open the recording dialog.
* ***For full instructions on recording your DMX clips, please refer to the \[Recording ArtNET] section.***
#### Unassigned Clips
This list shows all DMX clips currently stored on the MVP that are not assigned to a MIDI note.
* **Trash Icon**: Click the trash can next to a file to permanently delete it from the device storage.
* **Free Space**: The storage meter at the top of this section shows your remaining disk space.
***
### 4. The Lighting Grid (MIDI Map)
The main area of the screen displays cards corresponding to the MIDI notes.
* **The Notes**: Each card represents a specific MIDI note (e.g., MIDI: C#-2).
* **Blackout**: Note 0 (C-2) is default assigned to "Blackout." Triggering this note sends a value of "0" to all DMX channels, effectively killing the lights.
* **Assignment**: To assign a lighting look, click the dropdown arrow in a card and select a recorded clip from your library.
* **Active State**: When a clip is active, its card highlights to indicate playback.
* **Removing**: Click the X icon to unassign a clip from that note.
* *Note: This does not delete the clip from the device; it only moves it back to the "Unassigned" list.*
***
### 5. Lighting Slots (Banks)
The MVP features 5 independent memory banks called Slots (A through E). Each slot stores its own unique set of MIDI assignments, allowing you to manage multiple shows or setlists on a single device and switch between them instantly.
#### Accessing the Slots Menu
By default, the MVP uses Slot A. To access the menu:
1. Locate the Slot Name (e.g., "Main Show") next to the "Lighting Configuration" title at the top of the page.
2. Click the name to open the Slot Dropdown menu.
#### Managing Slots
**Switching & Syncing**: When you select a new slot from the list, a dialog box will appear giving you two options for how to handle the transition:
1. **Sync to Playback**: This immediately updates your MVP. All incoming MIDI notes will now trigger the lighting clips assigned in the new slot right away.
2. **Not Now** (Background Editing): This loads the new slot into the UI for editing without interrupting the live show. The MVP will continue playing triggers from the previous slot (e.g., Slot A) while you arrange the files in the new slot (e.g., Slot B) in the background. You can sync the changes later when you are ready.
#### Advanced: Switching via MIDI CC
You can automate slot changes during a performance using your MIDI controller or DAW. Sending a specific CC Value on CC 119 will instantly load the corresponding bank.
| **Slot** | **MIDI CC Number** | **Value** |
| -------- | ------------------ | --------- |
| Slot A | 119 | 10 |
| Slot B | 119 | 20 |
| Slot C | 119 | 30 |
| Slot D | 119 | 40 |
| Slot E | 119 | 50 |
*Note: Slot changes via MIDI CC happen instantaneously, allowing for seamless transitions between songs or sets.*
***
> ⚠️ IMPORTANT: Video & Lighting Slots are Independent
>
> Video and Lighting playback operate completely separately. Switching the Video Slot does NOT automatically switch the Lighting Slot (and vice versa).
>
> When using CC 119 to automate slot changes, you must send the message on the correct MIDI Channel:
>
> * Send CC 119 on the Video MIDI Channel → Switches the Video Slot.
> * Send CC 119 on the Lighting MIDI Channel → Switches the Lighting Slot.
# Recording ArtNET - Lighting Software
The MVP supports recording and playback of up to 16 Universes. This guide covers how to record DMX lighting clips onto your MVP using PC or Mac based lighting software.
> ⚠️ FIRMWARE CHECK
>
> Please ensure your MVP is running the latest version 1.2.x firmware before proceeding.
>
> *To check for updates instructions, read the \[*[*Update your MVP Guide*](/archive-v12-userguide/1.-getting-started/update-your-mvp)*].*
***
### 1. The Concept (USB Passthrough)
In the past, recording from a computer required a complex network switch setup.
Now, the MVP supports **USB-ArtNET Passthrough**.
How it works:
1. Your Laptop sends ArtNet data to the MVP via the USB-C cable.
2. The MVP records this data internally.
3. Simultaneously, the MVP broadcasts/forwards that data out of its Ethernet port to your ArtNET Node.
Result: You can see your physical lights react in real-time while you record, with zero latency and no network switch required.
***
### 2. Hardware Connections
1. Laptop to MVP: Connect your computer to the MVP's HOST (USB-C) port.
2. MVP to Lights: Connect the MVP's ETHERNET port directly to your ArtNet Node.
***
### 3. Network Configuration (Crucial Step)
Because the MVP is acting as a bridge between your computer and your lights, we need to ensure the IP addresses are set correctly on both your MVP and ArtNET node.
#### A. The Ethernet Side (MVP -> Node)
This connection uses the standard ArtNet "2.x.x.x" range. Do not use other IP ranges unless you are experienced with ArtNET configurations.
* **ArtNet Node**: Set your node to a static IP (e.g., `2.0.0.10`) and Subnet Mask `255.0.0.0`.
* **MVP Ethernet**: Go to **Dashboard** > **Settings** > **Ethernet** and ensure the MVP is set to a compatible static IP (Default: `2.0.0.111`) and Subnet Mask `255.0.0.0`.
#### B. The USB Side (Laptop -> MVP)
This connection uses a separate private network created through the USB cable by the MVP.
* **Windows**: The MVP connection appears as `192.168.2.111`.
* **Mac**: The MVP connection appears as `192.168.3.100`.
* *Note: You cannot change these addresses; just ensure your lighting software targets this network interface.*
***
### 4. Software Setup
Configure your lighting software to output ArtNet to the MVP's USB network interface.
Example (Generic):
1. Open your Network/DMX settings.
2. Enable ArtNet Output.
3. **Interface Selection**: Select the network adapter that corresponds to the MVP's USB connection (e.g., `192.168.2.111` or `192.168.3.100`).
* *Do NOT select your Wi-Fi or hardwired Ethernet adapter.*
4. **Enable Broadcast**: Broadcast Mode must be enabled
5. **Universe Mapping**: The MVP supports recording up to 16 Universes. Ensure your software is broadcasting the desired universes (e.g., Univ 1–16).
**ONYX** Lighting Software:
**LightKey** Lighting Software:
**QLC+** Lighting Software:
**Show Buddy** Lighting Software:
***
### 5. Recording Process
#### Step 1: Recording Dialog Box
1. Navigate to the Lighting tab on the MVP UI.
2. Toggle **EDIT MODE** to **ON**.
3. Click the **RECORD NEW CLIP** button on the right sidebar.
#### Step 2: Verify Signal
Before recording, look at the **ArtNET Preview** grid in the dialog box.
* **Play a Cue**: Fire a lighting cue in your software.
* **Check Preview**: You should see the grid pixels dancing *AND* your physical lights connected to the node should light up.
* *If the grid moves but physical lights don't:* Check your Ethernet connection, and Node IP.
* *If nothing moves:* Check your Software Output Interface (Step 4).
#### Step 3: Capture
1. **Name Your Clip**: Enter a descriptive name (e.g., "Chorus Strobe").
2. **Arm the Recorder**: Press the red **START RECORDING** button.
3. **Wait for Data**: The MVP is now "Armed" and listening, but it will not begin recording until it detects the first change in DMX values. This feature ensures your clips are perfectly tight, with no empty "dead air" at the beginning of the clip.
4. **Perform**: Play your lighting cue in your lighting software. As soon as the MVP detects a value change on *any* DMX channel, it will instantly start recording.
5. **Stop**: Press **STOP RECORDING**.
The new clip will immediately appear in your Unassigned Clips list, ready to be mapped to a MIDI note.
# Recording ArtNET - Lighting Desk
The MVP supports recording and playback of up to 16 Universes. This guide covers how to record lighting clips onto your MVP using a physical lighting console (such as GrandMA, Avolites, ChamSys, etc.).
***
### 1. The Concept (The Network Switch)
Unlike the Software workflow which uses USB, recording from a physical desk requires an Ethernet connection.
Because the MVP has a single Ethernet port, it cannot "pass through" Ethernet data to your lights while simultaneously receiving it from the console. Therefore, we use a standard Network Switch to create a shared network.
How it works:
1. Your Console broadcasts ArtNet data into the Network Switch.
2. The Switch splits this signal to all connected devices.
3. The MVP receives the data to record it.
4. Your ArtNet Node receives the same data to drive the lights.
Result: You can see your physical lights react in real-time while you record, ensuring your looks are perfect before capturing.
***
### 2. Hardware Connections
You will need a basic [Gigabit Network Switch](https://www.google.com/search?q=Gigabit+Network+Switch) and three Ethernet cables.
1. **Console to Switch**: Connect your Lighting Desk's Ethernet port to the Switch.
2. **MVP to Switch**: Connect the MVP's ETHERNET port to the Switch.
3. **Node to Switch**: Connect your ArtNet Node to the Switch.
***
### 3. Network Configuration (Crucial Step)
For ArtNet to work, all three devices (Console, MVP, and Node) MUST be on the same IP range. The industry standard for ArtNet is the `2.x.x.x` range.
#### A. IP Address Rules
Set all devices to Static IP addresses. They must share the first number (2) and the Subnet Mask, but the last number must be unique.
* **Subnet Mask**: Set ALL devices to `255.0.0.0`
Recommended IP Map:
* **Lighting Console**: `2.0.0.20`
* **ArtNet Node**: `2.0.0.10`
* **MVP Ethernet**: `2.0.0.111`
* *To configure your MVP:* Go to **Dashboard** > **Settings** > **Ethernet** and enter the IP/Subnet manually.
***
### 4. Console Setup
Configure your lighting desk to output ArtNet to the network.
1. **Enable ArtNet**: Go to your console's Network/DMX Protocols settings and enable ArtNet Output.
2. **Broadcast Mode**: Ensure the Output Mode is set to Broadcast.
* *Why?* Broadcast sends the data to everyone on the network. If you use "Unicast," you would have to tell the console to send data specifically to the MVP's IP address, which is more complex to set up.
3. **Universe Mapping**: Ensure your console is outputting the correct universes (e.g., Universe 1–16).
***
### 5. Recording Process
#### Step 1: Recording Dialog Box
1. Navigate to the Lighting tab on the MVP UI.
2. Toggle **EDIT MODE** to **ON**.
3. Click the **RECORD NEW CLIP** button on the right sidebar.
#### Step 2: Verify Signal
Before recording, look at the ArtNET Preview grid in the dialog box.
1. **Play a Cue**: Fire a lighting cue on your console.
2. **Check Preview**: You should see the grid pixels dancing in the MVP UI AND your physical lights connected to the node should light up.
* *If the lights work but the MVP grid doesn't move:* Check the MVP's IP settings.
* *If nothing works:* Check your Console's output settings and the Network Switch power.
#### Step 3: Capture
1. **Name Your Clip**: Enter a descriptive name (e.g., "Verse Blue Wash").
2. **Arm the Recorder**: Press the red START RECORDING button.
3. **Wait for Data**: The MVP is now "Armed" and listening. It will not begin recording until it detects the first change in DMX values. This ensures your clips are tight, with no "dead air" at the start.
4. **Perform**: Play your lighting cue on the console. The MVP will instantly start recording as soon as the values change.
5. **Stop**: Press STOP RECORDING.
The new clip will immediately appear in your Unassigned Clips list, ready to be mapped to a MIDI note.
#### Step 4: Test Your New Clip (Crucial)
Once your clip is recorded, you will want to play it back to see how it looks.
⚠️ **IMPORTANT**: Before you trigger the clip on the MVP, you MUST stop your lighting console from outputting ArtNet.
**The "Glitch" Effect**: Even if your console faders are at zero, the desk is likely still broadcasting "0" values to the network 40 times a second. If the MVP tries to send lighting data to the node while the console is also sending "zeros," the two signals will fight. This results in flickering, strobing, or glitching lights.
How to Test Cleanly:
1. **Silence the Console**: Either disable ArtNet Output in your console's settings OR simply unplug the Ethernet cable connecting the Console to the Switch.
2. **Assign the Clip**: On the MVP Lighting page, assign your new clip to a MIDI Note (e.g., `DMX 01`).
3. **Trigger**: Send that MIDI note to the MVP.
4. **Verify**: Your lights should play back the recorded look smoothly, exactly as it was captured.
*Once you are finished testing, remember to re-enable your console output to record the next look.*
# LTC Timecode Setup
Linear Timecode (LTC) allows you to trigger video and lighting clips using an LTC (SMPTE) audio source.
The MVP listens for the audio signal via its rear input port and fires specific clips when the incoming timecode matches your Timecode Trigger.
***
### 1. Hardware Connection
1. Source: Connect your timecode source into the Pink 1/8" (3.5mm) **IN** port on the rear of the MVP.
***
### 2. Signal Verification (The Input Monitor)
Before programming triggers, you must ensure the MVP is receiving a clear signal.
1. Navigate to the MVP's **Dashboard** page.
2. Start playback on your LTC source.
3. Check the **LTC Counter**: You should see the numbers running rapidly (HH:MM:SS:FF).
Troubleshooting Signal Levels:
* If the counter is frozen or erratic: The audio volume is likely too low or too loud (clipping).
* Fix: Adjust the output volume on your source device up or down until the MVP's LTC Counter runs smoothly and consistently.
***
### 3. Creating Triggers
Once your signal is verified, go to the **LTC** tab in the left sidebar.
Add New Timecode Trigger
1. Click the toggle switch to enable **EDIT MODE** on the top right.
2. Click the blue **ADD NEW TIMECODE TRIGGER** button.
3. **Select Type**: Choose between **VIDEO TRIGGER** or **LIGHTING TRIGGER**.
4. **Set the Time**: Enter the exact HH (Hours), MM (Minutes), SS (Seconds), and FF (Frames) for the trigger.
5. **Select your Media**: Choose the specific video file or lighting clip from the dropdown menu.
6. **Save**: Click the **SAVE** button.
Repeat this process to add all of your LTC triggers.
#### Managing Triggers
* **Edit**: Click the Pencil Icon next to any trigger to change its settings.
* **Delete**: Click the Trash Can icon to remove a trigger.
* **Sort**: Triggers are automatically sorted chronologically.
***
Note that the MVP uses LTC as a Start Trigger, not for continuous synchronization.
* Behavior: When the incoming timecode matches the Timecode Trigger values (e.g., `00:01:30:00`), the MVP simply presses "Play" on the assigned clip.
* No Scrubbing: The clip plays at its normal speed. It does not slow down, speed up, or scrub backward if the external timecode changes speed. It purely listens for the specific "Go" frame.
# DAW / Computer Triggering
This guide outlines the general workflow for using a Digital Audio Workstation (DAW) or sequencer to trigger MVP playback using standard MIDI notes.
***
### 1. Physical Connections
#### A. Control Connection
* Computer → MVP: Use the included USB-C cable to connect your computer to the MVP's HOST Port.
* *Note:* The computer provides both power and MIDI data over this single cable.
#### B. Output Connections
* Video: Connect the HDMI Port to your Projector, Video Wall, or TV.
* Lighting: Connect the Ethernet Port to your ArtNet Node or Network Switch.
***
### 2. Wiring Scenarios
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
#### Scenario B: Lighting Playback Only
* Signal Chain: Computer → MVP → Ethernet → ArtNet Node → DMX Fixtures
#### Scenario C: Video + Lighting Playback
* Signal Chain: Computer → MVP → HDMI & Ethernet
***
### 3. Software Specific Guides
Select your software below for detailed routing instructions:
* [\[Ableton Live Setup\]](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/ableton-live-setup)
* [\[Pro Tools Setup\]](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/pro-tools-configuration)
* [\[Logic Pro Setup\]](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/logic-pro-configuration)
***
### 4. Trigger Behavior
* Start Trigger: The MVP listens for a Note On message to begin playback.
* Note Duration: The length of the MIDI note in your DAW does not affect playback duration. A short pulse triggers the file just as effectively as a long note.
* Stopping Playback: Stopping the DAW transport does not send a stop command to the MVP. To stop playback, you must trigger the assigned Blackout Note (Default: Note 0 / C-2).
# Ableton Live Setup
This guide covers the steps to send MIDI notes from Ableton Live to the MVP.
> Note: This guide assumes basic familiarity with Ableton Live's interface. For general instruction on using the software, please refer to the [\[Official Ableton Live Manual\]](https://www.ableton.com/en/manual/welcome-to-live/).
***
### 1. Configure MIDI Preferences
First, we must configure Ableton to send data to the MVP.
1. Connect the MVP's **HOST** port to your computer via USB.
2. Open Ableton Live.
3. Open **Preferences** (macOS: `Live > Settings...` | Windows: `Options > Preferences`).
4. Navigate to the **Link Tempo MIDI** tab.
5. Scroll down to the **MIDI Ports** section.
6. Locate Output: **MVP**.
7. Ensure the **Track** checkbox is enabled (On).
* *This allows MIDI notes from your tracks to be sent to the device.*
***
### 2. Create a MIDI Track
1. Create a new MIDI Track (`Shift + Cmd + T` / `Shift + Ctrl + T`).
2. Rename the track (e.g., "MVP VIDEO").
***
### 3. Route the Output
Now we configure where this track sends its notes.
1. Locate the I/O section on the track (if hidden, press `Cmd/Ctrl + Option + I`).
2. **MIDI From**: Select **No Input**.
3. **MIDI To**: Select **MVP**.
4. **Channel**: Set to same Channel number you have in the MVP UI.
***
### 4. Program Your Cues
1. Insert a MIDI Clip: Double-click a slot (Session View) or highlight an area and press `Shift + Cmd + M` (Arrangement View).
2. Draw a Note: Open the Clip, View/Piano Roll.
3. Match the Assignment: Draw a note that matches your file assignment in the MVP.
* *Example:* If your video is assigned to E-2, draw a E-2 note in Ableton.
4. Play: Press Play in Ableton. The MVP should trigger instantly.
Note: In most circumstances, you will want to disable the **Loop** setting next to the piano roll.
***
### 5. Stopping Playback (Blackout)
Remember that stopping Ableton does not automatically stop the MVP.
To program a "Stop" cue in your song:
* Draw a note at C-2 (Note 0).
* This triggers the MVP's default Blackout function.
# Pro Tools Configuration
How to route MIDI out of Pro Tools to the MVP from a MIDI track.
### 1. Create a new MIDI track
Navigate to the TRACK menu in the top bar. and select NEW.
The "New Tracks" window will open. Set the following settings accordingly.
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. \
{% hint style="info" %}
Pro Tip: turn the track's MIDI INPUT to NONE to ensure no clips are triggered unexpectedly from other MIDI sources.
{% endhint %}
### 3. Arrange MIDI in the track and play it back to the MVP
# Logic Pro Configuration
How to create a MIDI output track and route it to the MVP to play along with the arrangement.
### 1. Create a new EXTERNAL MIDI track
Right click in the track header area, and select "New External MIDI Track". \
Name the track "MVP OUT" or something similar.
### 2. Select MVP from MIDI Output menu
### 3. Set MIDI track settings as needed.
* Set MIDI input as OFF if you're just triggering from arrangement based MIDI.
* Set MIDI OUT channel as 1 for video triggers or 3 for lighting triggers
### 4. Add MIDI to the track's arrangement to trigger the MVP
# Network MIDI (RTP-MIDI) Setup
Network MIDI (RTP-MIDI) allows you to send MIDI to the MVP over a standard WiFi or Ethernet network.
This is the preferred method for long-distance runs (e.g., FOH to Stage) where USB cables are not feasible.
> ⚠️ WI-FI
>
> While Network MIDI does work over Wi-Fi, it can be susceptible to network latency and jitter. For live performances, we recommend using a hardwired Ethernet connection.
***
### 1. Network Connection (choose one)
#### WiFi
1. Open the MVP UI, and click on the WIFI icon in the top right corner
2. Connect to your WiFi network (Your router will handle the IP settings automatically)
3. Ensure your Computer is connected to the same WiFi network
#### Ethernet
1. Connect: Plug an Ethernet cable into the MVP's Ethernet Port.
2. Network: Connect the other end to your computer directly or to a Network Switch.
3. IP Settings: Ensure your computer and the MVP are on the same IP range.
* *Default MVP IP:* `2.0.0.111`
* *Computer:* Set to Static IP (e.g., `2.0.0.50`), Subnet `255.0.0.0`.
Mac:
Windows:
***
### 2. macOS Setup (Native)
Macs have RTP-MIDI built directly into the operating system.
Step 1: Open MIDI Studio
1. Press Command + Space to open Spotlight.
2. Type "Audio MIDI Setup" and press Enter.
3. In the top menu bar, click Window > Show MIDI Studio.
Step 2: Configure Network
1. In the MIDI Studio window, double-click the Globe Icon (labeled "Network").
* *Or in the top menu bar, click MIDI Studio > Open MIDI Network Setup.*
2. Look at the "My Sessions" box (top left). If it is empty, click the + button to create a new session.
1. Rename: Click on the new session name and rename it to "Network MVP".
2. Enable: Click the Checkbox next to the session name to enable it.
Step 3: Connect to MVP (Crucial Step)
In the "Directory" box (bottom left), you will likely see two devices listed for the MVP.
* `MVP` (Short name)
* `MVP/RtMidiIn Client-MVP` (Long name)
⚠️ You MUST select the one with the LONG NAME.
1. Select `MVP/RtMidiIn Client-MVP`.
2. Click the Connect button.
3. The device should move to the "Participants" list on the right.
***
### 3. Windows Setup (rtpMIDI)
Windows does not support this natively, so you must use the free rtpMIDI app.
1. Download: Install [rtpMIDI](https://www.tobias-erichsen.de/software/rtpmidi.html).
2. Launch: Open the program. The interface is almost identical to the macOS version above.
3. Create Session: Click the + under "My Sessions" and change Local Name to "Network MVP".
1. Enable: Check the box above Local Name.
2. Connect: In the Directory, select the Long Name device (`MVP/RtMidiIn Client-MVP`) and click Connect. You will see it move to the "Participants" list.
***
### 4. Testing Your Connection
#### Connecting your DAW (Live, ProTools, etc)
In a DAW, you will see Network MVP in your MIDI settings.
Set your MIDI track's output too Network MVP.
To verify the connection without opening a DAW, use a virtual keyboard:
#### macOS: MidiKeys (Simplest)
1. Download MidiKeys (Free).
2. Set Destination to "Network MVP".
3. Press keys on your computer keyboard to trigger the MVP.
#### Cross-Platform: VMPK
If you prefer VMPK (Virtual MIDI Piano Keyboard), follow these steps:
"Unverified Developer" Fix (macOS):
If you get an error saying the app cannot be opened:
1. Right-Click the VMPK app icon.
2. Select Open.
3. Click Open in the popup dialog.
Configuration:
1. Open VMPK.
2. Go to Edit > MIDI Connections.
3. MIDI OUT Driver: Select CoreMIDI (Mac) or Windows MM (PC).
* *Do NOT select "Network" here.*
4. Output Connection: Select "Network MVP" (the session you created earlier).
5. Click OK. You can now play the on-screen keys to test.
# ArtNet Configuration
Setting up an ArtNet network for recording and playing back DMX clips.
For users new to working with stage lighting, ArtNet is the lighting control protocol that allows for DMX lighting data to be sent over an ethernet network. The MVP can both receive DMX over ArtNet for recording DMX cues and output to ArtNet for lighting playback, both via the ethernet port on the back of the device. When the MVP is connected to other ArtNet devices (lighting desks, computers running lighting software, ArtNet Nodes) via the ethernet port it is part of an ArtNet network.
{% hint style="info" %}
An ArtNet node is a device that translates in either direction between ArtNet (via ethernet) on one end, and DMX on the other. With MVP, an ArtNet node can be used to receive lighting data from the MVP via ArtNet and output to DMX lighting fixtures.
{% endhint %}
To ensure proper communication between ArtNet devices, they must have compatible IP and subnet mask settings. The MVP by default assigns it's ethernet port the following network settings:
IP: 2.0.0.111\
Subnet mask: 255.0.0.0
These settings are compatible with standard configurations of many ArtNet devices. You can verify the MVP’s network settings on the top of the lighting page of the UI.
{% hint style="info" %}
MVP must detect an ethernet connection to load and display it's network settings in the UI and on the device display.
{% endhint %}
If the MVP does not seem to be communicating with other devices on your ArtNet network, double check their settings and confirm that they are assigned a unique IP address beginning with the same 2 as the first number, and a matching subnet mask of 255.0.0.0. If the subnet masks match but the IP address does not start with the same number as the MVP, you can change either the MVP or other device’s IP address to match the first number.
If outputting DMX over ArtNet from a computer lighting software to the MVP, check the software’s output settings and ensure that each DMX universe is outputting to the port connected to the MVP, and that said port has been configured with a compatible IP & subnet mask. If recording lighting clips from computer software using USB ArtNet, you can find MVP in your software's ArtNet output settings with the following IP addresses:
Mac: 192.168.3.1\
Windows: 192.168.2.1
For more advanced ArtNet users, the MVP allows you to manually reassign its IP and subnet mask settings. See [Networking](/archive-v12-userguide/detail-archive/networking) for details.
# Networking
Set up and configure MVP's network settings
## WIFI
MVP can connect to wifi networks to receive updates and communicate with 4CAST's cloud servers. When setting up your MVP for the first time, you'll be prompted to connect to a network. To connect to a different network, click the wifi icon in the upper right of the UI and wait for MVP to scan for available networks. Select the network you'd like to connect to and input the password. MVP will remember known networks much like your computer, unless a network is 'forgotten' by clicking the bookmark icon next to the network name.
{% hint style="info" %}
For security reasons, we strongly recommend only connecting your MVP to private wifi networks. If necessary to connect to a public network (i.e. a venue's public guest wifi), once finished click the bookmark icon next to the network name to forget the login, and disconnect wifi.
{% endhint %}
## Ethernet
MVP's ethernet network settings are set by default to an IP of 2.0.0.111 and subnet mask of 255.0.0.0, but can be custom configured as needed to communicate with your Artnet or RTP Midi networks. Click on the cog icon in the upper right of the UI, then 'Ethernet | Artnet' to access and update network settings.
MVP can operate in static or DHCP mode. For most Artnet setups, static will be the ideal setting. However, if connecting MVP to your router via Ethernet to receive updates from 4CAST, or for more complex setups, DHCP mode allows MVP to dynamically receive an IP from the network.
{% hint style="info" %}
MVP must detect an Ethernet connection to load and display it's network settings in the UI and on the device display. You will not be able to update settings unless an Ethernet connection is detected.
{% endhint %}
# Meet Your MVP
Get started below.
For a video overview of using your MVP, check out our tutorial.
{% content-ref url="/pages/BbsScKo3ZaTDwpSQKuYR" %}
[Tutorial](/archive-v12-userguide/resources-archive/tutorial)
{% endcontent-ref %}
For more detailed information to get started, explore the Quickstart section.
{% content-ref url="/pages/5a3RZGP4P6cXCkDHKXwQ" %}
[Quickstart](/archive-v12-userguide/resources-archive/quickstart)
{% endcontent-ref %}
Can't find an answer? [Contact us](/archive-v12-userguide/resources-archive/contact-us).
# Contact Us
If you can't find an answer to your question here, reach out to and we'll see if we can help.
# Tutorial
Learn about setting up and using your MVP.
{% embed url="" %}
# Quickstart
Start here to get set up and begin using your MVP.
{% content-ref url="/pages/peq0ENQ1tPOJmuuXUzkD" %}
[Connecting Via Browser](/archive-v12-userguide/resources-archive/quickstart/connecting-via-browser)
{% endcontent-ref %}
{% content-ref url="/pages/yYvcej6EWjMq3Zvy6trf" %}
[Register Your MVP](/archive-v12-userguide/resources-archive/quickstart/register-your-mvp)
{% endcontent-ref %}
{% content-ref url="/pages/xWdnYIifU9bUJXgpGJKN" %}
[Video Configuration](/archive-v12-userguide/resources-archive/quickstart/video-configuration)
{% endcontent-ref %}
{% content-ref url="/pages/yLduXD9JhWIri0WnCQ69" %}
[DMX Lighting Configuration (Beta)](/archive-v12-userguide/resources-archive/quickstart/dmx-lighting-configuration-beta)
{% endcontent-ref %}
{% content-ref url="/pages/zEnABU4D7iv8Xk3fcmb2" %}
[Playback Setup](/archive-v12-userguide/resources-archive/quickstart/playback-setup)
{% endcontent-ref %}
# Connecting Via Browser
Access the MVP's UI for configuration via a browser window.
When first setting up an MVP, connect it to the USB port on any computer using the USB-C ‘host’ port on the MVP. The MVP should power on as indicated by the status light on the side. Wait 5-10 seconds for the MVP to fully load.
Open a browser window on your computer and navigate to mvp.local. The computer should recognize the connected MVP and load the configuration page. The first time you connect the MVP it will prompt you to register it to an email and connect to a wifi network to be able to receive updates. Follow the instructions on screen, or skip to configure your account settings at a later time.
Note, the MVP configuration page is loaded directly off the device itself and does not require an internet connection to reach.
{% hint style="info" %}
MVP must first be powered by USB-C to your computer to ensure that the computer recognizes the device and is able to access the UI. If the MVP is instead powered first via the barrel plug PSU before connecting to your computer, the UI will not be accessible.
{% endhint %}
***
### Troubleshooting
If the browser doesn’t recognize your MVP:
* Make sure MVP is powered on and connected to your computer through the ‘host’ port
* Ensure MVP is receiving proper USB bus power. Computers and hubs with multiple devices connected can lead to under powering or inconsistent power, causing issues with MVP function. See [troubleshooting](#troubleshooting) for more info.
* Check your computer settings to make sure it is recognized as a USB device
* On Macs: open click on the Apple menu and open ‘System Settings’. In ‘System Settings’ click on ‘Network’. MVP should appear as ‘MVP’ as connected in ‘Other Services’. If you don’t see the MVP connected, try to power the MVP off and on.
* On Windows: Open ‘Settings’, click on ‘Network and Internet’ and under ‘Advanced Network Settings’ click ‘Change Adapter Options’. The MVP should show up as an ethernet device.
* Try connecting to MVP in the browser using MVP’s USB-C host IP:
* On Macs: type into the address bar
* On Windows: type into the address bar
* Try using a different browser. We recommend Chrome, a Chromium-based browser, or Firefox
{% hint style="info" %}
It's intended to access the MVP's UI via the USB-C host port, however it is possible to access the UI via Ethernet as well. If the UI has been accessed previously on a computer via Ethernet, the DNS cache may attempt to resolve mvp.local to the Ethernet IP instead of the USB IP. In this case, the UI should still be reachable via the direct IP, but you can also run a Terminal command to clear the DNS cache and reset the mvp.local resolution.
{% endhint %}
# Register Your MVP
Connect your MVP to an email.
When first accessing the UI on your MVP, a pop up will prompt you to connect your MVP to wifi, and register an email with us. You can also connect your MVP to the internet via Ethernet connection to your router. To connect this way, make sure MVP's network settings are set to DHCP to receive an IP from your router.
Linking your MVP to an email allows us to provide support services, and connecting to wifi allows MVP to communicate with the cloud to check for updates.
You can change your wifi settings at any time by clicking the icon in the upper right corner of the UI.
{% hint style="info" %}
For security reasons, we recommend only connecting to a private wifi network (i.e., not a venue's public wifi) and disconnecting MVP from wifi before performing.
{% endhint %}
# Video Configuration
Upload and map your video clips.
The MVP works by mapping video files loaded onto it to MIDI note triggers which the MVP can receive from any MIDI source. To configure video playback:
From the MVP UI, click on the ‘Video’ tab.
{% hint style="info" %}
The video configuration page can be in locked view mode or edit mode. To make any changes to the configuration, first make sure edit mode is enabled by clicking on the ‘edit’ toggle in the top right. The toggle will turn red when enabled.
{% endhint %}
**Upload** video files by dragging and dropping them onto the right side of the video configuration page, or by clicking ‘upload’ and locating them on your computer. Once you see the video preview, click the upload icon in the corner to begin uploading. Uploaded videos will appear in the ‘Unassigned Videos’ sidebar. The MVP supports h264 MP4 or MOV videos up to 4k quality and 30 frames per second.
{% hint style="info" %}
Navigating away from the video page in the UI will cancel a current upload. Remain on the page until your file upload is complete.
{% endhint %}
**Map** video files to MIDI notes by clicking on the title bar of any MIDI note block and searching one of your uploaded videos from the dropdown. The assigned video name will appear below the MIDI note when mapped.
**Delete** mappings by clicking the ‘X’ next to any MIDI note. Click the ‘X’ next to a video file in the ‘Unassigned Videos’ sidebar to delete the file from your MVP.
**Push updates** to MVP's configuration file by power cycling the unit or sending it MIDI note value 127 over MIDI channel 1. Updates must be pushed before taking effect for playback.
# DMX Lighting Configuration (Beta)
Record and map DMX lighting clips.
The MVP works by mapping DMX lighting clips recorded onto it to MIDI note triggers which the MVP can receive from any MIDI source. The MVP can record and playback clips up to 4 DMX universes. Recording clips to the MVP requires use of a lighting desk or software for clip design. To configure DMX lighting playback:
**Connect** the MVP to a computer via the USB-C ‘host’ port and bring up the browser configuration page. From the MVP configuration page, click on the ‘lighting’ tab.
**Connect** the MVP over ArtNet to a lighting desk or computer running lighting software. If recording clips from the same computer you are using to access the UI, ArtNet can be received over the same USB-C cable, without the need for an additional connection. Otherwise, connect the MVP to your lighting desk or computer running lighting software using the ethernet port. Make sure the desk or software is set to output over ArtNet to the MVP. For assistance on setting up an ArtNet connection, see [ArtNet configuration](/archive-v12-userguide/detail-archive/artnet-configuration).
{% hint style="info" %}
The lighting configuration page can be in locked view mode or edit mode. To make any changes to the configuration, first make sure edit mode is enabled by clicking the edit toggle in the top right. The toggle will turn red when enabled.
{% endhint %}
**Test** to make sure the MVP is receiving signal by sending DMX data from your connected lighting desk or software. Click the ‘record’ button, and if working correctly, the DMX preview display should display DMX values it’s receiving from your source in real time.
**Record** DMX clips by pressing the ‘record’ button and then sending DMX signal out of your chosen source into the MVP. The MVP will listen for DMX signal and start recording from the first change in DMX value until you press ‘stop recording’. Give the clip a descriptive name to easily identify the effect.
{% hint style="info" %}
To avoid conflicting signals, do not trigger existing DMX clips with MIDI while recording a new clip.
{% endhint %}
**Map** DMX clips to MIDI notes by clicking on the title box next to any MIDI note in the grid and searching the dropdown menu for the appropriate clip. The assigned clip name will appear below the MIDI note when mapped.
{% hint style="info" %}
MIDI note C-2 is hard coded to a 'black out' clip that zeros all DMX channels on all universes, for stopping lighting playback. For situations where you may need to zero only certain universes, record custom black out clips.
{% endhint %}
**Delete** mappings by clicking the ‘X’ next to any MIDI note. Click the ‘X’ next to a clip in the ‘Unassigned Clips’ sidebar to delete the file from your MVP.
**Push updates** to MVP's configuration file by power cycling the unit or sending it MIDI note value 127 over MIDI channel 3. Updates must be pushed before taking effect for playback.
If you are new to lighting design, you may find it helpful to work with a lighting designer familiar with lighting software or lighting desk for the initial design and set up of your clips. Once clips have been recorded onto the MVP, no further technical expertise is required.
{% hint style="info" %}
The MVP records the entire stream of DMX received and plays it back on trigger exactly as it was received from the source without knowledge of what fixtures the clip was designed for or what fixtures the MVP is outputting to. Because of the nature of DMX signal, It’s important that recorded clips are designed specifically for the lighting package that clip will be used with as any change in the lighting package will produce a different result from the same signal.
{% endhint %}
# Playback Setup
Set up your MVP for your performance.
Once videos and/or DMX lighting cues are configured and mapped to MIDI notes it’s simple to control playback from any MIDI source.
### Connect MVP to Inputs/Outputs
Connect the MVP to video and/or lighting outputs:
**HDMI** - for video output to a video screen, projector or other external display.
**Ethernet (ArtNet) -** for DMX lighting output to an ArtNet node, which is connected to your light fixtures. For detailed ArtNet set up instructions see [ArtNet configuration](/archive-v12-userguide/detail-archive/artnet-configuration).
Connect the MVP to a MIDI source through one of the following ports:
**Host** - for connecting a computer running playback software (DAW) like Ableton, Logic, Protools, etc.
**USB A** or **MIDI DIN** - for connecting hardware MIDI controllers, MIDI keyboards, sequencers, etc.
**Ethernet** - for RTP MIDI
Connect and power on all of your other inputs and outputs before powering the MVP to ensure smooth connection.
{% hint style="info" %}
The MVP is USB powered when connected to a computer, but will require the barrel plug power supply when not connected to a computer.
{% endhint %}
### Control Playback From a DAW
In your playback session with the MVP connected and powered on, make sure your DAW recognizes the MVP as a MIDI device in MIDI preferences and that the DAW can send MIDI messages to it. In Ableton this means enabling the ‘track’ check box on the OUT setting for the MVP.
Add a MIDI track to your session and choose the MVP as the output. Select the MIDI channel corresponding to which mappings you need to control. By default the MVP maps video cues to MIDI channel 1 and lighting cues to MIDI channel 3.
Draw MIDI in the track at the points you want to trigger a cue with the notes corresponding to the mappings you configured. I.e. if you want to trigger ‘video 1’ which you mapped to the MIDI note C1, add a C1 note at the point in your session where the video should begin to play.
Play through your session and test that the MVP is outputting video and/or lights correctly in time with your audio playback.
{% hint style="info" %}
DAWs and MIDI controllers have different octave naming conventions. The MVP names MIDI notes in line with Ableton’s naming scheme, however other setups may vary. For example, what the MVP considers C0 might be named C1 by your DAW or controller. The numerical MIDI value (0-127) will always be consistent.
{% endhint %}
{% hint style="info" %}
The MIDI note triggers the beginning of the cue only, which will continue to play independently of your DAW session. By default, MIDI note 0/C-2 is mapped to STOP playback of the active cue on that channel. Similarly, starting playback in the middle of a song after the programmed MIDI trigger will skip the programmed cue. Depending on your set up and needs, it may be beneficial to break longer videos into smaller clips that can be individually triggered in sequence to add fall back trigger points.
{% endhint %}
{% hint style="info" %}
The MVP has a negligible response time from receiving a MIDI signal, however longer cabling setups and different video outputs will produce additional delay outside of the MVP. Accommodate for delay by nudging MIDI notes forward as needed or adjusting the MIDI track’s delay settings. We recommend testing delay anytime your setup changes (i.e. using a new screen at a different venue).
{% endhint %}
### Control Playback From a Hardware Controller
Make sure your hardware controller is programmed to output the range of MIDI notes and channel corresponding to the video or lighting cue mappings you configured in the MVP. Most modern controllers allow for custom MIDI mappings. Consult the manual for your controller on how to customize yours. By default the MVP maps video triggers to MIDI channel 1 and DMX lighting cues to MIDI channel 3.
With your controller connected to the MVP via one of the USB-A ports or the MIDI DIN port, and with the MVP powered via the barrel plug power supply, use your controllers keys or sample pads to send MIDI signal to the MVP. If connected correctly the MVP should automatically begin playing back the cue mapped to the note you triggered.
MVP supports native profiles for several common hardware controllers and will continue to add more. See [MIDI Controller Profiles](/archive-v12-userguide/technical-archive/midi-controller-profiles) for a list.
### Using multiple MIDI sources
The MVP will listen and respond to MIDI from any connected source simultaneously. For example, it is possible to have a DAW playback session triggering videos synced with audio playback while a sample pad is also connected to trigger video clips in real time. Any video triggered from either source will automatically replace any previously playing video.
# LTC Configuration (Beta)
Create Linear Time Code (LTC) triggers for video and lighting clips.
MVP includes a beta implementation of LTC playback which uses timecode triggers to correspond with video and lighting clips. In this implementation, video and lighting playback is begun on timecode triggers in the same way MIDI triggers are received. Note however that clips will not follow changes in LTC signal once playback has begun, such as speeding up, slowing down, or stopping LTC.
To set up LTC triggers, navigate to the LTC page in the MVP UI. Click to add a new trigger, or edit an existing trigger. Triggers are defined in a HH:MM:SS:FF format (hours/minutes/seconds/frames), and can be set for either video or lighting clips. Choose the relevant clip and save the trigger.
Existing triggers will appear in a chronological list as either a video or lighting trigger.
MVP receives LTC signal via the 1/8" audio in port, sent from any LTC generating source.
{% hint style="info" %}
MVP is recognizable as a USB audio device for future implementation, however at present LTC will not be received over USB and instead must be via the 1/8" audio in.
{% endhint %}
# Troubleshooting
Solutions to common problems.
**No video output** No video output
With the HDMI connected, power cycle the MVP to ensure an HDMI output is detected on boot. Ensure the MVP is playing back a video by sending MIDI to it. The display on the top of the device should reflect the MIDI note and video title that has been triggered. If no video is displayed, double check the MVP is receiving MIDI input and that the MIDI note received has a video clip mapped to it.
If the display is showing video playback but no video is appearing via the HDMI output, check to see that the correct HDMI source is selected on your video screens’ settings, and if necessary power the screen off and on and then the MVP off and on by unplugging the power source. If you still have issues, there may be an issue with the video file itself. Make sure your file conforms to the supported video specs and if necessary delete and re-upload your video.
If the issue still persists, test the MVP with a different HDMI cable and a different video screen to ensure there isn’t a technical issue with your hardware.
No DMX lighting output
If your lighting fixtures are not receiving any signal from the MVP, first confirm that the MVP is connected to your ArtNet node over Ethernet, and that your ArtNet node is connected to your lighting fixtures via DMX cable(s). Also confirm that your MVP is playing back lighting cues by checking the display on top of the device and ensuring a DMX cue is displayed as playing.
If you are still not receiving DMX signal to your lights, double check that the ArtNet node network settings are compatible with the network settings of the MVP. For more information on this see [ArtNet Configuration](/archive-v12-userguide/detail-archive/artnet-configuration).
Browser not connecting to MVP
Ensure the MVP is connected to your computer through the USB-C ‘host’ port and that the MVP is powered on as indicated by the status light on the front side of the MVP.
With the MVP powered on and connected properly it should automatically appear in your computer’s device or network settings:
On **Mac computers**, open click on the Apple menu and open ‘System Settings’. In ‘System Settings’ click on ‘Network’. The MVP should appear as ‘MVP’ as connected in ‘Other Services’. If you don’t see the MVP connected, try to power the MVP off and on. If the MVP still is not recognized, click on ‘...v’ in the bottom right and then select ‘Add Service’. Select ‘MVP’ as the Interface, and type MVP as the Service Name. Your computer should now recognize the MVP network connection through your USB port.
On **Windows computers**, open ‘Settings’, click on ‘Network and Internet’ and under ‘Advanced Network Settings’ click ‘Change Adapter Options’. The MVP should show up as an ethernet device.
When the MVP is connected and recognized by your computer, any browser should recognize it at the address mvp.local, however if the MVP configuration page is not loading you can alternately reach it by entering the IP address ([*http://192.168.3.1*](http://192.168.3.1) *on Macs,* [*http://192.168.2.1*](http://192.168.2.1) *on PCs)* in your browser. We recommend using Chrome, a Chromium build browser, or Firefox for MVP configuration.
If mvp.local does not work, but using the direct IP address does successfully load the UI, your computer has cached DNS settings resolving to another connection. We always recommend connecting to the UI via the USB-C host port, but this DNS issue can occur if you’ve connected to the UI at mvp.local via Ethernet, in which case your computer may automatically try to resolve the .local address to the Ethernet IP. To resolve the issue, you can try several things in this order:
* Clear your browser cache
* In your network settings, renew the DHCP lease for the MVP, then power cycle the MVP
* Also in network settings, deactivate/reactivate the MVP, then power cycle the MVP
* As a last solution for technical users, you can use a Terminal window to run a command clearing your DNS cache
DAW not recognizing MVP as MIDI device
Make sure the MVP is recognized by your computer as a MIDI device. Next, double check that the MVP is enabled as a MIDI device in your DAWs settings and that the MVP is selected as the output for your MIDI track(s).
Common issues with video screens
Resolution: the MVP will detect the resolution of your video output destination over HDMI and automatically adjust your content to fit. For the best results make sure your video files are rendered at the same aspect ratio and an equal or higher resolution as your output destination. The MVP will scale your content up or down to fit the entire video while preserving the aspect ratio, and in cases where the aspect ratio of your video file is different than the output this can result in black bars on the sides of your display where there is dead space.
Delay: the MVP has a negligible response time from receiving a MIDI trigger to playing back the corresponding cue, however depending on the length of your HDMI cable and the specs of your video output your system may have additional delay. We recommend testing your video playback any time your setup changes to appropriately compensate for the delay.
Inconsistent or under powered USB connection
Inadequate USB bus power can lead to issues with MVP's performance, particularly with networking and accessing the UI. For proper performance, ensure MVP has reliable, full power, especially when first booting. See below for tips:
* Disconnect unnecessary USB devices that may draw power allocation away from MVP.
* Connect MVP first before any other USB devices. Computers may allocate power priority based on the order of connection.
* Connect MVP to your computer through a powered USB hub that will provide MVP with its own reliable power. Leave other USB devices connected directly to the computer or another hub so that they do not draw from the same power supply.
* Once MVP has successfully booted via USB-C, you can connect the barrel plug PSU for redundant power. It's important that MVP first boots off USB power to load the proper gadget drivers.
If your issue is not addressed here, please reach out to [support](/archive-v12-userguide/resources-archive/contact-us).
# FAQ
Frequently asked questions.
I need to restart a song, will the MVP restart?
The MVP responds to MIDI notes to trigger the start of video clips or lighting cues. Once triggered, the MVP will play your cue independently of your session until the cue ends (when not in loop mode), until a new cue is triggered, or until playback is stopped by triggering MIDI note 0/C-2. To restart a song, trigger a playback stop if necessary and then make sure the cue is re-triggered on the song restart.
How many hours of video can I store on the MVP?
The MVP holds up to 100 gigabytes of video files. On average the MVP will hold around 33 hours of 2K video, or 70 hours of 1080p video.
How do I manually stop playback?
Playback can be stopped by triggering the MIDI note 0/C-2.
How long does it take to set up?
Most shows can be configured in under an hour! Once a show is configured, performing with the MVP is as simple as connecting it to your playback computer or hardware controller and connecting the output to your screen or lighting package.
Do I need any other hardware?
All you need is a MIDI source (controller or your existing playback computer) and something to output video and/or lights to. For video playback, MVP will output to any screen or projector over HDMI, and for lighting playback MVP outputs over ArtNet to any ArtNet node connected to your lighting package.
Are there additional features coming?
We have a long list of features we’re continually developing and will roll out through over-the-air updates. Note that lighting playback and LTC support are currently in open beta as we continue to develop features.
Why is the MVP hardware and not just software?
Software requires a computer to run on, meaning the added costs of a dedicated video/lighting playback machine, or adding processing strain to your existing audio playback machine. The MVP performs all the processing directly on the device, meaning no burden on your existing systems.
What is DMX and ArtNet?
DMX is the industry standard lighting data protocol for controlling stage lighting fixtures. A DMX signal includes 512 channels of data, each individual channel of which may control different parameters of a lighting fixture (color, position, etc) depending on the profile of that fixture and the DMX address (channel) it is set to begin listening to.
ArtNet is a protocol for transmitting DMX data over an ethernet connection and is capable of transmitting multiple DMX ‘universes’ (streams of data). ArtNet nodes are used to translate ArtNet into DMX for the final connection to lighting fixtures.
# Show Day Guide
Quick reference for day-of.
The MVP is designed to be quick and simple to set up at your show and allow you to focus on everything else on your to-do list. Follow this short list to ensure a smooth show:
1. When loading in and soundchecking, set up your MVP and connect it to your MIDI source and video and/or lighting outputs and ensure its getting power either from your computer or via the PSU. Always connect all other inputs and outputs before connecting the MVP to power (via USB-C host or PSU).
2. Confirm that the MVP is receiving MIDI signal from your source by sending MIDI from your computer or hardware controller and verifying that the note is registered on the display on the top of the MVP, and the corresponding cue is playing back.
3. If applicable, power on your video display with the HDMI input the MVP is connected to selected. Once again test sending MIDI from your source and confirm that the MVP is outputting video to your screen. Pay attention to the video sizing, resolution, and quality - issues with any of these aspects may be due to settings on your screen or SDI converter, or with the video file itself. Also pay attention to the delay between your MIDI trigger and the video appearing on screen by testing moments in your set where timing is particularly important. Different set ups with longer cable runs or different display specs may produce different delay lengths which can be accommodated for by adjusting the ‘track delay’ setting of your MIDI track if using DAW playback. For specific recommendations, check out [troubleshooting](/archive-v12-userguide/resources-archive/troubleshooting), or try power cycling the MVP.
4. If applicable, power on your lighting package and again test MIDI signal to make sure the MVP is outputting DMX to your lights. If any cues are producing different results than intended, double check that your fixtures are assigned the correct DMX addresses to receive the appropriate signal.
Once everything is working as intended, we recommend if possible leaving the MVP, MIDI source, video screen and lights powered on and untouched between soundcheck and your performance.
{% hint style="info" %}
For security purposes, we recommend disconnecting your MVP from any wifi before performance.
{% endhint %}
# Common Setups
Suggested setups to add MVP to your rig.
If you need ideas of how MVP could fit into your performance set up, here’s some common scenarios we see with the MVP:
### DAW Playback (Ableton, etc.)
Ideal for: Artists already performing with audio backing tracks. Easy audio/visual sync for impactful moments.
For artists already performing with audio backing tracks, MVP makes it simple to add time-synced video and lighting cues to your performance by simply adding a MIDI track to your DAW session outputting to the MVP.
Many artists have a single video clip the length of each song and can synch their performance with a single MIDI note at the start of each song. If your videos are in ‘loop’ mode, remember to trigger a stop at the end of each song with MIDI note 0/C-2.
If you have shorter clips, or if you need multiple playback start points throughout a song, pencil additional MIDI notes trigger clips at the beginning of new song sections. You may even cut a longer clip into smaller individual sections to have fallback trigger points, so long as you ensure the MIDI triggers are appropriately timed for seamless playback.
### MIDI Controller Playback
Ideal for: Artists not playing to audio backing tracks, more improvisational control
With any commercially available hardware MIDI controller, anyone can control video or lighting playback in real time. Controllers with a grid of sample pads that can be mapped to MIDI notes are the most natural for MVP control, such as the Roland SPD-SX, Akai APC, or Novation Launchpad.
Once configured, any performer on stage can use the MIDI controller to change dynamically between your video and/or lighting cues with the press of a button at the beginning of songs or sections. Or, you can easily give a non-technical crew member off stage control. For example, a front of house engineer can easily control lights as well without having to navigate an entirely separate console.
### Video Outputs
For artists performing in multiple venues without house video screens, short throw projectors are often an economical and portable option to output your video to. Projectors can be pointed against a blank wall, or a simple portable projector screen of which many are available.
### Lighting Packages
Because of the nature of the DMX protocol, the MVP currently needs to playback DMX cues specifically to the lighting package they were designed for and it will not produce consistent results across varying venue lighting packages. Artists using the MVP for lighting control typically tour with either a purchased or rented ‘floor package’ of consistent lights. Check our recommended partners page for more.
The types of fixtures that work best with the MVP are LED bars, strobes, or other non-moving heads that are relatively portable. LED bars in particular are easily programmed with many different effects and can be placed and configured in endless combinations. Depending on the size of your LED bars, they can generally be packed in a duffle bag or long rifle-style hard case for easy travel. On stage, they may be placed on the floor or mounted with simple bracket mounts.
Lighting vendors can also supply you with easily set up ‘pipe and base’ for mounting lights on if needed, but note that these will quickly add weight for traveling.
# Recommended Equipment
Suggested equipment to use in tandem with MVP.
If you're new to video and lighting production, below are some recommended pieces of equipment or manufacturers to consider. We will add to this list over time, and it is not intended to be exhaustive. We have no direct affiliation unless otherwise indicated.
### MIDI Controllers
* [AKAI](https://www.akaipro.com/products/controllers.html)
* [Novation Launch series](https://us.novationmusic.com/launch)
* [Roland SPD-SX](https://www.roland.com/us/products/spd-sx/)
### ArtNet Nodes
* [PKNight](https://www.pknightpro.com/)
### Lighting Rentals
* [Aspect Lighting](http://aspectlighting.com/) (US)
* [Christie Lites](https://www.christielites.com/) (UK)
# MVP Version 1.1 - New Features
The MVP Version 1.1 Update has introduced a number of really cool new features.
[#id-1.-beta-feature-effects-mode](#id-1.-beta-feature-effects-mode "mention")
[#id-2.-new-dashboard-real-time-status-info](#id-2.-new-dashboard-real-time-status-info "mention")
[#id-3.-lighting-up-to-16-universes](#id-3.-lighting-up-to-16-universes "mention")
[#id-4.-assignable-midi-channels](#id-4.-assignable-midi-channels "mention")
[#id-5.-sync-changes-to-playback-button](#id-5.-sync-changes-to-playback-button "mention")
## New Features Overview (Video)
{% embed url="" %}
## How to update your MVP to version 1.1 (Video)
This video shows how to download and apply the version 1.1 update on your MVP:
{% embed url="" %}
4CAST MVP v1.1 Update Guide
{% endembed %}
## 1. **Beta Feature: Effects Mode**
Effects Mode enables real-time video effects, controlled by MIDI CC messages.
### What does it do?
Effects Mode allows you to adjust video playback in real time using your MIDI controller or DAW.\
Currently there are 4 color balance and 4 transformation controls available. More will be added in the future.
### How Do I Enable Effects Mode?
1. Connect your MVP, open your browser and navigate to: mvp.local
2. Click on the Settings cog in the top right corner, and choose Beta Features.
3. Click the toggle switch to enable beta features.
4. Navigate to the Video Configuration page by clicking on Videos.
5. You will find a new **Video Mode** dropdown at the top of the page. Choose Effects Mode.
6. Start a video, and then use the MIDI CCs and notes below.
### How do I use it?
Assign your MIDI controller's CC knobs/sliders to the following:
* CC 48: Brightness
* CC 49: Contrast
* CC 50: Hue
* CC 51: Saturation
* CC 52: Rotation
* CC 53: Scale
* CC 54: Position X
* CC 55: Position Y
### Resetting Effects with MIDI Notes
You can quickly reset any effect to its default value by sending a specific MIDI note:
* Note 110: Reset all effects to their defaults
* Note 111: Reset Brightness
* Note 112: Reset Contrast
* Note 113: Reset Hue
* Note 114: Reset Saturation
* Note 115: Reset Rotation
* Note 116: Reset Scale
* Note 117: Reset Position X
* Note 118: Reset Position Y
### Default Values
* All effects' default CC value is 64 (centered),
* except Rotation, who's default CC value is 0 (no rotation).
\
Notes:
* Effects Mode is intended for creative live performance and VJ workflows.
* 4K video files are not supported.
## **2. New Dashboard – Real-time Status Info**
### “Currently Playing” display
Shows the active video and/or lighting clip and playtime at a glance.
### Real-time ArtNet viewer
Monitor the currently playing DMX data across all universes and channels.
### Real-time Device Status
* WiFi and Ethernet connection status and IP details.
* HDMI connection status, display name, resolution, and framerate.
* Input Monitor: View incoming MIDI notes (channel and device name) and LTC timecode frames.
* MVP Version & Update Notification area: See when updates are available.\
## **3. Lighting – Up to 16 Universes**
* Expanded support for up to 16 universes for recording and playback, perfect for larger-scale shows and more complex lighting setups.
## **4. Assignable MIDI Channels**
* Video and Lighting MIDI channels are no longer hardcoded to Channel 1 and Channel 3.
* Customize MIDI channel assignments on the Video Configuration and Lighting Configuration pages to fit your setup.
## **5. “Sync Changes To Playback” Button**
* Appears on Videos, Lighting, and LTC pages whenever configuration changes are made.
* Push it to immediately sync changes to the playback engine for instant setup and testing.
# Triggering the MVP from a DAW
Select your DAW below for simple configuration instructions.
{% content-ref url="/pages/ihd2hUNezVONuxPnRfHp" %}
[Ableton Configuration](/archive-v12-userguide/triggering-the-mvp-from-a-daw/ableton-configuration)
{% endcontent-ref %}
{% content-ref url="/pages/EEpPQd3Np6yG4Sn42i9h" %}
[Pro Tools Configuration](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/pro-tools-configuration)
{% endcontent-ref %}
{% content-ref url="/pages/Vy9bJgW8kYavqzGxmm11" %}
[Logic Pro Configuration](/archive-v12-userguide/5.-triggering-your-media/daw-computer-triggering/logic-pro-configuration)
{% endcontent-ref %}
# Ableton Configuration
Setting up playback with Ableton as a MIDI source.
If you perform with an Ableton playback session, MVP can easily be triggered by MIDI notes straight out of your Ableton session. First, make sure your MVP has been configured with MIDI mappings. See [Video Configuration](/archive-v12-userguide/resources-archive/quickstart/video-configuration) and [DMX Lighting Configuration](/archive-v12-userguide/resources-archive/quickstart/dmx-lighting-configuration-beta) for more details on this step.
Open your session and click Live > Settings > Link Tempo MIDI to access your MIDI settings. With the MVP connected to your computer via the USB-C ‘host’ port you should see ‘MVP’ listed under ‘MIDI Ports’. Make sure the ‘track’ box is checked on the MVP ‘out’ so that Ableton can send MIDI notes to the MVP. Currently the other settings will not impact the MVP either way, however future updates may make advantage of additional settings.
In your session add a MIDI track and select the MVP as the output. Below the output selection, select the appropriate MIDI channel based on what signal you want to send to the MVP. By default the MVP receives video triggers on MIDI channel 1 and lighting triggers on channel 3.\
Pencil notes into MIDI clips on the track at the points in your arrangement where you want to trigger playback on the MVP. You can also make specific clips in the Session view to trigger lighting and video cues in the MVP. \
\
Make sure each note you pencil corresponds to the correct MIDI mapping you configured on the MVP. When you playback your session, Ableton should output MIDI notes to the MVP in time with your music to sync your video or lights.
To trigger a stop of playback on the MVP, send MIDI note MIDI note 0/C-2. Remember the MVP plays back independently of your Ableton session and only receives MIDI information to trigger the start of a clip, so stopping playback on your Ableton session alone will note stop playback on the MVP.\
{% hint style="info" %}
PRO TIP: Render your song videos into "sections" to match the song arrangement, and trigger them individually per-section with unique MIDI notes. This allows much more flexibility to change the structure on the fly and not have to change what you program in the MVP.
{% endhint %}
# Device I/O
Explore the MVP's input & output options.
USB-C Host
Connect to a computer with a USB-C cable for configuration and set up, as well as MIDI over USB from any DAW (Ableton, ProTools, etc.).
HDMI Out
Send video signal out to any screen or projector. MVP receives info from your connected output source and adjusts your video playback accordingly. MVP outputs up to 4K, 30 frames per second.
Ethernet (ArtNet)
Send DMX lighting data over ArtNet to an ArtNet node and on to your lighting package. MVP supports up to 4 DMX universes at launch.
Simple ArtNet nodes are cheaply available on Amazon or from other retailers.
5V 2A power (optional)
The MVP is powered over USB when connected to a computer via the USB-C host port. For set ups without a connected computer, the MVP can be powered via the included power supply unit.
MIDI In
Receive MIDI input from any MIDI controller or source.
USB-A x 2
Receive MIDI input from any MIDI controller or source.
1/8" In/Out
Audio in for LTC timecode triggers (beta). Audio out for future implementations.
# Technical Specs
Storage: 100GB video & DMX clip storage
Supported Video File Types: h264 encoded mp4 and MOV files, up to 4k resolution & 30 frames per second
ArtNet output up to 4 DMX universes
Dimensions:\
Height: 1.25 in\
Width: 6 in\
Depth: 3.3 in
Other Features:\
Status display\
Indicator light\
2x VESA mounting holes, compatible with M2 screws
I/O:\
USB-C Host (for computer)\
USB-A x 2 (for MIDI controller)\
Ethernet (for ArtNet)\
MIDI In Port (5 pin DIN)\
HDMI Out\
5V 2A power (for optional PSU)
# MIDI Controller Profiles
Supported MIDI controllers.
While MVP can be used with any hardware controller that outputs to the appropriate MIDI channels and notes, MVP includes built in profiles for the following controllers that map controller buttons to MIDI blocks for easy configuration. As a rule of thumb, MIDI blocks starting at note 0 will be mapped to supported controllers' sample pads left to right, and bottom to top.
**Supported Controllers**
* AKAI APC Mini
* AKAI APC Mini MK2
* Novation Launchpad Mini MK3
This list will be added to as additional profiles are included in future updates.
# Hardware (Standalone) Triggering
The MVP is designed to run completely standalone, allowing you to trigger your show using physical controllers without a computer on stage.
This workflow is perfect for "DAW-less" setups, like drummers using sample pads, or guitarists using MIDI pedalboards.
***
### 1. Power Requirement
Since you are not connecting the MVP to a computer via the USB-C Host port, you must use the included DC Power Adapter.
* Connect the power adapter to the barrel jack on the rear of the MVP.
* *Note: The MVP provides power to USB controllers connected to its USB-A ports.*
***
### 2. Connection Methods
The MVP supports two types of hardware connections.
#### A. USB MIDI Controllers
Connect class-compliant USB MIDI controllers directly to the USB-A Ports on the back of the MVP.
* Examples: Novation Launchpad, Akai APC Mini, Korg nanoKEY.
* Compatibility: Any "Class Compliant" device (drivers not required) will work.
* Power: The MVP powers these devices over the USB cable.
#### B. 5-Pin DIN MIDI
Connect MIDI hardware using a standard 5-Pin MIDI cable to the MIDI IN Port.
* Examples: Line 6 Helix, Roland SPD-SX, Nord Keyboards, Behringer FCB1010.
***
### 3. General Setup Workflow
Regardless of which controller you use, the setup logic is consistent:
1. Set the MIDI Channel: Configure your hardware controller to transmit on the correct channel.
2. Map the Notes:
* On your controller, assign a specific button, key, or pad to a specific note (e.g., C#-2).
3. Trigger: Press the button. The MVP receives the "Note On" message and starts playback immediately.
***
### 4. Hardware Guides
Select your device type below for specific setup instructions:
* \[USB Controllers (Launchpad, APC, etc.)]
* \[Standard MIDI (SPD-SX, Helix, Keyboards)]
# USB Controllers
# MIDI Controllers
# MVP User Guide
Version 1.3
### Welcome
The 4CAST MVP is a compact, professional media playback device that plays perfectly synced video and lighting from MIDI, timecode, USB keyboards, or any combination.
This guide walks you through everything from unboxing to show day.
***
### New Here?
Start with the [Quick Start Guide](/quick-start-guide-videos) to get video playing in under 5 minutes.
***
### Guide Overview
| Section | What You'll Learn |
| ----------------------------------------- | ------------------------------------------------------------------ |
| [1. Getting Started](/1.-getting-started) | What's in the box, hardware connections, the UI, and the Dashboard |
| [2. Video Setup](/2.-video-setup) | Upload videos, download stock clips, and configure Effects Mode |
| [3. Lighting Setup](/3.-lighting-setup) | Record and trigger DMX lighting via ArtNet |
| [4. Timecode Setup](/4.-timecode-setup) | Build timelines and sync to LTC or MTC timecode |
| [5. Triggering](/5.-triggering) | MIDI notes, MIDI CC, USB keyboards, DAWs, and hardware controllers |
| [6. Configuration](/6.-configuration) | System settings and configuration slots |
| [7. Networking](/7.-networking) | Wi-Fi, Ethernet, ArtNet, and IP configuration |
| [8. Reference](/8.-reference) | MIDI reference, supported formats, troubleshooting, and FAQ |
| [9. Show Day](/9.-show-day) | Venue setup checklists |
# Quick Start Guide - Videos
This guide will help you get your MVP up and running in under 5 minutes with Video triggered by MIDI Notes. Please check the GETTING STARTED section for the full MVP documentation.
> *For* [*Timecode*](/4.-timecode-setup/timecode-overview)*,* [*MIDI CC Trigger Mode*](/5.-triggering/midi-cc-trigger-mode)*, or* [*Lighting Configuration*](/3.-lighting-setup/lighting-configuration) *information, please refer to those guides.*
***
## 1. Connect & Power Up
1. **Unbox**: Open the travel case. You will find the MVP unit, USB cables, mounting screws, and a power adapter.
2. **Connect**: Use the included USB-C cable to connect the MVP **HOST** port to your computer.
* ***Note**: The MVP powers on automatically via USB connection.*
3. **Verify**: After a few seconds, the Status Display on your MVP will light up.
***
## 2. Access the Dashboard
1. **Open Browser**: On your connected computer, navigate to `http://mvp.local`.
2. **Connect Wi-Fi**: Once the Dashboard loads, click the Wi-Fi icon in the top bar to connect your MVP to the internet. *(Required for updating your MVP and downloading Stock Videos.)*
***
## 3. Upload & Assign Videos
Click the **Videos** tab in the left-hand navigation menu to open **Video Configuration**.
### Option A: Upload Your Videos
Enable **EDIT MODE**, then drag and drop your video files directly onto the upload box.
* **Supported Codecs**: H.264, H.265, MJPEG, VP8, VP9
* **File Types**: .mp4, .mov, .m4v, .mkv, .webm, .jpg (still image)
* **Max Resolution**: 4K (30fps) or 1080p (60fps)
### Option B: Download Stock Video
Don't have any videos yet? Search through half a million royalty-free videos, and download them directly to your MVP.
1. Click the **Search Stock Videos** button.
2. Type a keyword (e.g., "Ocean," "Hyper Tunnel," "Tiger," "Clouds").
3. Select your resolution and click **Download**.
### Assign to MIDI
Once uploaded, use the dropdown menus to assign your videos to MIDI Notes (e.g., C#-2).
***
## 4. Play Your First Clip
#### If Using a Laptop (DAW)
1. Open your DAW (Ableton, Pro Tools, Logic, etc.).
2. In your DAW's MIDI settings, enable MIDI Output to **MVP**.
3. Create a new MIDI Track.
4. Set the Track Output to **MVP** on the MIDI channel configured in your Video settings (default: Channel 1).
5. Draw a note on the Piano Roll that matches your video assignment.
6. Press Play. The video will trigger instantly.
> *Detailed Instructions:* [*Triggering from a Computer (DAW)*](/5.-triggering/daw-computer-triggering)
#### If Using Hardware (Standalone)
1. Connect the included Power Adapter to the MVP.
2. Connect your MIDI Controller to the MVP via 5-Pin DIN or USB-A.
3. Press the corresponding physical key/pad on your controller.
> *See also:* [*Hardware Controller Setup*](/5.-triggering/hardware-controllers) *|* [*USB Keyboard Triggering*](/5.-triggering/usb-keyboards-hid)
***
## 5. Verify
If you aren't seeing video, check the Status Display on the device or the Dashboard in your browser. It will show you exactly which MIDI note was received and which file is attempting to play.
***
## What's Next?
* **Add Lighting**: [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- trigger DMX lighting clips alongside your videos
* **Timecode Sync**: [Timecode Overview](/4.-timecode-setup/timecode-overview) -- synchronize video and lighting to a timeline using LTC or MTC
* **Explore Triggering Options**: [Triggering Overview](/5.-triggering/triggering-overview) -- MIDI, keyboard, CC triggers, hardware controllers, and more
# 1. Getting Started
Everything you need to know before diving into video, lighting, or timecode setup. This section covers what's in the box, how to connect the hardware, and how to navigate the MVP's web interface and Dashboard.
***
#### In This Section
* [**What's Included**](/1.-getting-started/whats-included) — Unboxing, accessories, and device specs
* [**Hardware Connections & Specs**](/1.-getting-started/hardware-connections-and-specs) — Ports, cables, and physical setup
* [**The User Interface (UI)**](/1.-getting-started/the-user-interface-ui) — Navigating the MVP web interface
* [**The MVP Dashboard**](/1.-getting-started/the-mvp-dashboard) — Real-time status, playback monitoring, and input display
* [**Updating Your MVP**](/1.-getting-started/updating-your-mvp) — How to check for and install firmware updates
# What's Included
Congratulations on your new MVP! Let's see what's in the box.
#### In the Box
* Travel Case
* Your MVP
* Accessories:
* 1x USB-C to USB-A Cable
* 1x USB-C to USB-C Cable
* 4x M2 Screws (for VESA mounting)
* Power Adapter
#### Device Details
| Spec | Value |
| -------------- | --------------------------------------- |
| **Dimensions** | 1.25" x 6" x 3.3" (H x W x D) |
| **Storage** | 100GB internal |
| **Mounting** | VESA compatible with included M2 screws |
***
## Related Pages
* [Hardware Connections & Specs](/1.-getting-started/hardware-connections-and-specs) -- Port-by-port guide
# Hardware Connections & Specs
## Connection Ports
All connection ports are located on the rear panel of the device.
#### 1. Power - Barrel Jack (optional)
**Optional Power Supply**: If you are using the MVP without a computer (standalone), or if your computer's USB ports are underpowered, use the included DC power adapter.
#### 2. MIDI Input (5-Pin DIN)
Standard 5-pin MIDI input for connecting MIDI controllers, pedalboards, or any other MIDI equipment directly to the MVP.
#### 3. Ethernet Port
A gigabit connection used for lighting and network control:
* **Art-Net**: Outputs lighting data to Art-Net nodes. Up to **16 universes** (8,192 channels).
* **RTP-MIDI**: Allows control of the MVP over a local network ([Network MIDI](/5.-triggering/network-midi-rtp-midi-setup)).
* **UI Access**: Access the MVP interface from any device on the same network.
#### 4. HDMI Output
Supports video displays up to **4K resolution**. Connect this directly to your monitor, projector, or video wall processor.
The output resolution and refresh rate, and the on-screen position and size of the video, are configurable, **per display** — the MVP fingerprints each display by EDID and reapplies your saved settings automatically on reconnection. See [Display Settings](/6.-configuration/display-settings) and[ Display Calibration](/6.-configuration/display-settings/display-calibration).
#### 5. HOST Port (USB-C)
This is the primary connection for computer-based setups. A single USB-C cable handles three functions simultaneously:
* **Power**: Powers the MVP via USB bus power.
* **MIDI**: The MVP appears as a class-compliant MIDI device on your computer (no drivers required).
* **UI Access**: Provides access to the MVP web interface. Once connected, open a browser and navigate to `http://mvp.local`.
#### 6. USB-A Ports (x2)
Connect external peripherals to control the MVP:
* **USB MIDI Controllers**: Any class-compliant MIDI device (Akai APC Mini, Launchpad, drum pads, etc.).
* **USB Keyboards**: Trigger video and lighting cues via keystrokes. See [USB Keyboard Triggering](/5.-triggering/usb-keyboards-hid).
#### 7. Audio In (LTC)
3.5mm (1/8") audio input. Accepts a Linear Timecode (LTC) audio signal for synchronizing video and lighting playback to an external timecode source. See [LTC Setup](/4.-timecode-setup/ltc-audio-timecode-setup).
#### 8. Storage: 100GB
Enough space for more than 10 hours of high-quality 4K video or 27 hours of 1080p content.
***
## Device Status Indicators
Your MVP has two front-panel indicators that give you at-a-glance feedback:
* **Status Display** -- A color display that shows all connection info, trigger activity during performance, and a live timecode clock during timecode playback. It switches views automatically.
* **Status LED** -- A dual-color LED (blue/red) that indicates the current operating mode and flashes on triggers.
> For full details on what each display view shows and all LED behaviors, see [System Settings](/6.-configuration/system-settings).
***
## Supported Codecs & Formats
| Codecs | File Types | Max Resolution |
| ----------------------------- | ------------------------------------------ | ----------------------- |
| H.264, H.265, VP8, VP9, MJPEG | .mp4, .mov, .m4v, .mkv, .webm, .jpg, .jpeg | 4K/30fps or 1080p/60fps |
See [Supported File Formats](/8.-reference/supported-video-formats) for full details.
***
## Related Pages
* [What's Included](/1.-getting-started/whats-included) -- Box contents
* [The User Interface (UI)](/1.-getting-started/the-user-interface-ui) -- Browser access
# The User Interface (UI)
Here, we show how to access the MVP's web interface from your browser, including first-time setup and troubleshooting connection issues.
***
## Connect & Power Up
1. **Connect via USB-C**: Use the included USB-C cable to connect the MVP's **HOST** port to your computer.
* The MVP powers on automatically when connected via USB-C HOST.
* After a few seconds, the Status Display on the device will light up.
2. **Open your browser**: Navigate to: `http://mvp.local`\
> **Alternative URLs**: You can also use the direct USB IP address:
>
> * **Mac**: `http://192.168.3.1`
> * **Windows**: `http://192.168.2.1`
***
## First-Time Registration
On your first connection, the MVP will display a welcome dialog prompting you to:
1. **Connect to Wi-Fi** (or Ethernet) for internet access
2. **Enter your email** to register the device
Registration enables:
* MVP Update notifications
* Product support
***
## Getting Around the UI
1. **Settings Icons**: Once the Dashboard loads, you'll notice four icons on the top right corner.
* **Theme Icon**: Choose between Dark and Light modes.
* **User Icon**: Opens the MVP Registration dialog box.
* **WIFI Icon**: Opens the WIFI Connection dialog box.
* **Settings Icon**: Provides access to Ethernet Settings, System Settings, and this support site.
2. **Nav Bar Links**: On the left side of the UI, you can navigate between the Dashboard, Videos, Lighting, and Timecode configuration pages.\
Note: You can find details about each of those pages in their respective section.
***
## Accessing the MVP Over Wi-Fi
You don't need to stay connected via USB to use the web interface. Once your MVP is connected to Wi-Fi:
1. Find the MVP's Wi-Fi IP address on the **Dashboard** (Wi-Fi Status card) or the device's Status Display (shown on the HOME view scrolling ticker).
2. On any device connected to the **same Wi-Fi network**, navigate to that address:
Anytime your MVP is powered on and connected to your WIFI router, you can use that IP address in your browser
***
## Troubleshooting Connection Issues
### Browser won't load `mvp.local`
* **Try a different browser**: Some browsers cache DNS aggressively.
* **Clear your DNS cache** if you previously accessed the MVP via a different network:
* Mac: `sudo dscacheutil -flushcache`
* Windows: `ipconfig /flushdns`
***
## Related Pages
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard) -- Understanding the Dashboard
* [Wi-Fi Setup](/7.-networking/wifi-setup) -- Connecting to Wi-Fi networks
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Wired network setup
* [Update Your MVP](/1.-getting-started/updating-your-mvp) -- Firmware updates
# The MVP Dashboard
The Dashboard is the home page of the MVP web interface. It provides a live overview of everything happening on your device: what's playing, what signals are being received, and the status of all connected hardware.
***
## Playback Column
### Timecode Section
When timecode clips are configured in the [Timeline Editor](/4.-timecode-setup/the-timeline-editor), a timecode header and timeline appear at the top of the Playback column. If no timecode clips are configured, this section is hidden entirely.
The timecode header shows:
* **Active slot name**: Links to the Timecode page
* **Source & FPS chip**: Shows "LTC" or "MTC" with detected framerate (e.g., "LTC . 30fps"). Turns red with a pulse animation if the detected FPS doesn't match the configured FPS. Only visible when timecode signal is present.
* **Rate chip**: Shows playback speed (e.g., "1.000x"). Only visible when timecode signal is present.
* **SMPTE timecode display**: Large HH:MM:SS:FF display (classic LED clock style)
Below the header, a **Timecode Timeline** visualization shows:
* **Two track lanes**: VIDEO and LIGHTING with colored clip blocks
* **Ruler**: Major tick marks every minute (HH:MM:SS), minor ticks every 15 seconds
* **Red playhead**: Auto-follows the incoming timecode position during playback
* **Clip labels and thumbnails**: Video clips show image thumbnails, lighting clips show a "DMX" badge
### Playback Status Bar
Two side-by-side sectioins showing the current state of Video and Lighting playback:
| Field | Description |
| ------------ | ------------------------------------------------------------------------------------------- |
| **Title** | "Videos" or "Lighting Cues" (clickable to navigate to that page), with the active slot name |
| **State** | "Playing" (pulsing green) or stopped |
| **Filename** | Currently playing file |
| **Position** | Current playback position in HH:MM:SS.t format |
### Trigger Tables
Two scrollable tables showing the complete MIDI note-to-file assignment for Video and Lighting:
* **Note** column: MIDI note number (00-99)
* **File** column: Assigned filename
* **"Show only assigned"** checkbox: Filters both tables to hide empty notes
* **Green pulse highlight**: The currently playing clip's row pulses green
* **Note 00**: Always shows "Black Out" in both tables
### ArtNET Preview
A link labeled **"ArtNET Preview"** appears in the Lighting trigger table header. Clicking it opens a **floating overlay panel** in the top-right corner of the screen.
The overlay displays:
* **512-channel grid**: Each cell shows a DMX value (0-255)
* **Universe selector**: Dropdown to choose which of the 16 universes to view
* **Real-time updates**: Refreshes as DMX data changes
* **Close button**: Dismisses the overlay
***
## Device Status (Right Column)
### MVP Version
Shows the current firmware version with an info icon. Displays update status messages:
| Status | Display |
| ----------------------------------- | --------------------------------------------------------------------- |
| **Up to date** (internet connected) | "Your MVP is up to date" |
| **No internet** | "Connect to Internet to check for updates" |
| **Update available** | Pulsing green "MVP v\_\_\_ Update Available" with "Click for Details" |
| **Update downloaded** | "MVP v\_\_\_ Update Ready" with "Click for Details" |
| **Critical update** | "Important Update Available. Please download now." |
Click to open the [Update Dialog](broken://pages/0e63625673a69c52d4cdf033f488431cd1ac9d28). If no internet and an update is available, clicking here opens the Wi-Fi dialog instead.
### Wi-Fi Status
| Field | Description |
| -------------- | ------------------------------------------ |
| **SSID** | Connected network name, or "Not Connected" |
| **IP Address** | MVP's Wi-Fi IP address |
| **Subnet** | Network subnet mask |
Click to open the Wi-Fi configuration dialog. Grayed out when not connected.
### Ethernet Status
| Field | Description |
| -------------- | -------------------------------------- |
| **Mode** | "Static" or "DHCP", or "Not Connected" |
| **IP Address** | MVP's Ethernet IP address |
| **Subnet** | Network subnet mask |
Click to open Ethernet settings. Grayed out when not connected. A yellow warning icon appears if Wi-Fi and Ethernet share the same IP range.
### USB-C Host Status
| Field | Description |
| ------------- | ---------------------------------------------- |
| **Host Type** | "Mac", "PC", or "Disconnected" |
| **MVP IP** | The IP address the MVP uses on the USB network |
| **Host IP** | The IP address of the connected computer |
Grayed out when no computer is connected.
### HDMI
| Field | Description |
| --------------- | ----------------------------------- |
| **Device Name** | Connected display name |
| **Resolution** | Output resolution (e.g., 1920x1080) |
| **Framerate** | Output refresh rate (e.g., 60 Hz) |
Shows "Not Connected" when no display is detected. Grayed out when disconnected.
> To change the output resolution or reposition the video on the screen surface, see [Display Settings](/6.-configuration/display-settings) and [Display Calibration](/6.-configuration/display-settings/display-calibration).
***
## Input Monitor
The Input Monitor card is always visible in the right column and provides real-time feedback on all incoming signals.
### LTC Signal Quality (Conditional)
**Only visible when an LTC timecode signal is detected.** Two horizontal meters help you verify your LTC audio signal:
* **LTC Volume**: Shows incoming audio signal level in dB. Color-coded: green (good, -20dB to -1dB), orange (too low), red (clipping).
* **Frames Decoded**: Shows successful frame decode rate as a percentage. Green = no frame loss; orange/red = increasing loss. Displays "--" when no signal detected.
### MIDI Display
Shows the last received MIDI event with a green flash animation:
* **Note events**: "Note {number}"
* **CC events**: "CC: {number} Value: {value}"
### Event Log
A scrollable text area showing the most recent incoming events with timestamps. Events include:
* MIDI note triggers (with note number and device name)
* MIDI CC messages
* Device connect/disconnect events
* Slot switch events
***
## Video Effects Meters
**Only visible when Video Mode is set to "Effects" (Beta).**
Shows 8 vertical meters displaying the current MIDI CC value for each Effects Mode control:
| CC | Control | Default |
| ----- | ---------- | ------- |
| CC 48 | Brightness | 64 |
| CC 49 | Contrast | 64 |
| CC 50 | Hue | 64 |
| CC 51 | Saturation | 64 |
| CC 52 | Rotation | 0 |
| CC 53 | Scale | 64 |
| CC 54 | Position X | 64 |
| CC 55 | Position Y | 64 |
Reset notes (Note 110 = reset all, Notes 111-118 = reset individual) also update the meters.
See [Effects Mode](/2.-video-setup/effects-mode) for details.
***
## Related Pages
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Build and edit timecode shows
* [Video Configuration](file:///5753738/2.-Video-Setup/video-configuration.md) -- Assign video clips
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign lighting clips
* [Effects Mode](/2.-video-setup/effects-mode) -- Real-time video manipulation via MIDI CC
# Updating Your MVP
We release new features and improvements regularly. Keeping your MVP up to date ensures you have the latest features and improvements.
***
## How to Update
### 1. Connect to the Internet
Click the **Wi-Fi icon** in the top bar of the MVP UI to connect your MVP to a Wi-Fi network with internet access.
### 2. Check for Updates
When an update is available, the Dashboard's **MVP Version** section automatically displays a notification. The update availability is pushed in real time from the 4CAST cloud -- no manual check required.
* If your MVP is **up to date**, the card shows "Your MVP is up to date."
* If there is **no internet**, the card shows "Connect to Internet to check for updates."
* **Critical updates** are flagged with "Important Update Available. Please download now."
Click the version card to open the **Update Dialog**.
### 3. Download the Update
The Update Dialog shows the available version and details. Press **Download** to begin downloading the update package from the cloud.
\[SCREENSHOT: Update dialog showing version info and download button with progress bar]
A progress bar with percentage and status text tracks the download.
> If your MVP is not connected to the internet when an update is available, the dialog will prompt you to connect to Wi-Fi first.
### 4. Apply the Update
Once downloaded, the dialog shows "MVP v\_\_\_ Update Ready." Click **Apply Update** to begin the update process.
A warning dialog appears:
> **CRITICAL WARNING**: **DO NOT** power off the MVP during the update process. Once you click "Proceed," do not touch the MVP or the USB cable. Interruption during this process can render the device non-functional.
\[SCREENSHOT: Update warning dialog with the PROCEED button]
Click **Proceed** to confirm.
***
## After Updating
Once the update completes:
* The browser will **automatically refresh** after a few seconds
* The Dashboard will show the new version number
* All your video files, lighting clips, and configurations are preserved
***
## Tips
* **Don't rush**: Let the update process complete fully before interacting with the device.
* **Check release notes**: The update dialog shows what's new in each version.
***
## Related Pages
* [The User Interface (UI)](/1.-getting-started/the-user-interface-ui) -- Browser access and Wi-Fi setup
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard) -- Where update notifications appear
# 2. Video Setup
Configure your video clips, assign them to MIDI notes, and get them ready for playback. You can upload your own files or browse a library of royalty-free stock videos directly from the MVP.
***
#### In This Section
* [**Video Configuration**](/2.-video-setup/video-configuration) — Upload, assign, and manage your video clips
* [**Stock Videos** ](/2.-video-setup/stock-videos)— Search and download from a library of royalty-free clips
* [**Effects Mode**](/2.-video-setup/effects-mode) — Real-time video effects controlled via MIDI CC (Beta)
* [**Effects Mode: Crossfade**](/2.-video-setup/effects-mode/effects-mode-crossfade) — Smooth transitions between clips
* [**Loop Mode Override**](/2.-video-setup/loop-mode-override) — Per-clip Loop / Freeze / Blank behavior
# Video Configuration
The Video Configuration page is where you upload video files, assign them to MIDI notes, and configure playback behavior.
Click on the **VIDEOS** link on the left side bar to open the Video Configuration Page.
***
## Configuration Slots (A-E)
Five independent video configuration banks. Each slot has its own set of MIDI note-to-file assignments. Click a slot button to switch.
* Switching slots loads that slot's assignments immediately
* Rename any slot by clicking the pencil icon
* Switch slots during a live show via MIDI CC #119 (values: 10=A, 20=B, 30=C, 40=D, 50=E)
* Video and Lighting slots are **independent** -- you can have Video on Slot B and Lighting on Slot D
> *For more on slots:* [*Configuration Slots (A-E)*](/6.-configuration/configuration-slots)
## Global Video Settings
### MIDI Channel
Select which MIDI channel (1-16) triggers video clips. Default is **Channel 1**. The dropdown excludes whichever channel is assigned to Lighting to prevent conflicts.
### Video Mode (Beta)
> **Note**: Video Mode is only visible when **Beta Features** are enabled in [System Settings](/6.-configuration/system-settings).
Choose between two playback modes:
| Mode | Description |
| ---------------- | ------------------------------------------------------------------------------- |
| **Fast Trigger** | Standard mode. Instant video switching on MIDI trigger. Supports up to 4K. |
| **Effects** | Enables real-time video manipulation via MIDI CC 48-55. Limited to 1080p 60fps. |
Changing video mode requires confirmation -- a dialog warns that switching will immediately stop any currently playing video or lighting cue. See [Effects Mode](/2.-video-setup/effects-mode) for details.
### Loop Mode
Controls what happens when a video clip reaches the end:
| Option | Behavior |
| ---------- | --------------------------------------------------------- |
| **Loop** | Video restarts from the beginning automatically (default) |
| **Freeze** | Video holds on the last frame |
| **Blank** | Screen goes to black |
This is a **system-wide** setting that apply to every clip. To give an individual clip different end-of-clip behavior, use [Loop Mode Override](/2.-video-setup/loop-mode-override) in that clip's Video Info dialog.
> **Precedence:** [Autoplay](/6.-configuration/autoplay) → per-clip [Loop Mode Override](/2.-video-setup/loop-mode-override) → system-wide Loop Mode. If Autoplay is enabled for video, it advances to the next clip at the end of every clip and both Loop Mode Override and the system-wide Playback Option are ignored.
### Default Video on Boot
Select which video plays automatically when the MVP starts up. Options include:
* Any video or still image
* **BLACKOUT** (starts with a black screen)
> **Note**: If [Autoplay](/6.-configuration/autoplay) is enabled for video, the default video is skipped at boot. The MVP instead starts the first non-empty assignment in the active configuration slot.
### Edit Mode
Toggle **EDIT MODE** to enable configuration changes. When off, the page is read-only to prevent accidental edits during a live performance.
***
## MIDI Assignment Grid
The main area contains **100 cards** (MIDI notes 0-99):
### Card 0 -- Blackout
Always present, labeled **"VIDEO 00 - MIDI: C-2"** with the description "Black Out Clip." Triggering Note 0 on the video channel sends the output to black. This card cannot be reassigned.
### Cards 1-99
Each card shows:
* **Header**: Video Number and MIDI Note (e.g., "VIDEO 01 - MIDI: C#-2"). Note names use standard MIDI naming: C, C#, D, D#, E, F, F#, G, G#, A, A#, B with octave = floor(note/12) - 2.
* **File selector**: Autocomplete dropdown to assign a video file (only functional in Edit Mode)
* **Hint line**: When assigned, shows `FileName - FileSize`, clickable to show the Video Details
* **Currently playing indicator**: Green pulse animation on the active clip's card
* **Clear button**: Small X icon to unassign the video (Edit Mode only)
To assign a video to a note:
1. Enable **Edit Mode**
2. Click the dropdown on any card
3. Select a video file from the list
4. Click **Sync Changes to Playback** to apply
***
## Media Panel (Right Column)
### Sync Changes to Playback
After making any changes, click **"Sync Changes to Playback"** to apply your changes. Changes do not take effect until synced.
### Upload Videos
Drag and drop video files onto the **upload zone**, or click to browse.
**Accepted formats:**
| Extensions | MIME Types |
| --------------------------------------- | -------------------------------------------------------- |
| `.mp4`, `.mov`, `.m4v`, `.mkv`, `.webm` | video/mp4, video/quicktime, video/x-matroska, video/webm |
| `.jpg`, `.jpeg` | image/jpeg |
Still images (.jpg, .jpeg) are supported and display as persistent stills on screen.
**Upload validation:**
* **Filename characters**: Only letters, numbers, dashes, underscores, dots, and spaces are allowed. Files with other characters are rejected with an alert.
* **Duplicate detection**: If an uploaded file's basename (extension stripped, case-insensitive) matches any existing video file, the upload is blocked. A dialog shows "File Already Exists" with the conflicting filename and instructions to delete the existing file or rename the new file first. There is no overwrite option.
Upload progress is shown in the **Upload Queue Widget** in the bottom-right corner.
### Search Stock Videos
Click **"Search Stock Videos"** to browse and download from a library of over half a million royalty-free videos. Requires a Wi-Fi internet connection. See [Stock Videos](/2.-video-setup/stock-videos) for details.
### Free Disk Space
Shows the remaining storage space available on the device.
### Unassigned Videos
Lists all uploaded video files that are not currently assigned to any MIDI note in the current slot. From here you can:
* View file details by clicking the info icon
* Delete files (with confirmation)
> **Note**: You cannot delete a file that is assigned in other configuration slots. A dialog will inform you which slots reference the file.
### Video Info Dialog
Click the info icon on any video to see detailed information:
| Field | Description |
| -------------- | ---------------------------------------------------------------------------- |
| **Thumbnail** | Video preview image |
| **Filename** | Full filename |
| **Resolution** | (e.g., "1080p (1920x1080)") |
| **Codec** | Video format (e.g., "h264") |
| **File Type** | Extension in uppercase (e.g., "MP4") |
| **Duration** | Total length (formatted m:ss) |
| **File Size** | Video file size (KB, MB, GB) |
| **Frame Rate** | FPS (e.g., "30 fps") |
| **Source** | Source name with author link (stock), or "Local Upload" with date (uploaded) |
**Loop Mode Override**: Below the file details, a toggle lets you override the system-wide Loop Mode setting for this clip only — **Loop**, **Freeze**, or **Blank**. The override is saved immediately and travels with the file across slots and MIDI note reassignments. The section is hidden for still images. See [Loop Mode Override](/2.-video-setup/loop-mode-override).
For still images (.jpg/.jpeg), only Resolution, File Type, and File Size are shown (no codec, duration, or framerate).
***
## Tips
* **Edit Mode is your safety net**: Leave it off during shows to prevent accidental changes.
* **Sync after editing**: Don't forget to click "Sync Changes to Playback". Changes aren't active until synced.
* **Still images**: Upload .jpg files and assign them just like videos. They display as persistent stills on screen.
* **Effects mode is 1080p only**: If you enable Effects Mode, videos above 1080p will not play properly. Use Fast Trigger mode for 4K content.
***
## Related Pages
* [Stock Videos](/2.-video-setup/stock-videos) -- Free video library
* [All-Intra & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- Video preparation for timecode
* [Effects Mode](/2.-video-setup/effects-mode) -- Real-time video manipulation
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots) -- Multi-slot system
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [Loop Mode Override](/2.-video-setup/loop-mode-override) -- Per-clip end-of-clip behavior
* [Autoplay](/6.-configuration/autoplay) -- Automatic sequential playback
# Stock Videos
The MVP includes direct access to a library of over **half a million royalty-free stock videos**. Search, preview, and download content directly to your MVP.
**Prerequisite**: Your MVP must be connected to the internet via Wi-Fi.
***
## 1. Accessing the Library
1. Navigate to the **Videos** tab on the left sidebar.
2. Enable **Edit Mode**.
3. Click the **SEARCH STOCK VIDEOS** button in the right-hand media panel.
***
## 2. Searching & Browsing
The Stock Videos dialog opens with search and filter options:
* **Search Bar**: Type any keyword (e.g., "Ocean," "Cyberpunk," "Abstract," "Clouds")
* **Sort**: Popular (default) or Latest
* **Type**: All (default), Film, or Animation
* **Category**: All (default), plus 20 categories including Backgrounds, Nature, Science, Education, and more
* **Safe Search**: Off by default
* **Editor's Choice**: Off by default -- toggle to filter for curated content
* **Orientation**: Landscape (default) or Portrait
Results show video cards with:
* Hover to preview (video plays on hover)
* Resolution badge (4K / 2K / 1080p / 720p)
* Duration badge
* Author name
***
## 3. Preview & Resolution Selection
Click any video to open the **Preview & Download** window:
* **Video Player**: Preview the full video before downloading.
* **Resolution Selector**: Dropdown showing all available resolutions (4K, 2K, 1080p, 720p).
* **Author Attribution**: Profile link and author information
* **Tags**: Content tags for the video
***
## 4. Naming & Downloading
1. Click the **Download** button.
2. Enter a **custom filename** for the clip (max **48 characters**). The resolution suffix and `.mp4` extension are added automatically (e.g., `MyClip-1080p.mp4`).
* Allowed characters: letters, numbers, dashes, underscores, spaces
* Periods are not allowed (leave off the file extension)
* Invalid characters are automatically replaced with underscores
* The default filename suggestion is based on the video author's username
3. Click **DOWNLOAD** to save to your MVP.
The download progress appears in the **Stock Download Widget** in the bottom-right corner of the screen. Once complete, the video appears in your **Unassigned Videos** list ready to be assigned to a MIDI note.
***
## Tips
* **Search broadly**: Try different keywords to find unexpected content. Broad words like "Abstract" and "background" often yield great results for live visuals.
* **Wi-Fi speed matters**: Stock video downloads can be large (50-200MB). A fast Wi-Fi connection makes the process smoother.
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign downloaded videos to MIDI notes
* [Wi-Fi Setup](/7.-networking/wifi-setup) -- Internet connection required for stock videos
# Effects Mode
Effects Mode enables real-time video color and transformation controls via MIDI CC messages. This turns the MVP from a clip player into a visual performance tool.
> **Important Notes:**
>
> * **Resolution**: Effects Mode supports video playback up to **1080p 60fps only**. 4K and 2K videos are not supported in this mode.
> * **Beta Feature**: Effects Mode requires Beta Features to be enabled first.
***
## 1. How to Enable Effects Mode
Effects Mode is a feature that must be enabled in two steps:
### Step 1: Enable Beta Features
1. Click the **Settings** gear icon in the top-right corner.
2. Select **System**.
3. Click **Beta Features**.
4. Toggle the switch to **Enable**.
### Step 2: Activate Effects Mode
1. Navigate to the **Videos** tab and enable **Edit Mode**.
2. Use the **Video Mode** dropdown at the top of the page.
3. Select **Effects**.
4. Confirm the warning dialog (switching modes stops any currently playing video or lighting cue).
***
## 2. MIDI CC Controls
Assign these MIDI CC numbers to knobs or faders on your controller to manipulate video in real time. All CCs are sent on the **Video MIDI channel**.
| Parameter | CC Number | Range | Default | Description |
| ---------- | --------- | ----- | ------- | --------------------------------------- |
| Brightness | CC 48 | 0-127 | 64 | Adjusts video brightness |
| Contrast | CC 49 | 0-127 | 64 | Adjusts video contrast |
| Hue | CC 50 | 0-127 | 64 | Shifts color hue |
| Saturation | CC 51 | 0-127 | 64 | Adjusts color intensity |
| Rotation | CC 52 | 0-127 | 0 | Rotates the video frame (0-360 degrees) |
| Scale | CC 53 | 0-127 | 64 | Zooms in/out |
| Position X | CC 54 | 0-127 | 64 | Moves video left/right |
| Position Y | CC 55 | 0-127 | 64 | Moves video up/down |
**Default values**: Most effects use MIDI value **64** (midpoint) as the default/neutral position. Rotation defaults to **0** (no rotation).
### Dashboard Monitoring
When Effects Mode is active, the Dashboard's Device Status column shows **8 vertical meters** displaying the current value of each CC control in real time.
***
## 3. Resetting Effects (MIDI Notes)
Instantly snap any effect back to its default value by sending a MIDI note on the **Video MIDI channel**:
| Reset Function | MIDI Note |
| --------------------- | ------------ |
| **RESET ALL EFFECTS** | **Note 110** |
| Reset Brightness | Note 111 |
| Reset Contrast | Note 112 |
| Reset Hue | Note 113 |
| Reset Saturation | Note 114 |
| Reset Rotation | Note 115 |
| Reset Scale | Note 116 |
| Reset Position X | Note 117 |
| Reset Position Y | Note 118 |
***
## 4. Crossfade
Effects Mode can smoothly **crossfade between videos** when you trigger a new clip, instead of cutting instantly.
1. Open **Settings** → **System** → **Beta Features**.
2. Expand the **Effects Mode (Video Playback)** panel and scroll to **Crossfade** at the bottom.
3. Toggle **Enable Crossfade** and set the **Crossfade Duration** (0.1 – 5.0 seconds, default 1.0).
Key behaviors:
* **Triggers during a crossfade are ignored** — the current transition always completes before a new one can start.
* **Blackout fades too**, using the same duration.
* **Re-triggering the current clip restarts it instantly** (no fade).
* **Timecode playback is always instant** — crossfade is automatically bypassed for frame accuracy.
See [Effects Mode: Crossfade](/2.-video-setup/effects-mode/effects-mode-crossfade) for full details.
***
## 5. MIDI Controllers
For MIDI controllers, manually assign CC 48-55 to knobs or faders in your controller's configuration software.
**Akai APC Mini** and **APC Mini MK2:** Since these two controllers are not programmable, The MVP automatically maps their 8 faders directly to CC 48-55, and includes toggle buttons to enable/disable individual effects. See [Hardware Controllers](/5.-triggering/hardware-controllers#akai-apc-mini-original-and-mk2) for details.
***
## Tips
* **Use Note 110 as a panic button**: Assign it to an easily accessible pad to instantly reset all effects to defaults.
* **Combine with clip switching**: You can trigger different videos while simultaneously adjusting effects -- the CC values persist across clip changes and crossfades.
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Video Mode selection
* [Hardware Controllers](/5.-triggering/hardware-controllers#akai-apc-mini-original-and-mk2) -- APC Mini fader mappings
* [MIDI Reference](/8.-reference/midi-reference) -- Complete CC and note reference
# Effects Mode: Crossfade
Smooth transitions between clips in Effects Mode, with a configurable 0.1–5.0 second fade.
## Effects Mode: Crossfade
**Crossfade** brings smooth transitions to Effects Mode. When enabled, triggering a new video no longer cuts instantly — the outgoing and incoming clips blend across a configurable fade, exactly like a video mixer's T-bar. All eight real-time effects (brightness, contrast, hue, saturation, rotation, scale, position X/Y) apply to the combined image during the fade.
Crossfade is part of [**Effects Mode**](/2.-video-setup/effects-mode) and is available only when the Video Mode is set to Effects. Fast Trigger and Timecode modes are unaffected.
***
### Where to Find It
1. Click the **gear icon** in the top-right corner of any page.
2. Select **System**, then open **Beta Features**.
3. Expand the **Effects Mode (Video Playback)** panel.
4. Scroll to the **Crossfade** section.
There you'll find:
* **Enable Crossfade** — the master switch for this feature.
* **Crossfade Duration** — how long the fade lasts, in seconds. Range is **0.1 to 5.0** seconds in 0.1 s steps (e.g. `1.2`). The default when first enabled is **1.0** second.
Changes apply immediately to the next trigger — no restart required. Turning the toggle off disables crossfading entirely (instant cuts).
***
### Rules During a Fade
* **New triggers are ignored while a crossfade is in progress.** If you fire another note mid-fade, it's ignored. Wait for the fade to finish (plus a fraction of a second), then trigger again. Keep this in mind when choosing longer durations for fast-paced triggering.
* **Blackout crossfades too.** Triggering blackout (Note 0) fades to black over the same duration. Like any other trigger, blackout is ignored if a fade is already running.
* **Re-triggering the same clip restarts it instantly.** Firing the note of the clip that's already playing seeks back to the start with no fade, same as it always has.
#### Timecode Is Always Instant
Timecode playback is frame-accurate by design, so **crossfade is automatically bypassed whenever timecode is active** — clip changes driven by LTC are always instant, regardless of the Crossfade setting. You don't need to toggle anything off before a timecode show.
***
### Interaction with Effects
The MIDI CC effects (CC 48–55) and reset notes (110–118) work exactly as before. Effects are applied to the **combined output**, so during a fade both clips are colored and transformed together — brightness, hue, rotation, scale, and position all remain live throughout the transition.
***
### Good to Know
* **1080p limit.** As with all of Effects Mode, video is limited to 1080p 60fps (4K media is not supported in this mode).
* **Beta feature.** Crossfade ships as part of Effects Mode under Beta Features. Feedback to is welcome.
# Loop Mode Override
Set per-video end-of-clip behavior — Loop, Freeze, or Blank — overriding the system-wide playback option.
## Loop Mode Override
The MVP has a **system-wide playback mode** that decides what happens when a video reaches the end of its file: it can **loop** back to the start, **freeze** on the last frame, or go to **blank** (black). For most shows you pick one of these once and forget about it.
But some clips need to behave differently from the rest of the show.
**Loop Mode Override** lets you set that behavior **per video file**, overriding the system-wide setting just for that one clip. The override is saved as a tiny metadata sidecar next to the video file, so it follows the clip even if you re-assign it to a different MIDI note or move it between Configuration Slots.
***
### Where to Find It
1. Open the **Video Configuration** page.
2. Click a video to open the **Video Info** dialog.
3. Look for the **Loop Mode Override** section.
The section is hidden for still images — `.jpg` and `.jpeg` files.
***
### How to Use It
The section starts with a single labelled toggle:
* **Toggle off (default)** — the video uses the system-wide playback mode. No override is stored.
* **Toggle on** — a selector appears below the toggle with three options: **Loop**, **Freeze**, **Blank**.
Pick the behavior you want. Your choice is saved immediately — there's no Apply button.
#### Loop
The video loops back to the start and plays again, immediately and continuously. Use this for any video where you want endless playback without operator action.
#### Freeze
When the video reaches its end, the **last frame holds on screen**. The frame stays until you trigger another video.
#### Blank
When the video reaches its end, the screen goes **black**.
***
### Behavior at End-of-Video
When a clip reaches its end, the MVP resolves what to do in this order:
1. **Is Autoplay enabled for video?** If yes, the next non-empty assignment is started. Override is ignored — autoplay always wins. (See [Autoplay](/6.-configuration/autoplay).)
2. **Does the clip have a Loop Mode Override?** If yes, use that override.
3. **Otherwise, use the system-wide playback option** (loop / freeze / blank).
This means a Freeze override on a clip will only show its frozen-frame behavior if Autoplay is off. With Autoplay on, the system advances at the end of every clip regardless of overrides, which is usually what you want for "set and forget" sequential playback.
***
### When to Use Override vs. System-wide
**Set the system-wide mode** when most of your show wants the same behavior. For a live music show that loops bumpers between songs, set system-wide to **Loop** and only override the few clips that need to freeze or blank.
**Use overrides** for the small number of clips that diverge — the intro, the outro, the freeze-frame curtain call. Two or three overrides per show is typical. Don't try to manage 50 overrides; that's what changing the system-wide mode is for.
***
### Related Pages
* [Autoplay](/6.-configuration/autoplay) — Sequential playback that overrides Loop Mode Override
* [Loop Mode](/2.-video-setup/video-configuration#loop-mode) — System-wide Loop / Freeze / Blank / Crossfade settings
# 3. Lighting Setup
The MVP can record and play back DMX lighting data over ArtNet, letting you trigger synchronized lighting alongside your video clips. This section covers how to record lighting scenes from your lighting software or desk.
***
#### In This Section
* [**Lighting Configuration**](/3.-lighting-setup/lighting-configuration) — Assign lighting clips to MIDI notes and configure ArtNet output
* [**Recording ArtNet - Lighting Software**](/3.-lighting-setup/recording-artnet-lighting-software) — Capture DMX data from software like QLC+ or MagicQ
* [**Recording ArtNet - Lighting Desk**](/3.-lighting-setup/recording-artnet-lighting-desk) — Capture DMX data from a physical lighting console
# Lighting Configuration
The Lighting page is where you assign DMX lighting clips to MIDI notes, record new clips, and configure the lighting output.
***
## Configuration Slot (A-E)
Five independent lighting configuration banks. Each slot has its own MIDI note-to-DMX-clip assignments.
* Click the slot name in the header to expand the slot selector
* Switch slots by clicking on any slot in the list
* Rename any slot by clicking the pencil icon (up to 30 characters)
* Switching slots prompts you to sync -- choose "Sync to Playback," "Not Now," or "Cancel"
* Switch slots during a live show via MIDI CC #119 on the **lighting** MIDI channel (values: 10=A, 20=B, 30=C, 40=D, 50=E)
* Lighting and Video slots are **independent** -- you can have Lighting on Slot C and Video on Slot A
> *For more on slots:* [*Configuration Slots (A-E)*](/6.-configuration/configuration-slots)
***
## Global Lighting Settings
### MIDI Channel
Select which MIDI channel (1-16) triggers lighting clips. Default is **Channel 3**. The dropdown excludes whichever channel is assigned to Video to prevent conflicts.
### ArtNet Settings
Displays the current **Ethernet IP** and **Subnet Mask** used for ArtNet output. This is configured in the [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration), not on this page.
The MVP broadcasts ArtNet data on the Ethernet interface with support for **up to 16 DMX universes** (8,192 channels).
### Edit Mode
Toggle **EDIT MODE** to enable changes. When off, the page is read-only.
***
## DMX Assignment Grid
The main area contains **100 cards** (MIDI notes 0-99):
### Card 0 -- Blackout
Always present. Label: **"DMX 00 - MIDI: C-2"** with value "Black Out Clip" and hint "Sends zero to all DMX channels." Triggering Note 0 on the lighting channel loads a special blackout clip that zeros all 512 DMX channels across all 16 universes. This card cannot be reassigned.
### Cards 1-99
Each card shows:
* **Header**: DMX Clip number and MIDI Note (e.g., "DMX 01 - MIDI: C#-2")
* **File selector**: Autocomplete dropdown listing all DMX clips
* **Clear button**: Small X icon to unassign (Edit Mode only)
* **Currently playing indicator**: Green pulse animation on the active clip's card
To assign a clip:
1. Enable **Edit Mode**
2. Click the dropdown on any card
3. Select a DMX clip from the list
4. Click **Sync Changes to Playback** to apply
***
## Media Panel (Right Column)
### Sync Changes to Playback
After making assignment changes, click **"Sync Changes to Playback"** to push the new changes. Changes do not take effect until synced.
### Record New Clip
Unlike the Videos page where you upload files, the Lighting page allows you to record ArtNet data directly from your lighting console or software.
* Record Button: Click the **RECORD NEW CLIP** button to open the recording dialog.
> *For detailed ArtNet recording setup with lighting software or a lighting desk, see:*
>
> * [*Recording ArtNet -- Lighting Software*](broken://pages/d94e8f7a086466b2dc36d6a108e15f5f8b93c7a9)
> * [*Recording ArtNet -- Lighting Desk*](broken://pages/10510c154f78c5e783ca13d18a35f0f4cf92c263)
### Free Disk Space
Shows remaining device storage spacce.
### Unassigned Clips
Lists all DMX clips not currently assigned to any MIDI note in the active slot. Each item shows the clip name and file size. Clips can be deleted from here (with confirmation).
> **Note**: You cannot delete a clip that is assigned in other configuration slots. A dialog will list which slots reference the file.
***
## ArtNet Preview
The Dashboard includes an [ArtNet Preview](/1.-getting-started/the-mvp-dashboard#artnet-preview) fthat shows a real-time 512-channel grid of DMX values. Use this to verify your clips are sending the expected data:
1. Assign and sync a clip
2. Trigger it (via MIDI, keyboard, or timecode)
3. Open the ArtNet Preview from the Dashboard's Lighting trigger table
4. Select the universe you want to inspect (1-16)
5. Verify the DMX channel values are flowing and match your expectations
***
## Related Pages
* [Recording ArtNet -- Lighting Software](/3.-lighting-setup/recording-artnet-lighting-software) -- Record from ONYX, LightKey, QLC+, Show Buddy
* [Recording ArtNet -- Lighting Desk](/3.-lighting-setup/recording-artnet-lighting-desk) -- Record from GrandMA, Avolites, ChamSys
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Network setup for ArtNet
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots) -- Multi-slot system
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
# Recording ArtNET - Lighting Software
> ⚠️ FIRMWARE CHECK
>
> Please ensure your MVP is running at least version 1.2.x firmware before proceeding.
>
> *To check for updates instructions, read the* [*Update your MVP Guide*](/1.-getting-started/updating-your-mvp)*.*
***
#### 1. The Concept (USB Passthrough)
In the past, recording from a computer required a complex network switch setup.
Now, the MVP supports **USB-ArtNET Passthrough**.
How it works:
1. Your Laptop sends ArtNet data to the MVP via the USB-C cable.
2. The MVP records this data internally.
3. Simultaneously, the MVP broadcasts/forwards that data out of its Ethernet port to your ArtNET Node.
Result: You can see your physical lights react in real-time while you record, with zero latency and no network switch required.
***
#### 2. Hardware Connections
1. Laptop to MVP: Connect your computer to the MVP's HOST (USB-C) port.
2. MVP to Lights: Connect the MVP's ETHERNET port directly to your ArtNet Node.
***
#### 3. Network Configuration (Crucial Step)
Because the MVP is acting as a bridge between your computer and your lights, we need to ensure the IP addresses are set correctly on both your MVP and ArtNET node.
**A. The Ethernet Side (MVP -> Node)**
This connection uses the standard ArtNet "2.x.x.x" range. Do not use other IP ranges unless you are experienced with ArtNET configurations.
* **ArtNet Node**: Set your node to a static IP (e.g., `2.0.0.10`) and Subnet Mask `255.0.0.0`.
* **MVP Ethernet**: Go to **Dashboard** > **Settings** > **Ethernet** and ensure the MVP is set to a compatible static IP (Default: `2.0.0.111`) and Subnet Mask `255.0.0.0`.
**B. The USB Side (Laptop -> MVP)**
This connection uses a separate private network created through the USB cable by the MVP.
* **Windows**: The MVP connection appears as `192.168.2.111`.
* **Mac**: The MVP connection appears as `192.168.3.100`.
* *Note: You cannot change these addresses; just ensure your lighting software targets this network interface.*
***
#### 4. Software Setup
Configure your lighting software to output ArtNet to the MVP's USB network interface.
Example (Generic):
1. Open your Network/DMX settings.
2. Enable ArtNet Output.
3. **Interface Selection**: Select the network adapter that corresponds to the MVP's USB connection (e.g., `192.168.2.111` or `192.168.3.100`).
* *Do NOT select your Wi-Fi or hardwired Ethernet adapter.*
4. **Enable Broadcast**: Broadcast Mode must be enabled
5. **Universe Mapping**: The MVP supports recording up to 16 Universes. Ensure your software is broadcasting the desired universes (e.g., Univ 1–16).
**ONYX** Lighting Software:
**LightKey** Lighting Software:
**QLC+** Lighting Software:
**Show Buddy** Lighting Software:
***
#### 5. Recording Process
**Step 1: Recording Dialog Box**
1. Navigate to the Lighting tab on the MVP UI.
2. Toggle **EDIT MODE** to **ON**.
3. Click the **RECORD NEW CLIP** button on the right sidebar.
**Step 2: Verify Signal**
Before recording, look at the **ArtNET Preview** grid in the dialog box.
* **Play a Cue**: Fire a lighting cue in your software.
* **Check Preview**: You should see the grid pixels dancing *AND* your physical lights connected to the node should light up.
* *If the grid moves but physical lights don't:* Check your Ethernet connection, and Node IP.
* *If nothing moves:* Check your Software Output Interface (Step 4).
**Step 3: Capture**
1. **Name Your Clip**: Enter a descriptive name (e.g., "Chorus Strobe").
2. **Arm the Recorder**: Press the red **START RECORDING** button.
3. **Wait for Data**: The MVP is now "Armed" and listening, but it will not begin recording until it detects the first change in DMX values. This feature ensures your clips are perfectly tight, with no empty "dead air" at the beginning of the clip.
4. **Perform**: Play your lighting cue in your lighting software. As soon as the MVP detects a value change on *any* DMX channel, it will instantly start recording.
5. **Stop**: Press **STOP RECORDING**.
The new clip will immediately appear in your Unassigned Clips list, ready to be mapped to a MIDI note.
# Recording ArtNET - Lighting Desk
The MVP supports recording and playback of up to 16 Universes. This guide covers how to record lighting clips onto your MVP using a physical lighting console (such as GrandMA, Avolites, ChamSys, etc.)
#### 1. The Concept (The Network Switch)
Unlike the Software workflow which uses USB, recording from a physical desk requires an Ethernet connection.
Because the MVP has a single Ethernet port, it cannot "pass through" Ethernet data to your lights while simultaneously receiving it from the console. Therefore, we use a standard Network Switch to create a shared network.
How it works:
1. Your Console broadcasts ArtNet data into the Network Switch.
2. The Switch splits this signal to all connected devices.
3. The MVP receives the data to record it.
4. Your ArtNet Node receives the same data to drive the lights.
Result: You can see your physical lights react in real-time while you record, ensuring your looks are perfect before capturing.
***
#### 2. Hardware Connections
You will need a basic **Gigabit Network Switch** and three Ethernet cables.
1. **Console to Switch**: Connect your Lighting Desk's Ethernet port to the Switch.
2. **MVP to Switch**: Connect the MVP's ETHERNET port to the Switch.
3. **Node to Switch**: Connect your ArtNet Node to the Switch.
***
#### 3. Network Configuration (Crucial Step)
For ArtNet to work, all three devices (Console, MVP, and Node) MUST be on the same IP range. The industry standard for ArtNet is the `2.x.x.x` range.
**A. IP Address Rules**
Set all devices to Static IP addresses. They must share the first number (2) and the Subnet Mask, but the last number must be unique.
* **Subnet Mask**: Set ALL devices to `255.0.0.0`
Recommended IP Map:
* **Lighting Console**: `2.0.0.20`
* **ArtNet Node**: `2.0.0.10`
* **MVP Ethernet**: `2.0.0.111`
* *To configure your MVP:* Go to **Dashboard** > **Settings** > **Ethernet** and enter the IP/Subnet manually.
***
#### 4. Console Setup
Configure your lighting desk to output ArtNet to the network.
1. **Enable ArtNet**: Go to your console's Network/DMX Protocols settings and enable ArtNet Output.
2. **Broadcast Mode**: Ensure the Output Mode is set to Broadcast.
* *Why?* Broadcast sends the data to everyone on the network. If you use "Unicast," you would have to tell the console to send data specifically to the MVP's IP address, which is more complex to set up.
3. **Universe Mapping**: Ensure your console is outputting the correct universes (e.g., Universe 1–16).
***
#### 5. Recording Process
**Step 1: Recording Dialog Box**
1. Navigate to the Lighting tab on the MVP UI.
2. Toggle **EDIT MODE** to **ON**.
3. Click the **RECORD NEW CLIP** button on the right sidebar.
**Step 2: Verify Signal**
Before recording, look at the ArtNET Preview grid in the dialog box.
1. **Play a Cue**: Fire a lighting cue on your console.
2. **Check Preview**: You should see the grid pixels dancing in the MVP UI AND your physical lights connected to the node should light up.
* *If the lights work but the MVP grid doesn't move:* Check the MVP's IP settings.
* *If nothing works:* Check your Console's output settings and the Network Switch power.
**Step 3: Capture**
1. **Name Your Clip**: Enter a descriptive name (e.g., "Verse Blue Wash").
2. **Arm the Recorder**: Press the red START RECORDING button.
3. **Wait for Data**: The MVP is now "Armed" and listening. It will not begin recording until it detects the first change in DMX values. This ensures your clips are tight, with no "dead air" at the start.
4. **Perform**: Play your lighting cue on the console. The MVP will instantly start recording as soon as the values change.
5. **Stop**: Press STOP RECORDING.
The new clip will immediately appear in your Unassigned Clips list, ready to be mapped to a MIDI note.
**Step 4: Test Your New Clip (Crucial)**
Once your clip is recorded, you will want to play it back to see how it looks.
⚠️ **IMPORTANT**: Before you trigger the clip on the MVP, you MUST stop your lighting console from outputting ArtNet.
**The "Glitch" Effect**: Even if your console faders are at zero, the desk is likely still broadcasting "0" values to the network 40 times a second. If the MVP tries to send lighting data to the node while the console is also sending "zeros," the two signals will fight. This results in flickering, strobing, or glitching lights.
How to Test Cleanly:
1. **Silence the Console**: Either disable ArtNet Output in your console's settings OR simply unplug the Ethernet cable connecting the Console to the Switch.
2. **Assign the Clip**: On the MVP Lighting page, assign your new clip to a MIDI Note (e.g., `DMX 01`).
3. **Trigger**: Send that MIDI note to the MVP.
4. **Verify**: Your lights should play back the recorded look smoothly, exactly as it was captured.
*Once you are finished testing, remember to re-enable your console output to record the next look.*
# 4. Timecode Setup
The MVP supports frame-accurate, timeline-based playback driven by SMPTE timecode. Build a timeline of video and lighting cues, connect a timecode source (LTC audio or MTC MIDI), and the MVP handles synchronization automatically.
***
#### In This Section
* [**Timecode Overview**](/4.-timecode-setup/timecode-overview) — How timeline-based playback works and what you need
* [**The Timeline Editor**](/4.-timecode-setup/the-timeline-editor) — Build and edit your show timeline in the MVP web interface
* [**All Intra Videos** ](/4.-timecode-setup/all-intra-videos)— Why All-Intra encoding matters for frame-accurate seeking
* [**MTC (MIDI Timecode) Setup**](/4.-timecode-setup/mtc-midi-timecode-setup) — Receive timecode over MIDI
* [**LTC (Audio Timecode) Setup**](/4.-timecode-setup/ltc-audio-timecode-setup) — Receive timecode via the 3.5mm audio input
* [**Exporting All-Intra from Editing Software**](/4.-timecode-setup/exporting-all-intra-from-editing-software) — Encode All-Intra files from Premiere, Resolve, and others
# Timecode Overview
Frame Accurate Timecode
The MVP supports **timeline-based show playback**, where incoming SMPTE timecode drives video and lighting clips in perfect sync with your audio source. This is designed for live performances where a DAW, ShowKontrol or a dedicated timecode generator provides the master clock.
***
## Frame-Accurate Playback
The MVP delivers frame-accurate playback of both Video and Lighting at any point on your timeline. The MVP automatically handles synchronization and speed matching. You just build your timeline and let the MVP do the rest.
## How It Works
1. **You build a timeline** using the MVP's built-in [Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- placing video and lighting clips at specific timecode positions.
2. **A timecode source** sends SMPTE timecode to the MVP (via audio or MIDI).
3. **The MVP follows along** -- loading the correct files, seeking to the right position, and keeping perfect sync.
When the incoming timecode falls outside any clip on the timeline, video goes to blackout and lighting holds its last state.
***
## Timecode Input Methods
The MVP accepts timecode from two formats. Both can be connected simultaneously -- whichever signal arrives drives playback. There is no priority or arbitration between them.
### LTC (Linear Timecode) - Audio
| | |
| ------------------ | --------------------------------------------------------------- |
| **Connection** | 3.5mm (1/8") audio input on the rear of the MVP |
| **Signal** | SMPTE LTC encoded as an audio waveform |
| **Common Sources** | DAW audio output, click track with LTC, dedicated LTC generator |
> *Setup details:* [*LTC (Audio Timecode) Setup*](/4.-timecode-setup/ltc-audio-timecode-setup)
### MTC (MIDI Timecode)
| | |
| ------------------ | ------------------------------------------------------------ |
| **Connection** | Any MIDI input: USB-C, 5-pin DIN, or Network MIDI (RTP-MIDI) |
| **Signal** | MIDI Timecode |
| **Common Sources** | DAW MIDI output, timecode converters, show controllers |
MTC provides additional capabilities beyond LTC:
* **MMC (MIDI Machine Control)**: Your DAW can send Stop, Play, and Locate commands to pause, resume, and scrub the MVP's playback position. (Pause is treated identically to Stop.)
* **Network delivery**: MTC can be sent via Ethernet or Wi-Fi [Network MIDI (RTP-MIDI)](/5.-triggering/network-midi-rtp-midi-setup).
> *Setup details:* [*MTC (MIDI Timecode) Setup*](/4.-timecode-setup/mtc-midi-timecode-setup)
***
## Supported Frame Rates
| Frame Rate | Standard |
| -------------- | ---------- |
| 24 fps | Film |
| 25 fps | PAL / EBU |
| 29.97 fps (DF) | Drop Frame |
| 30 fps | Default |
The frame rate is configured per timecode slot in the [Timeline Editor](/4.-timecode-setup/the-timeline-editor). If the detected incoming frame rate doesn't match your configured rate, an amber warning chip appears in the timecode status bar.
***
## Sync Capabilities
The MVP doesn't just trigger clips at timecode points -- it **continuously synchronizes** playback:
* **Frame-accurate seeking**: Jump to any point on the timeline and playback starts at the correct frame *(requires* [*All-Intra encoded video*](/4.-timecode-setup/all-intra-videos)*)*.
* **Variable-speed following**: The MVP can follow timecode sources playing at anywhere from **50% to 200% of normal speed** (e.g., CDJ pitch fader, DAW rate change).
* **Transport control (MTC)**: Stop, Play, and Locate commands from your DAW control the MVP's playback -- freeze on a frame, resume, or jump to a specific position.
* **Signal loss protection**: If the timecode signal drops momentarily, playback continues smoothly. If the signal is lost for longer then one second, playback pauses gracefully (video goes to black, lighting holds last state). When signal returns, the MVP re-acquires and resumes sync.
***
## Timecode Slots (A-E)
Like Video and Lighting, the Timecode system supports **5 independent configuration slots (A-E)**. Each slot contains a complete timeline arrangement with its own video and lighting clip placements and frame rate setting.
* Switch slots from the Timecode page header
* Timecode slot switches take effect **immediately** (save auto-syncs to playback -- no separate "Sync" step)
* Timecode does **not** support MIDI CC slot switching (unlike Video and Lighting)
> *For more on the slot system:* [*Configuration Slots (A-E)*](/6.-configuration/configuration-slots)
***
## Timecode vs. MIDI Note Triggers
When timecode is actively driving playback, **manual MIDI note triggers are suppressed** on both the video and lighting channels. This prevents accidental clip changes during a synced show. The suppression is active whenever the MVP is receiving a timecode signal.
When the timecode signal stops (for more than 1 second), manual MIDI triggers resume automatically.
***
## Getting Started with Timecode
1. **Connect your timecode source** -- See [LTC Setup](/4.-timecode-setup/ltc-audio-timecode-setup) or [MTC Setup](/4.-timecode-setup/mtc-midi-timecode-setup)
2. **Verify signal** -- Check the Dashboard's Input Monitor for incoming timecode frames
3. **Build your timeline** -- Open the [Timeline Editor](/4.-timecode-setup/the-timeline-editor) and place clips
4. **Convert videos to All-Intra** -- Required for the timeline. See [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) or [export directly from your editing software](/4.-timecode-setup/exporting-all-intra-from-editing-software)
5. **Test** -- Play your timecode source and watch the MVP follow along
***
## Related Pages
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Build and edit your show timeline
* [LTC (Audio Timecode) Setup](/4.-timecode-setup/ltc-audio-timecode-setup) -- Hardware connection and signal verification
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- MIDI timecode and MMC transport control
* [All-Intra & Frame-Accurate Sync](/4.-timecode-setup/all-intra-videos) -- Why All-Intra is required and how conversion works
* [Exporting All-Intra from Editing Software](/4.-timecode-setup/exporting-all-intra-from-editing-software) -- Premiere, FCP, Resolve, Handbrake guides
# The Timeline Editor
The MVP includes a built-in NLE-style timeline for arranging video and lighting clips against a 24-hour SMPTE timecode range. This is where you build and edit your timecode-driven shows.
***
## Page Layout
The Timecode page is divided into several areas:
| Area | Location | Purpose |
| -------------------- | -------------- | ----------------------------------------------------------- |
| **Header** | Top | Slot selector, frame rate, edit mode |
| **Timeline Toolbar** | Above timeline | Save button, timecode status chips, SMPTE display |
| **Media Library** | Left column | Video and lighting clips available to place on the timeline |
| **Timeline** | Right column | Two-track editor with hour overview, ruler, and clip lanes |
| **Inspector** | Bottom strip | Properties and controls for the selected clip |
***
### Slot Selector (A-E)
Click the slot name in the header to expand the slot selector. Five independent timeline slots are listed. Click any slot to switch. **Timecode slot switches sync to playback immediately** -- there is no separate "Sync Changes" step.
If you have unsaved changes on the current slot, they are **saved automatically** before switching.
You can rename slots by clicking the pencil icon (up to 30 characters, letters, numbers, spaces, underscores, dashes, dots, parentheses, and ampersand).
### Frame Rate
Select the frame rate that matches your timecode source:
| Option | Value |
| -------------- | ----- |
| 24 fps | 24 |
| 25 fps | 25 |
| 29.97 fps (DF) | 29.97 |
| 30 fps | 30 |
If the incoming timecode frame rate doesn't match your selection, an amber **"Framerate Mismatch"** warning chip appears in the timeline toolbar.
### Edit Mode
Toggle **EDIT MODE** to enable timeline editing. When off, the timeline is read-only -- you can view and monitor but not make changes.
***
## Timeline Toolbar
#### Snap (Magnet) Toggle
The **magnet** icon in the header toggles magnetic snapping. When on, dragged clip edges and the playhead snap to nearby targets within \~8 px (zoom-independent):
1. Playhead
2. Other clip edges (both tracks)
3. Grid major ticks (the labeled ruler ticks)
4. Grid minor ticks (the unlabeled fine ticks)
5. Frame boundary -- always on, even when the magnet is off
The snap state is **persisted** across sessions. Press **S** to toggle from the keyboard, or hold **Alt** during a drag to temporarily bypass snap (the frame-floor remains in effect). When a snap engages during a drag, a colored guideline appears at the snap point.
#### Keyboard Shortcuts Cheat Sheet
The **keyboard** icon in the header opens an in-app reference of every shortcut. Press **?** or **F1** anywhere on the page to open the same dialog.
### Timecode Status
Real-time status indicators (only visible when timecode signal is present):
| Element | Meaning |
| ----------------------------------------------------- | ------------------------------------------------------ |
| **"ACTIVE . LTC"** or **"ACTIVE . MTC"** (green chip) | Timecode signal is being received, with source and FPS |
| **Framerate Mismatch** (red pulsing chip) | Detected FPS differs from your configured FPS |
| **Speed** (e.g., "1.000x") | Playback rate of the timecode source |
### SMPTE Timecode Display
A large **HH:MM:SS:FF** display in 7-segment LCD style (DSEG7 font) with a ghost-digit effect (classic LED clock appearance). Shows the current playhead position in real time.
### Save Changes Button
Click **SAVE CHANGES** to persist your timeline arrangement to the device. This button only appears when you have unsaved edits. Saving automatically syncs the configuration to the playback engine.
If you navigate away with unsaved edits, you'll be prompted to **Save & Leave** or **Discard & Leave**.
***
## Media Library
The left column lists all available Videos and DMX Clips that can be placed on the timeline, in two collapsible sections.
### Videos
Each video shows:
* **Thumbnail**
* **Filename**
* **Duration**
* **All-Intra badge**:
* Green checkmark: All-Intra encoded (ready for timeline use)
* Amber warning: Not All-Intra (conversion will be required when placed on the timeline)
* Image icon: Still image (no conversion needed)
Click a video file to view its detailed info in the Video Info Dialog.
### Lighting Clips
Each DMX clip shows:
* **Clip name**
* **Duration**
* **DMX badge** (amber gradient thumbnail)
* A fixed **BLACKOUT** entry is always listed first (sets all channels to zero)
### Adding Clips to the Timeline
**Drag** a file from the Media Library and **drop** it onto the appropriate track lane (Video or Lighting). The clip will be placed at the drop position. Dragging requires Edit Mode to be enabled.
* If you drop onto an existing clip, the new clip is placed before or after it based on your drop position.
* Clips cannot overlap on the same track.
* **Video clips require All-Intra encoding.** When you drop a non-All-Intra video, the MVP will prompt you to convert it. If you cancel the conversion, the clip is removed from the timeline. See [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) for details.
* All-Intra video clips that have not been analyzed yet will prompt for a quick video analysis (10-20 seconds). Cancelling removes the clip.
***
## Timeline Editor
### Hour Overview Bar
The bar at the top spans the full 24-hour range (hours 00-23). It serves as both a navigation tool and a minimap:
* **Minimap**: Tiny colored bars within each hour cell show where clips exist (blue = video, amber = lighting).
* **Viewport rectangle**: Shows which portion of the 24-hour range is currently visible.
* **Drag** the rectangle body to pan the view.
* **Drag the left or right edge** to zoom in or out.
* **Click** an hour cell to jump the view to that hour (default 1-hour viewport width).
### SMPTE Ruler
The ruler displays timecode labels that adapt to your zoom level. Tick intervals follow SMPTE-friendly values.
A **red playhead line** on the ruler shows the current timecode position.
### Track Lanes
Two horizontal tracks:
| Track | Color |
| ------------ | ----- |
| **VIDEO** | Blue |
| **LIGHTING** | Amber |
### Clips on the Timeline
Each clip appears as a colored block:
* **Label bar** (top): Clip name and duration. Video clips that are not All-Intra show an amber warning icon with tooltip.
* **Thumbnail** (video) or **DMX badge** (lighting): Visual identifier below the label.
* **Trim indicators** (bottom corners): Show trim-start and trim-end amounts when the clip has been trimmed.
* **Resize handles**: Left and right edge handles for trimming appear on hover or when selected.
* **Selection highlight**: Selected clip gets a white border.
#### Timeline Interactions
All editing requires **Edit Mode** to be enabled.
| Action | How |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Add a clip** | Drag from the Media Library onto a track |
| **Select a clip** | Click it (populates the Inspector) |
| **Move a clip** | Drag horizontally |
| **Nudge a clip** | Arrow keys: **←/→** = 1 frame, **Shift+←/→** = grid minor step, **Ctrl/Cmd+←/→** = grid major step |
| **Duplicate a clip** | **Ctrl/Cmd+D**, or click **Duplicate** in the Inspector. The copy is placed flush after the original, so repeated presses chain into a seamless loop. |
| **Trim clip start** | Drag the left edge handle, or type / scroll on the Trim Start field in the Inspector |
| **Trim clip end** | Drag the right edge handle, or type / scroll on the Trim End field in the Inspector |
| **Remove a clip** | Select it and press **Delete** or **Backspace**, or click "Remove Clip" in the Inspector |
| **Deselect** | Click empty space on the timeline, or press **Escape** |
| **Pan the view** | Mouse wheel, two-finger trackpad scroll, or click-and-drag empty space |
| **Zoom** | **Ctrl/Cmd/Shift + wheel** on a mouse, or **pinch** on a trackpad. Anchored at cursor. Range: 1 s -- 24 h. |
| **Scrub** | Hover to see a white line with SMPTE position |
| **Toggle snap** | **S** (or click the magnet icon in the header) |
| **Bypass snap** | Hold **Alt** while dragging |
| **Open shortcuts** | **?** or **F1** (also a keyboard icon in the header) |
All positions are snapped to the nearest SMPTE frame boundary. While dragging a clip, a tooltip at the leading edge shows the SMPTE start time, and any active snap target is highlighted with a colored guideline.
> The wheel/trackpad mapping mirrors industry standards (Premiere, Resolve, Final Cut, Logic, Reaper). On a notched mouse, plain wheel = pan, modified wheel = zoom. On a trackpad, two-finger scroll = pan, pinch = zoom -- exactly as in any modern NLE/DAW.
***
## Inspector
The Inspector appears below the timeline when a clip is selected.
### Empty State
When no clip is selected: *"Select a clip on the timeline."*
### Clip Selected
**Row 1 -- Identity:**
* Clip name
* Track type (Video or Lighting)
* Full file duration in SMPTE format
* **Duplicate** button (primary, requires Edit Mode) -- places a copy flush after the original
* **Remove Clip** button (red, requires Edit Mode)
**Row 2 -- Timing:**
* **Start Position**: Editable SMPTE field -- see Editing Timecode Fields below
* **Duration**: Read-only (calculated from start to end)
* **End Position**: Read-only
**Row 3 -- Trimming:**
* **Trim Start**: Editable SMPTE field showing the file offset. Type a value, scroll, or use the same smart-parser shortcuts.
* **Trim End**: Editable SMPTE field showing the end trim. Same conventions as Trim Start.
* A **"Trimmed"** chip (amber, with scissors icon) appears when either trim value is greater than zero.
**Editing Timecode Fields**
All three SMPTE fields (Start Position, Trim Start, Trim End) follow the same professional NLE/DAW conventions:
* **Click** the field -- the entire value is selected; your first keystroke replaces it.
* **Enter** or **Tab** commits your typed value. **Esc** cancels and reverts.
* If the value is invalid (parse error, out of range, or it would collide with another clip), the field flashes red briefly and reverts -- no modal interruption.
* Mouse wheel still nudges by one frame per click. Trackpad two-finger scroll nudges smoothly (one frame per \~50 px).
The smart parser accepts several formats:
| You type | Interpreted as |
| ------------- | -------------------------------------------------------- |
| `01:23:45:10` | Full SMPTE -- 1 h 23 m 45 s 10 f |
| `5:00` | 5 seconds, 0 frames (rightmost group is always frames) |
| `:15` | 15 frames |
| `5300` | `00:00:53:00` (digits right-fill into HH:MM:SS:FF pairs) |
| `+1:00` | Advance the current value by 1 second |
| `-:15` | Retreat the current value by 15 frames |
Values are always quantised to the nearest frame boundary on commit.
### All-Intra Status (Video Clips Only)
An additional row for video clips shows the encoding status. All-Intra is **required** for the timeline -- non-All-Intra clips must be converted before they can be used for timecode playback.
| Status | Display | Action |
| ---------------------------- | ------------------------------------------------------ | ---------------------------------------- |
| **All-Intra** | Green chip: "Frame-accurate seeking enabled" | None needed |
| **Not All-Intra** | Amber chip: "Convert for frame-accurate timecode sync" | **"Convert to All-Intra"** button |
| **Converted version exists** | Amber chip + "Already converted" | **"Switch to All-Intra"** button (green) |
| **Conversion in progress** | Progress circular with percentage | Wait for completion |
| **Queued** | "Queued for All-Intra Conversion" | Wait |
| **Analyzing** | Spinner: "Analyzing Video..." | One-time video analysis in progress |
A help button opens the All-Intra explanation dialog.
> *For details on All-Intra encoding and the conversion process:* [*All-Intra Video & Timecode Sync*](/4.-timecode-setup/all-intra-videos)
***
## Timeline Playback Behavior
When timecode is active, the timeline responds in real time:
* The **red playhead** tracks the incoming timecode position, auto-scrolling the viewport to keep it in view
* The **timecode status chips** update to show signal state, source, FPS, and speed
* If timecode enters a clip range, the MVP plays that clip
* If timecode leaves all clip ranges, video goes to blackout and lighting holds its last state
* If the timecode source changes speed (e.g., CDJ pitch), the MVP adjusts its playback rate to keep perfect sync
***
## Video Analysis
If your videos are already All-Intra, when you first place the video clip on the timeline, the MVP prompts you to run a **one-time video analysis**. This ensures frame-accurate playback with timecode.
* Takes approximately 10-20 seconds per file
* Video playback is temporarily disabled during analysis
* Only happens once per file
* If you cancel, the clip is removed from the timeline
* If analysis fails, the clip is removed and a notification prompts you to try again
***
## Tips
* **All videos must be All-Intra** for the timeline. Convert before uploading for the fastest workflow, especially for 4K content. See [Exporting All-Intra from Editing Software](/4.-timecode-setup/exporting-all-intra-from-editing-software).
* **Use the Hour Overview** to quickly navigate a long show timeline instead of scrolling manually.
* **Mouse wheel on timing fields** in the Inspector is the fastest way to make fine adjustments (one frame per scroll tick).
* **Timecode saves auto-sync** -- unlike Video and Lighting pages, there is no separate "Sync Changes to Playback" step.
* **Save frequently** -- the navigation guard will catch you if you forget, but it's good practice.
* **Loop a clip the fast way**: select it and press **Ctrl/Cmd+D** repeatedly. Each press appends another copy flush against the previous one -- ideal for hold frames and repeated DMX cues.
* **Type, don't drag, for precision**: click any timecode field in the Inspector, type `+:15` to nudge forward 15 frames, or `1:00:00:00` to jump to exactly one hour.
* **Hold Alt while dragging** to temporarily bypass snap when you need to land between snap targets.
* **Press ?** any time to see every keyboard shortcut without leaving the page.
***
## Related Pages
* [Timecode Overview](/4.-timecode-setup/timecode-overview) -- Understanding LTC, MTC, and sync capabilities
* [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- Why All-Intra is required and how conversion works
* [Exporting All-Intra from Editing Software](/4.-timecode-setup/exporting-all-intra-from-editing-software) -- Premiere, FCP, Resolve, Handbrake guides
* [LTC (Audio Timecode) Setup](/4.-timecode-setup/ltc-audio-timecode-setup) -- Hardware setup for audio timecode
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- MIDI timecode and transport control
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots) -- Multi-slot system explained
# All Intra Videos
The MVP can convert your videos to All Intra video files. All-Intra encoding is **required** for video clips on the timecode timeline. This page explains why and how.
***
## Why All-Intra Is Required
### The Problem with Standard Video
When the MVP receives a timecode position (e.g., 00:05:23:15), it needs to seek the video file to exactly that frame. With standard video encoding:
* The video is divided into **Groups of Pictures (GOP)**, typically 12-250 frames apart
* Only the first frame in each group (I-frame/keyframe) is a complete image
* The frames in between store only the *differences* from the previous frame (P-frames and B-frames)
This means seeking is slow and inaccurate -- making reliable timecode sync impossible.
### The Solution: Every Frame Is an I-Frame
With All-Intra (GOP=1), **every single frame is a complete image**. The decoder can jump directly to any frame with no reconstruction:
* Seeking is instant and frame-accurate
* The MVP maintains frame-accurate sync throughout your show
***
## What Happens When You Place a Video on the Timeline
When you drag a video file onto the timeline, the MVP checks its encoding and follows one of these paths:
### Already All-Intra (ready to use)
The clip is added to the timeline silently. No dialogs, no conversion needed.
### Already All-Intra (needs analysis)
A **"Video Analysis Required"** dialog appears. The MVP needs to perform a one-time video analysis for this file:
* Takes approximately 10-20 seconds
* Video playback is temporarily disabled during measurement
* Only happens once per file
* Click **"Analyze Now"** to proceed, or **"Cancel"** to remove the clip from the timeline
If analysis fails, the clip is automatically removed and you'll see a notification to try again.
### Not All-Intra (converted version already exists)
If you previously converted this file (creating a `-All-Intra.mkv`), the clip is **automatically switched** to the All-Intra version. An informational dialog confirms the switch -- no action needed from you.
### Not All-Intra (no converted version)
A **conversion confirmation dialog** appears:
1. A new All-Intra file will be created alongside the original
2. Video playback is disabled during conversion (the hardware encoder shares the video decoder)
3. A performance measurement runs automatically after conversion completes
4. An **Advanced Settings** section provides optional controls for Conversion Quality (Very High, Ultra, Maximum Bitrate) and, for 4K files, Output Resolution (see below)
5. Click **"Proceed"** to start conversion, or **"Cancel"** to **remove the clip from the timeline**
**4K Files — Output Resolution & Effects Mode**
If the source video is **4K (width ≥ 3840 pixels)**, an **Output Resolution** option appears inside Advanced Settings:
| Option | Effect |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Match Source (4K)** *(default)* | Converts at full 4K resolution. [Effects Mode](/2.-video-setup/effects-mode) is not available for 4K All-Intra files. |
| **Convert to 1080p** | Downscales during conversion. Required for Effects Mode compatability. |
When the device is configured for **Effects Mode (Fast Trigger)**, the dialog also shows an inline note: *"4K files do not support effects mode."* In other video modes this note is hidden, but the Output Resolution option remains available in Advanced Settings.
> *For step-by-step export guides:* [*Exporting All-Intra from Editing Software*](/4.-timecode-setup/exporting-all-intra-from-editing-software)
***
## Converting on the MVP
### How On-Device Conversion Works
The MVP uses its built-in hardware video processor to convert videos:
* **Input**: Your original video file (any supported codec/container)
* **Output**: `-All-Intra.mkv` (H.265, GOP=1, Matroska container)
### During Conversion
* **Video playback is disabled** -- the hardware video processor is shared between playback and encoding
* Progress is shown in the Inspector when the converting clip is selected (amber chip with percentage)
* A **Conversion Queue Widget** in the bottom-right corner shows overall progress
### After Conversion
1. The timeline clip is automatically updated to use the new All-Intra file
2. A quick video analysis runs automatically (10-20 seconds)
3. Video playback is re-enabled
4. The original file remains on the device -- you can delete it manually to free storage space
### Cancelling a Conversion
If you cancel a conversion that is already in progress, all clips on the timeline referencing that non-All-Intra file are automatically removed.
***
## Exporting All-Intra from Your Editing Software (Recommended)
For faster results, export your videos with **GOP=1** directly from your editing software **before** uploading to the MVP. This is especially important for 4K content, where on-device conversion is very slow.
The key setting to look for in your export settings:
* **GOP Size** = 1, or **Keyframe Interval** = 1
* Some software calls this **"All-Intra"** or **"Intra-only"**
* **H.265 (HEVC)** is recommended for smaller file sizes
> *Step-by-step guides for Adobe Premiere Pro, Final Cut Pro, DaVinci Resolve, and Handbrake:* [*Exporting All-Intra from Editing Software*](/4.-timecode-setup/exporting-all-intra-from-editing-software)
***
## Checking All-Intra Status
You can check whether a video is All-Intra encoded in several places:
| Location | All-Intra | Not All-Intra | Still Image |
| -------------------------- | -------------------------------------------- | ---------------------------------- | ----------- |
| **Timeline Media Library** | Green checkmark badge | Amber warning badge | No badge |
| **Timeline Inspector** | Green chip: "Frame-accurate seeking enabled" | Amber chip with conversion options | N/A |
| **Video Info Dialog** | "ALL INTRA" badge | No badge | Image icon |
***
## Frame-Accurate Playback
All-Intra encoding allows the MVP to deliver frame-accurate playback at any point on your timeline. The MVP automatically handles synchronization and speed matching. You just build your timeline and let the MVP do the rest.
***
### File Size Considerations
All-Intra files are **2-5x larger** than standard encoding because every frame is stored as a complete image. File size depends on your output resolution and the Conversion Quality setting chosen in Advanced Settings.
**1080p Output** *(native 1080p files, or 4K downscaled to 1080p)*
| Quality | Est. file size (3 min) |
| --------------------- | ---------------------- |
| Very High *(default)* | \~110–180 MB |
| Ultra | \~145–235 MB |
| Maximum Bitrate | \~180–360 MB |
**4K Output** *(4K files converted at full resolution)*
| Quality | Est. file size (3 min) |
| --------------------- | ---------------------- |
| Very High *(default)* | \~400–650 MB |
| Ultra | \~520–845 MB |
| Maximum Bitrate | \~640–1,300 MB |
The MVP has 100GB of storage. Plan your storage accordingly when using All-Intra files.
***
## Related Pages
* [Exporting All-Intra from Editing Software](/4.-timecode-setup/exporting-all-intra-from-editing-software) -- Premiere, FCP, Resolve, Handbrake guides
* [Timecode Overview](/4.-timecode-setup/timecode-overview) -- Understanding the timecode system
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Building your show timeline
* [Supported File Formats](/8.-reference/supported-video-formats) -- All format details
# MTC (MIDI Timecode) Setup
MIDI Timecode (MTC) allows you to synchronize the MVP's video and lighting playback to your DAW or show controller using timecode sent over a MIDI connection. MTC also supports **MIDI Machine Control (MMC)** for transport commands like Stop, Play, and Locate.
***
## Connection Options
MTC can be received on **any** of the MVP's MIDI inputs:
| Input | Connection |
| --------------------------- | ---------------------------------------- |
| **USB MIDI** | USB-C cable to your computer's HOST port |
| **5-Pin DIN** | Standard MIDI cable to the DIN input |
| **Network MIDI (RTP-MIDI)** | Wi-Fi or Ethernet |
> *For Network MIDI setup:* [*Network MIDI (RTP-MIDI) Setup*](/5.-triggering/network-midi-rtp-midi-setup)
***
## How MTC Works
MTC sends continuous timecode data over your MIDI connection, updating the MVP with the current position multiple times per frame.
## DAW Setup
### Enabling MTC Output
Most DAWs can send MTC from their MIDI output. The general steps are:
1. Connect the MVP to your computer via USB-C (or configure [Network MIDI](file:///5753738/5.-Triggering/network-midi.md)).
2. In your DAW's **MIDI/Sync preferences**, enable **MTC Output** (also called "MIDI Timecode Send" or "Transmit MTC").
3. Set the MTC output destination to **MVP**.
4. Set the frame rate to match the rate configured in your [Timeline Editor](broken://pages/597844c56c819fdda457ac916bcc2ea08dd6dd12).
#### Ableton Live (requires LiveMTC)
1. Open **Preferences** > **Link Tempo MIDI**.
2. In the **MIDI Ports** section, find the **MVP** output.
3. Enable **Sync** for the MVP output.
4. Install and configure LiveMTC according to it's documentation.
5. Ableton will now send MTC to the MVP during playback.
> **Note**: Ableton does not natively send MMC. MTC alone is sufficient -- the MVP detects transport start/stop from the timecode stream.
#### Pro Tools
1. Open **Setup** > **Peripherals** > **Synchronization**.
2. Enable MTC output and choose the **MVP**.
3. Set the frame rate to match your session and the MVP's timeline configuration.
> **Note**: Pro Tools does not send MMC Play after a Locate. The MVP handles this by automatically resuming when MTC quarter-frame messages resume.
#### Logic Pro
1. Open **File** > **Project Settings** > **Synchronization**.
2. Under **MIDI**, enable **Transmit MTC**.
3. Set the output to **MVP**.
4. Configure the frame rate to match the MVP's timeline configuration.
#### Other DAWs
Look for settings labeled:
* "MIDI Timecode" or "MTC"
* "Sync Output" or "Transmit Timecode"
* "External Sync" or "MIDI Clock"
Enable MTC output and route it to the **MVP** device.
***
## Enabling MMC (MIDI Machine Control)
MMC extends MTC with transport commands. When enabled in your DAW, it provides direct control over the MVP's playback state:
| MMC Command | Effect on MVP |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Stop** | Freezes video on the current frame, lighting holds last state |
| **Play** | Resumes playback from the current position (or from a pending Locate position) |
| **Pause** | Same as Stop -- freezes current state |
| **Locate / GoTo** | Seeks video and lighting to a specific timecode position. When stopped, pre-positions for the next Play. When playing, repositions without pausing. |
### DAW MMC Setup
MMC is typically enabled alongside MTC in the same sync/MIDI preferences:
* **Ableton Live**: Does not natively send MMC. MTC alone is sufficient -- the MVP detects transport state from the timecode stream.
* **Pro Tools**: Enable MMC output in **Setup** > **Peripherals** > **Synchronization** > **Machine Control**.
* **Logic Pro**: Enable in **File** > **Project Settings** > **Synchronization** > **MIDI** > **Transmit MMC**.
> **Note**: MMC is optional. The MVP can sync using MTC alone -- it detects transport start/stop from the timecode stream. MMC adds the ability to explicitly pause and seek from your DAW, which is particularly useful during rehearsal and soundcheck.
***
## Signal Verification
Once your DAW is configured:
1. Navigate to the MVP **Dashboard**.
2. Start playback in your DAW.
3. Check the **Input Monitor** section -- you should see MTC frame events appearing in the event log.
4. The timecode status area should show:
* **Active** (green) with **MTC** source indicator
* Detected **FPS**
* Detected **Playback Rate**
* Running **SMPTE timecode display**
If you don't see this while your DAW is playing:
* Verify the MVP is selected as the MTC output in your DAW
* Check that MTC/Sync is enabled (not just MIDI note output)
* Try a different MIDI input method (USB vs. Network)
***
## MTC vs. LTC
| | MTC | LTC |
| --------------------- | ------------------------------------------------------------------- | -------------------------------------------- |
| **Connection** | MIDI (USB, DIN, or Network) | 3.5mm audio input |
| **Transport Control** | Yes (via MMC: Stop, Play, Locate) | No |
| **Scrub/Locate** | Yes (via MMC Locate or Full Frame SysEx) | No |
| **Wireless Option** | Yes (via RTP-MIDI) | No |
| **Signal Monitoring** | Dashboard MIDI event log | Dashboard LTC Volume + Frames Decoded meters |
| **Hardware Required** | MIDI interface (or USB-C cable) | Audio cable |
| **Simultaneous Use** | Yes -- both always active; whichever signal arrives drives playback | |
***
## Frame Rate Configuration
The frame rate must match between your DAW and the MVP:
1. In your DAW, check the project frame rate (usually in sync or timecode settings).
2. In the MVP's [Timeline Editor](/4.-timecode-setup/the-timeline-editor), set the **Frame Rate** dropdown to the same value.
3. If there's a mismatch, the MVP will show an amber **"Framerate Mismatch"** warning.
Supported frame rates: **24**, **25**, **29.97 (Drop Frame)**, **30** fps.
MTC encodes the frame rate in its rate bits, so the MVP can detect the source's frame rate. The configured rate is still used for all internal timing calculations.
***
## Tips
* **Test with a simple timeline first**: Place a single clip starting at 00:00:00:00 and verify that it plays when you hit Play in your DAW.
* **MTC over Network MIDI** works great for timecode delivery. See [Network MIDI Setup](/5.-triggering/network-midi-rtp-midi-setup) for configuration.
***
## Related Pages
* [Timecode Overview](/4.-timecode-setup/timecode-overview) -- LTC vs. MTC comparison and sync capabilities
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Building your timecode show
* [LTC (Audio Timecode) Setup](/4.-timecode-setup/ltc-audio-timecode-setup) -- Alternative audio-based timecode input
* [Network MIDI (RTP-MIDI) Setup](file:///5753738/5.-Triggering/network-midi.md) -- Wireless MTC delivery
* [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- Frame-accurate seeking for timecode
# LTC (Audio Timecode) Setup
LTC (Linear Timecode) allows you to synchronize the MVP's video and lighting playback using a SMPTE timecode signal sent over an audio connection.
***
## Hardware Connection
Connect your timecode source to the **3.5mm (1/8") audio input** on the rear of the MVP using a standard audio cable.
**Common LTC sources:**
* DAW audio output (dedicated timecode track)
* Click track with embedded LTC
* Dedicated LTC/SMPTE generator
***
## Signal Verification
Before building your timeline, verify the MVP is receiving a clean LTC signal.
1. Start playback on your LTC source.
2. Navigate to the MVP **Dashboard**.
3. Check the **Input Monitor** section (LTC meters only appear when LTC signal is detected):
### What to Look For
| Indicator | Healthy Signal | Problem |
| -------------------- | ----------------------------------------- | ---------------------------------------------------- |
| **LTC Volume** | Green bar, moderate level (-20dB to -1dB) | Orange = too quiet; Red = clipping; "--" = no signal |
| **Frames Decoded** | Green bar, 100% | Orange/red = increasing frame loss |
| **Timecode Display** | Numbers running smoothly (HH:MM:SS:FF) | Frozen or jumping = adjust volume |
### Adjusting Signal Level
If the timecode is frozen, erratic, or not appearing:
* **Too quiet**: Increase the output volume on your source device. Levels below -40dB are treated as no signal.
* **Too loud (clipping)**: Decrease the output volume. Levels above -1dB indicate clipping.
* **Just right**: The LTC Volume meter shows green with consistent moderate activity and the timecode counter runs smoothly.
The sweet spot varies by source, but aim for a signal in the -20dB to -1dB range.
***
## Frame Rate Detection
The MVP detects the incoming LTC frame rate automatically.
***
## Using LTC with the Timeline Editor
Once your signal is verified, you're ready to build your show in the [Timeline Editor](/4.-timecode-setup/the-timeline-editor):
1. Navigate to the **Timecode** page
2. Set the **Frame Rate** to match your LTC source (24, 25, 29.97, or 30 fps)
3. Place video and lighting clips on the timeline at the desired timecode positions
4. Start your LTC source -- the MVP will follow the timecode and play clips at the correct positions
***
## LTC Signal States
The MVP's timecode engine tracks the LTC signal through four states:
| State | Dashboard Shows | What Happens |
| ---------------------- | ------------------------------------- | ---------------------------------------------- |
| **No Signal** | Inactive (gray) | Idle, waiting for timecode |
| **Active** | Active (green), running SMPTE display | Video/lighting playback driven by timecode |
| **Signal Interrupted** | Active, timecode continues | Playback continues smoothly on internal timing |
| **Signal Lost** | Inactive, playback stops | Video goes to black, lighting holds last state |
When the signal returns after being lost, the MVP resumes sync.
***
## Important Notes About LTC
* **Continuous sync**: The MVP uses LTC for **full continuous synchronization** -- the timecode position drives the playback position on the timeline at all times. This is not a one-time trigger.
* **Variable speed**: The MVP can follow LTC sources playing at 50% to 200% of normal speed. If your source runs slightly fast or slow, the MVP detects the rate and adjusts playback to match.
* **LTC and MTC are both active**: Both inputs are always listening. Whichever signal arrives drives playback -- there is no priority between them.
***
## Related Pages
* [Timecode Overview](/4.-timecode-setup/timecode-overview) -- LTC vs. MTC comparison and capabilities
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Building your show timeline
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- Alternative MIDI-based timecode
* [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- Frame-accurate seeking
# Exporting All-Intra from Editing Software
This page provides instructions for exporting your videos with **All-Intra (GOP=1)** encoding from popular editing software. All-Intra is required for videos used on the MVP's timecode timeline.
We recommend **H.265 (HEVC)** for All-Intra exports -- it produces significantly smaller files than H.264 at the same quality, which matters because All-Intra files are larger than standard encoding.
***
## Adobe Premiere Pro
1. Select your sequence and go to **File > Export > Media** (or press Ctrl+M / Cmd+M).
2. In the Export Settings dialog:
| Setting | Value |
| ---------- | ------------ |
| **Format** | H.265 (HEVC) |
| **Preset** | Custom |
3. Scroll down to the **Video** tab and find the **GOP Settings** section (under the codec settings):
| Setting | Value |
| --------------------- | ----- |
| **Keyframe Interval** | 1 |
This sets GOP=1, making every frame an I-frame.
4. Set your desired resolution and bitrate:
| Setting | Recommendation |
| -------------------- | ---------------------------------------- |
| **Resolution** | Match your source (1080p or 4K) |
| **Bitrate Encoding** | VBR, 1 Pass |
| **Target Bitrate** | 30-50 Mbps for 1080p, 80-120 Mbps for 4K |
5. Under the **Video** tab, confirm **Profile** is set to **Main** or **Main 10**.
6. Click **Export**.
\[SCREENSHOT: Premiere Pro Export Settings showing H.265 format with Keyframe Interval set to 1]
> **Tip**: You can save this as a custom preset ("MVP All-Intra") to reuse for future exports.
***
## Final Cut Pro
1. Select your project in the browser or timeline.
2. Go to **File > Share > Master File** (or use a custom destination).
3. Click **Settings** to open the export settings.
4. Choose the **Video codec**:
| Setting | Value |
| --------------- | ----- |
| **Video codec** | H.265 |
5. Final Cut Pro does not expose a direct "GOP Size" setting in the standard Share dialog. To set GOP=1, use **Compressor** (Apple's companion app):
* Send to Compressor: **File > Send to Compressor**
* In Compressor, create a custom setting based on the H.265 codec
* Under **Video Properties > Key Frame Interval**, set to **1**
* Start the export
\[SCREENSHOT: Compressor showing H.265 setting with Key Frame Interval set to 1]
**Alternative**: If you don't have Compressor, export from Final Cut Pro as **Apple ProRes**, then convert to H.265 All-Intra using **Handbrake** (see below).
***
## DaVinci Resolve
1. Switch to the **Deliver** page (bottom nav bar).
2. Create a new render job or use a custom preset.
3. Configure the video settings:
| Setting | Value |
| ----------- | ----------------------------------------- |
| **Format** | MKV or MP4 |
| **Codec** | H.265 |
| **Encoder** | Native or NVIDIA (hardware, if available) |
4. Find the **Key Frame** setting under the advanced codec options:
| Setting | Value |
| -------------- | ---------- |
| **Key Frames** | All Frames |
If there is no "All Frames" option, look for a **Keyframe Interval** or **GOP Length** field and set it to **1**.
5. Set your quality:
| Setting | Recommendation |
| -------------- | --------------------------------------------------------- |
| **Quality** | Best or Restrict to 30-50 Mbps (1080p) / 80-120 Mbps (4K) |
| **Resolution** | Match your timeline resolution |
6. Click **Add to Render Queue**, then **Start Render**.
\[SCREENSHOT: DaVinci Resolve Deliver page showing H.265 codec with Key Frames set to All Frames]
***
## Handbrake (Free, Cross-Platform)
[Handbrake](https://handbrake.fr/) is a free, open-source video converter available for Windows, Mac, and Linux. Use it to convert existing videos to All-Intra format.
1. **Open** Handbrake and drag your video file onto the window (or use **File > Open Source**).
2. Under the **Summary** tab, set the output format:
| Setting | Value |
| ---------- | ---------- |
| **Format** | MKV or MP4 |
3. Switch to the **Video** tab and configure:
| Setting | Value |
| -------------------- | ---------------------------------------------- |
| **Video Codec** | H.265 (x265) |
| **Framerate** | Same as source |
| **Constant Quality** | RF 18-22 (lower = higher quality, larger file) |
4. Open the **Additional Options** field (at the bottom of the Video tab) and type:
```
keyint=1
```
This sets the keyframe interval to 1 frame (All-Intra). The full string in the options field should include `keyint=1`. If there are other options already present, add it with a colon separator: `existing-option:keyint=1`.
5. Click **Start Encode**.
\[SCREENSHOT: Handbrake Video tab showing H.265 codec with keyint=1 in the Additional Options field]
> **Tip**: For the fastest conversion on PC, check if your system has hardware encoding support. On the Video tab, you may see **H.265 (NVENC)** (NVIDIA), **H.265 (QSV)** (Intel), or **H.265 (VCE)** (AMD) options. These are significantly faster than the software x265 encoder.
***
## Verifying Your Export
After exporting, you can verify the file is All-Intra before uploading to the MVP:
### Using Handbrake
Open the file in Handbrake -- the **Summary** tab shows the keyframe interval.
### On the MVP
Upload the file and place it on the timeline. If it's All-Intra, it will be added without a conversion prompt. The Media Library shows a **green checkmark** badge next to All-Intra files.
***
## Quick Reference
| Software | Codec Setting | Key Setting | GOP/Keyframe Value |
| ------------------------------ | ------------- | ------------------ | ---------------------------- |
| **Premiere Pro** | H.265 (HEVC) | Keyframe Interval | 1 |
| **Final Cut Pro + Compressor** | H.265 | Key Frame Interval | 1 |
| **DaVinci Resolve** | H.265 | Key Frames | All Frames (or interval = 1) |
| **Handbrake** | H.265 (x265) | Additional Options | `keyint=1` |
***
## Related Pages
* [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- Why All-Intra is required for timecode playback
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Building your timecode show
* [Supported File Formats](/8.-reference/supported-video-formats) -- All supported codecs and containers
# 5. Triggering
The MVP supports multiple ways to trigger video and lighting clips — MIDI notes, MIDI CC, USB keyboards, DAW software, network MIDI, and hardware controllers. All methods can be used simultaneously; the last trigger received wins.
Start with the Triggering Overview for a comparison of all methods.
***
#### In This Section
* [**Triggering Overview**](/5.-triggering/triggering-overview) — All trigger methods at a glance
* [**DAW / Computer Triggering** ](/5.-triggering/daw-computer-triggering)— Ableton Live, Pro Tools, Logic Pro, and general DAW setup
* [**Network MIDI (RTP-MIDI) Setup**](/5.-triggering/network-midi-rtp-midi-setup) — Trigger wirelessly over your local network
* [**Hardware Controllers**](/5.-triggering/hardware-controllers) — Physical MIDI controllers via USB-A or 5-pin DIN
* [**USB Keyboards (HID)**](/5.-triggering/usb-keyboards-hid) — Trigger up to 36 clips from a standard keyboard
* [**MIDI CC Trigger Mode**](/5.-triggering/midi-cc-trigger-mode) — Trigger clips using MIDI CC #110 values
* [**MIDI Transport (Prev / Next)**](/5.-triggering/midi-transport-prev-next) — Step through the active slot with Notes 101/102
# 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 |
| **Note 101** | **Previous** -- step back to the previous non-empty assignment in the active slot |
| **Note 102** | **Next** -- step forward to the next non-empty assignment in the active slot |
**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) *|* [*Pro Tools*](/5.-triggering/daw-computer-triggering/pro-tools-setup) *|* [*Logic Pro*](/5.-triggering/daw-computer-triggering/logic-pro-setup) *|* [*Other DAWs*](/5.-triggering/daw-computer-triggering/other-daws-general-guide)
***
## MIDI Transport (Prev / Next)
Two hardcoded notes step through the assignments in the currently active configuration slot.
* **Note 101** = Previous, **Note 102** = Next
* Sent on the **video channel** they step video; on the **lighting channel** they step lighting
* Empty assignments are skipped; stepping wraps within the active slot and never crosses into another slot
* Debounced at 300 ms per direction to absorb double-triggers from hardware pads
* Always active -- there is nothing to enable
> *Details:* [*MIDI Transport (Prev / Next)*](/5.-triggering/midi-transport-prev-next)
***
## MIDI CC Trigger Mode
An alternative to note triggering is using Control Change messages.
* Uses **CC #110**
* Values 1-99 = trigger clip, value 100 = blackout
* Must be enabled in [System Settings](/6.-configuration/system-settings)
> *Details:* [*MIDI CC Trigger Mode*](/5.-triggering/midi-cc-trigger-mode)
***
## 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)
***
## 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) *|* [*Timeline Editor*](/4.-timecode-setup/the-timeline-editor)
***
## 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)
***
## 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)
***
## 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
**Scenario B: Lighting Playback Only**
* Signal Chain: Computer → MVP → Ethernet → ArtNet Node → DMX Fixtures
**Scenario C: Video + Lighting Playback**
* Signal Chain: Computer → MVP → HDMI & Ethernet
### Scenario D: Standalone (No Computer)
* Signal Chain: MIDI Controller → MVP → HDMI & Ethernet
***
## 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
* **Autoplay is not a trigger method** -- when enabled it advances at the end of each clip, and manual triggers (including Prev/Next) simply move the playhead without switching it off. See [Autoplay](/6.-configuration/autoplay).
***
## 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)
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign video clips
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign DMX clips
* [MIDI Reference](/8.-reference/midi-reference) -- Complete CC and note reference card
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard) -- Monitor triggers in real time
* [MIDI Transport (Prev / Next)](/5.-triggering/midi-transport-prev-next) -- Notes 101/102 step through the active slot
* [Autoplay](/6.-configuration/autoplay) -- Automatic advance at end of clip
# DAW / Computer Triggering
Step-by-step setup guides for triggering MVP clips from your DAW. Connect the MVP to your computer via USB-C, configure MIDI output in your DAW, and send notes on the appropriate channel.
***
#### In This Section
* [**Ableton Live Setup**](/5.-triggering/daw-computer-triggering/ableton-live-setup)
* [**Pro Tools Setup**](/5.-triggering/daw-computer-triggering/pro-tools-setup)
* [**Logic Pro Setup**](/5.-triggering/daw-computer-triggering/logic-pro-setup)
* [**Other DAWs (General Guide)**](/5.-triggering/daw-computer-triggering/other-daws-general-guide)
# Ableton Live Setup
This guide covers sending MIDI notes from Ableton Live to the MVP to trigger video and lighting clips.
> *This guide assumes basic familiarity with Ableton Live. For general instruction, see the* [*Official Ableton Live Manual*](https://www.ableton.com/en/manual/welcome-to-live/)*.*
***
## 1. Configure MIDI Preferences
1. Connect the MVP's **HOST** port to your computer via USB-C.
2. Open Ableton Live.
3. Open **Preferences** (macOS: `Live > Settings...` | Windows: `Options > Preferences`).
4. Navigate to the **Link Tempo MIDI** tab.
5. Scroll down to the **MIDI Ports** section.
6. Locate Output: **MVP**.
7. Enable the **Track** checkbox (this allows MIDI notes from your tracks to reach the MVP).
> **For timecode sync**: Also enable the **Sync** checkbox to send MTC from Ableton. See [MTC Setup](/4.-timecode-setup/mtc-midi-timecode-setup) for details.
***
## 2. Create a MIDI Track
1. Create a new MIDI Track (`Shift + Cmd + T` / `Shift + Ctrl + T`).
2. Rename the track (e.g., "MVP VIDEO" or "MVP LIGHTING").
***
## 3. Route the Output
1. Open the I/O section on the track (if hidden, press `Cmd/Ctrl + Option + I`).
2. **MIDI From**: Select **No Input**.
3. **MIDI To**: Select **MVP**.
4. **Channel**: Set to the channel configured in the MVP UI:
* Video channel (check your MVP Video Configuration -- default: Channel 1)
* Lighting channel (check your MVP Lighting Configuration -- default: Channel 3)
For both video and lighting, create **two separate tracks** -- one per channel.
***
## 4. Program Your Cues
1. **Insert a MIDI Clip**: Double-click a slot (Session View) or highlight an area and press `Shift + Cmd + M` (Arrangement View).
2. **Draw Notes**: Open the clip's Piano Roll. Draw notes that match your MVP file assignments:
* Note 1-99 = trigger the assigned clip
* Note 0 (C-2) = blackout
3. **Play**: Press Play in Ableton. The MVP triggers instantly.
> **Tip**: Disable the **Loop** toggle next to the piano roll.
***
## 5. Stopping Playback (Blackout)
Stopping Ableton does **not** stop the MVP. The last triggered clip continues playing.
To program a stop cue:
* Draw a note at **C-2 (Note 0)** at any point in your arrangement
* This triggers blackout (video goes black / DMX channels go to 0)
***
## Related Pages
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [Pro Tools Configuration](/5.-triggering/daw-computer-triggering/pro-tools-setup) -- Alternative DAW guide
* [Logic Pro Configuration](/5.-triggering/daw-computer-triggering/logic-pro-setup) -- Alternative DAW guide
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- Timecode sync from Ableton
* [MIDI Reference](/8.-reference/midi-reference) -- Complete note and CC reference
# Pro Tools Setup
This guide covers setting up Pro Tools to trigger video and lighting clips on the MVP via MIDI, and optionally sending MTC for timecode synchronization.
***
## Prerequisites
* MVP connected via USB-C (HOST port) to your computer
* Video and/or lighting clips assigned in the MVP's [Video Configuration](file:///2.-Video-Setup/video-configuration.md) or [Lighting Configuration](file:///3.-Lighting-Setup/lighting-configuration.md) pages
* Know your configured MIDI channels (check the Video and Lighting pages -- defaults are Channel 1 for video, Channel 3 for lighting)
***
## 1. Verify MIDI Connection
1. Open Pro Tools.
2. Go to **Setup > MIDI > MIDI Input Devices**.
3. Verify that **MVP** appears in the list and is checked/enabled.
If MVP doesn't appear, check your USB connection and try re-plugging the cable.
***
## 2. Create a MIDI Track
1. Go to **Track > New** (or press Cmd+Shift+N / Ctrl+Shift+N).
2. Create a new **MIDI Track**.
***
## 3. Route MIDI Output to MVP
1. Click on the track's **MIDI Output** selector (in the Mix window or I/O section of the Edit window).
2. Select **MVP** as the output device.
3. Set the **MIDI channel** to match your MVP configuration:
* For video triggers: the channel configured in MVP's Video settings (default: **Channel 1**)
* For lighting triggers: the channel configured in MVP's Lighting settings (default: **Channel 3**)
> **Tip**: Set the MIDI Input to **None** on your MVP trigger tracks. This prevents MIDI feedback loops if you have the MVP connected as both input and output.
***
## 4. Program MIDI Triggers
1. Switch to the **Edit** window if not already there.
2. Select the **Pencil tool** (or use the mini-keyboard in the MIDI Editor).
3. Draw MIDI notes on the piano roll:
* **Note 1-99**: Triggers the clip assigned to that note number
* **Note 0 (C-2)**: Triggers blackout
* Note length doesn't matter -- only the Note On event triggers the clip
### MIDI Note Numbering in Pro Tools
Pro Tools uses the **C3 = MIDI note 60** convention. Here's how MVP note numbers map:
| MVP Note | Pro Tools Note Name |
| ------------ | ------------------- |
| 0 (Blackout) | C-1 |
| 1 | C#-1 / Db-1 |
| 12 | C0 |
| 24 | C1 |
| 36 | C2 |
| 48 | C3 |
| 60 | C4 |
> **Tip**: The MVP Dashboard shows the actual MIDI note number received. If you're unsure about the mapping, play a note and check the Dashboard's Input Monitor to see which note number the MVP received.
***
## 5. Separate Tracks for Video and Lighting
To trigger both video and lighting clips from the same Pro Tools session:
1. Create **two MIDI tracks** -- one for video, one for lighting.
2. Route both to **MVP** as the output device.
3. Set the **video track** to your video MIDI channel (default: Channel 1).
4. Set the **lighting track** to your lighting MIDI channel (default: Channel 3).
5. Program video cues on the video track and lighting cues on the lighting track.
***
## 6. (Optional) Send MTC for Timecode Sync
If you're using the MVP's [Timeline Editor](/4.-timecode-setup/the-timeline-editor) for timecode-synced shows:
1. Go to **Setup > Peripherals > Synchronization** (or **Setup > MIDI > MIDI Beat Clock** depending on your Pro Tools version).
2. Enable **MTC output** to **MVP**.
3. Set the **frame rate** to match the rate configured in the MVP's Timeline Editor.
4. Optionally enable **MMC output** (Machine Control) for transport events (Stop, Play, Locate).
> *For details:* [*MTC (MIDI Timecode) Setup*](/4.-timecode-setup/mtc-midi-timecode-setup)
***
## 7. Stopping Playback
Stopping Pro Tools does **not** stop the MVP. The last triggered clip continues playing.
To stop video or lighting:
* **Draw a Note 0 (C-1)** at the end of your session or at any point where you want blackout
* This sends the blackout command to the MVP
***
## Tips
* **Disable Loop mode** on your MIDI clips in Pro Tools if you don't want triggers to repeat on loop playback
* **Use markers** in Pro Tools to label your visual cue points for easy reference
* **Monitor the MVP Dashboard** during programming to verify each note triggers the expected clip
***
## Related Pages
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [Ableton Live Setup](/5.-triggering/daw-computer-triggering/ableton-live-setup) -- Alternative DAW guide
* [Logic Pro Configuration](/5.-triggering/daw-computer-triggering/logic-pro-setup) -- Alternative DAW guide
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- Timecode sync from Pro Tools
* [MIDI Reference](/8.-reference/midi-reference) -- Complete note and CC reference
# Logic Pro Setup
This guide covers setting up Logic Pro to trigger video and lighting clips on the MVP via MIDI, and optionally sending MTC for timecode synchronization.
***
## Prerequisites
* MVP connected via USB-C (HOST port) to your Mac
* Video and/or lighting clips assigned in the MVP's [Video Configuration](/2.-video-setup/video-configuration) or [Lighting Configuration](/3.-lighting-setup/lighting-configuration) pages
* Know your configured MIDI channels (check the Video and Lighting pages -- defaults are Channel 1 for video, Channel 3 for lighting)
***
## 1. Create an External MIDI Track
1. Go to **Track > New Track** (or click the **+** button in the track header area).
2. Choose **External MIDI** as the track type.
3. Click **Create**.
***
## 2. Select MVP as MIDI Output
1. In the **Track Inspector** (left panel), find the **MIDI Output** dropdown.
2. Select **MVP** from the list.
If MVP doesn't appear, check your USB connection. You may need to go to **Logic Pro > Settings > MIDI > Inputs** and verify MVP is visible.
***
## 3. Set MIDI Channel
In the Track Inspector, set the **MIDI Channel**:
* For **video triggers**: Set to your video MIDI channel (default: **Channel 1**)
* For **lighting triggers**: Set to your lighting MIDI channel (default: **Channel 3**)
> **Tip**: Set the MIDI Input to **OFF** on your MVP trigger tracks to prevent feedback loops.
***
## 4. Program MIDI Triggers
1. Open the **Piano Roll** editor (double-click the MIDI region, or press P).
2. Use the **Pencil tool** to draw MIDI notes:
* **Note 1-99**: Triggers the clip assigned to that note number
* **Note 0**: Triggers blackout (video goes black / DMX all channels to 0)
* Note length doesn't matter -- only the Note On event triggers the clip
\[SCREENSHOT: Logic Pro Piano Roll with notes drawn, showing note names/numbers in the sidebar]
### MIDI Note Numbering in Logic Pro
Logic Pro's default note numbering convention uses **C3 = MIDI note 60**. MVP note numbers map as follows:
| MVP Note | Logic Note Name |
| ------------ | --------------- |
| 0 (Blackout) | C-2 |
| 1 | C#-2 |
| 12 | C-1 |
| 24 | C0 |
| 36 | C1 |
| 48 | C2 |
| 60 | C3 |
> **Note**: Logic Pro allows changing note display format in **Settings > Display > General**. If your note names look different, check this setting. The MVP Dashboard always shows the actual MIDI note number -- use it to verify.
***
## 5. Separate Tracks for Video and Lighting
To trigger both video and lighting from the same Logic session:
1. Create **two External MIDI tracks**.
2. Set both to output to **MVP**.
3. Set the **video track** to your video MIDI channel (default: Channel 1).
4. Set the **lighting track** to your lighting MIDI channel (default: Channel 3).
5. Arrange your video cues on one track and lighting cues on the other.
\[SCREENSHOT: Logic Pro with two MIDI tracks -- one labeled "MVP Video" on Ch.1, one labeled "MVP Lighting" on Ch.3]
***
## 6. Stopping Playback (Blackout)
Stopping Logic Pro does **not** stop the MVP. The last triggered clip continues playing.
To explicitly stop output:
* Draw a **Note 0** at the end of your arrangement or wherever you need blackout
* For both video and lighting blackout, place Note 0 on both tracks
***
## 7. (Optional) Send MTC for Timecode Sync
If you're using the MVP's [Timeline Editor](/4.-timecode-setup/the-timeline-editor) for timecode-synced shows:
1. Go to **File > Project Settings > Synchronization**.
2. Under the **MIDI** tab:
* Enable **Transmit MTC** (MIDI Timecode)
* Optionally enable **Transmit MMC** (MIDI Machine Control) for transport commands
3. Set the output to **MVP**.
4. Set the **frame rate** to match the rate configured in the MVP's Timeline Editor.
> *For details:* [*MTC (MIDI Timecode) Setup*](/4.-timecode-setup/mtc-midi-timecode-setup)
***
## Related Pages
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [Ableton Live Setup](/5.-triggering/daw-computer-triggering/ableton-live-setup) -- Alternative DAW guide
* [Pro Tools Configuration](/5.-triggering/daw-computer-triggering/pro-tools-setup) -- Alternative DAW guide
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- Timecode sync from Logic Pro
* [MIDI Reference](/8.-reference/midi-reference) -- Complete note and CC reference
# Other DAWS (General Guide)
This guide covers setting up any DAW or MIDI application to trigger video and lighting clips on the MVP. If your DAW isn't covered by our specific guides ([Ableton](broken://pages/1f4275d4c053ffb3e1675d3c53fdcdc284e2e017), [Pro Tools](broken://pages/4f621a212d05c07d4f88108f661e64701ed69645), [Logic Pro](broken://pages/6fcdb0999a7fcce8c22591aea17a835deb60b348)), follow these general steps.
***
## Prerequisites
* MVP connected via USB-C (HOST port) to your computer
* Video and/or lighting clips assigned in the MVP's configuration pages
* Know your configured MIDI channels (defaults: Channel 1 for video, Channel 3 for lighting)
***
## General Setup Steps
### 1. Connect the MVP
Plug the MVP into your computer using the included USB-C cable (HOST port on the MVP). The MVP appears as a class-compliant USB MIDI device -- no drivers needed.
### 2. Find the MVP in Your DAW
Open your DAW's **MIDI settings** or **preferences**. Look for:
* MIDI Output Devices
* MIDI Ports
* External Instruments
The MVP should appear as **"MVP"** in the list of available MIDI outputs. Enable it.
### 3. Create a MIDI Track
Create a new MIDI or Instrument track in your DAW. Route its **MIDI output** to **MVP**.
### 4. Set the MIDI Channel
Set the track's output MIDI channel:
* **Video channel**: Default is Channel 1 (check your MVP Video Configuration page)
* **Lighting channel**: Default is Channel 3 (check your MVP Lighting Configuration page)
For both video and lighting control, create separate tracks -- one per channel.
### 5. Program Triggers
Draw MIDI notes on the track:
* **Note 1-99**: Trigger the clip assigned to that number
* **Note 0**: Blackout (video goes black / DMX all channels to 0)
* **Note duration doesn't matter** -- only the Note On message triggers the clip
### 6. Test
Play the track and watch the MVP Dashboard's Input Monitor to verify:
* The correct MIDI note numbers are being received
* Clips are triggering as expected
***
## Important Notes
### Note On is the trigger
The MVP triggers a clip the instant it receives a **Note On** message. The note's duration (how long you hold it or how long the MIDI note is drawn) is irrelevant. A 1-tick note and a 4-bar note both trigger the same clip at the same moment.
### Stopping playback
Pressing Stop in your DAW does **not** stop the MVP. The last triggered clip continues playing (or looping). To explicitly stop output, send **Note 0** (blackout).
### MIDI input routing
Set the MVP track's MIDI **Input** to None or Off (if your DAW supports this). This prevents MIDI feedback if the MVP sends any messages back.
***
## DAW-Specific Notes
| DAW | Notes |
| ------------------- | ------------------------------------------------------- |
| **Reaper** | Enable in Preferences > MIDI Devices |
| **Cubase / Nuendo** | Enable in Studio > Studio Setup > MIDI Port Setup |
| **FL Studio** | Enable in Options > MIDI Settings > Output |
| **Bitwig Studio** | Appears in Settings > Controllers |
| **Reason** | Enable in Preferences > MIDI > Advanced |
| **GarageBand** | Automatically available as an External MIDI destination |
| **QLab** | Add as a MIDI output in Workspace Settings |
| **Companion** | Add MVP as a MIDI output in the settings |
| **MainStage** | Available as an External Instrument destination |
***
## Tips
* **Use the MVP Dashboard as your debugging tool**: The Input Monitor shows every MIDI event with the exact note number, channel, and device name.
* **MIDI note numbering varies between DAWs**: "C3" might be note 48 in one DAW and note 60 in another. Always check the Dashboard for the actual note number.
***
## Related Pages
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [Ableton Live Setup](/5.-triggering/daw-computer-triggering/ableton-live-setup) -- Ableton-specific guide
* [Pro Tools Configuration](/5.-triggering/daw-computer-triggering/pro-tools-setup) -- Pro Tools-specific guide
* [Logic Pro Configuration](/5.-triggering/daw-computer-triggering/logic-pro-setup) -- Logic Pro-specific guide
* [Network MIDI (RTP-MIDI) Setup](/5.-triggering/network-midi-rtp-midi-setup) -- Wireless MIDI to the MVP
* [MIDI Reference](/8.-reference/midi-reference) -- Complete note and CC reference
# Network MIDI (RTP-MIDI) Setup
Network MIDI (RTP-MIDI) allows you to send MIDI to the MVP over a standard Wi-Fi or Ethernet network. This is the preferred method for long-distance runs (e.g., FOH to stage) where USB cables are not feasible.
> **Performance Note**: While Network MIDI works over Wi-Fi, it can be susceptible to latency and jitter on congested networks. For critical live performances, a hardwired Ethernet connection is recommended.
***
## 1. Network Connection
First, you must choose where RTP-MIDI will be connecting from, WiFi or Ethernet:
Open **System Settings → Network MIDI Interface** and choose which one should advertise RTP-MIDI.
See \[[Network MIDI Interface](/6.-configuration/network-midi-interface)] for details
### For Wi-Fi
1. Open the MVP UI and click the **Wi-Fi icon** in the top bar.
2. Connect to your Wi-Fi network.
3. Ensure your Network MIDI Client is on the **same Wi-Fi network**.
### For Ethernet
1. Connect an Ethernet cable from the MVP to your computer (directly or via a network switch).
2. Set both devices to the same IP range:
* MVP default: `2.0.0.111`, Subnet `255.0.0.0`
* Computer: Set static IP (e.g., `2.0.0.50`), Subnet `255.0.0.0`
3. Mac:
Windows:
***
## 2. macOS Setup (Native)
Mac has RTP-MIDI built into the operating system.
### Step 1: Open MIDI Studio
1. Press `Command + Space` to open Spotlight.
2. Type **"Audio MIDI Setup"** and press Enter.
3. In the top menu bar, click **Window > Show MIDI Studio**.
### Step 2: Configure Network Session
1. In the MIDI Studio window, double-click the **Globe Icon** (labeled "Network").\
(*Or in the top menu bar, click MIDI Studio > Open MIDI Network Setup.)*
1. In the **"My Sessions"** box (top left), click **+** to create a new session.
2. Rename it to **"Network MVP"**.
3. Check the **checkbox** next to the session name to enable it.
### Step 3: Connect to MVP (Critical)
In the **"Directory"** box (bottom left), you will see two devices listed:
* `MVP` (Short name)
* `MVP/RtMidiIn Client-MVP` (Long name)
**You MUST select the one with the LONG NAME.**
1. Select **`MVP/RtMidiIn Client-MVP`**.
2. Click **Connect**.
3. The device moves to the **"Participants"** list on the right.
***
## 3. Windows Setup (rtpMIDI)
Windows does not support RTP-MIDI natively. You can use the free **rtpMIDI** app.
1. **Download**: Install [rtpMIDI](https://www.tobias-erichsen.de/software/rtpmidi.html).
2. **Launch**: Open the program. The interface is nearly identical to the macOS version.
3. **Create Session**: Click **+** under "My Sessions" and rename to **"Network MVP"**.
4. **Enable**: Check the box above the session name.
5. **Connect**: In the Directory, select the **long name** (`MVP/RtMidiIn Client-MVP`) and click **Connect**.
***
## 4. Testing Your Connection
### Using Your DAW
In your DAW's MIDI settings, **"Network MVP"** will appear as an available MIDI output.
1. Set your MIDI track's output to **Network MVP**.
2. Set the channel to match your MVP configuration.
3. Play a MIDI note -- the MVP Dashboard should show the event.
### Without a DAW
To verify the connection without opening a DAW, use a virtual MIDI keyboard:
#### macOS: MidiKeys (Simplest)
1. Download MidiKeys (free).
2. Set Destination to **"Network MVP"**.
3. Press keys on your computer keyboard to trigger the MVP.
#### Cross-Platform: VMPK
1. Download VMPK (Virtual MIDI Piano Keyboard).
2. **macOS "Unverified Developer" fix**: Right-click the app icon > Select Open > Click Open in the dialog.
3. Open VMPK > Go to **Edit > MIDI Connections**.
4. MIDI OUT Driver: Select **CoreMIDI** (Mac) or **Windows MM** (PC).
5. Output Connection: Select **"Network MVP"**.
6. Click OK and play the on-screen keys.
***
## Use Cases for Network MIDI
* **FOH to stage**: Send MIDI from the front-of-house computer to the MVP on stage over Ethernet -- no long USB cable needed.
* **Wireless triggering**: Control the MVP from a laptop or tablet over Wi-Fi during rehearsal.
* **MTC over network**: Send [MIDI Timecode](/4.-timecode-setup/mtc-midi-timecode-setup) to the MVP wirelessly.
* **Remote configuration**: Trigger test clips from anywhere on the network.
***
## Related Pages
* [Network MIDI Interface](/6.-configuration/network-midi-interface) -- Choose Ethernet or Wi-Fi for RTP-MIDI advertisement
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods
* [MTC (MIDI Timecode) Setup](/4.-timecode-setup/mtc-midi-timecode-setup) -- Timecode sync over Network MIDI
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Ethernet IP setup
* [MIDI Reference](/8.-reference/midi-reference) -- Complete note and CC reference
# 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) 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))
* 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))
### 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).
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign clips and set MIDI channels
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign DMX clips
* [USB Keyboard Triggering](/5.-triggering/usb-keyboards-hid) -- Use a standard keyboard as a trigger pad
* [CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode) -- Trigger clips via CC #110
* [Network MIDI (RTP-MIDI) Setup](/5.-triggering/network-midi-rtp-midi-setup) -- Wireless MIDI controllers
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods compared
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots) -- Prepare and switch between show configurations
# USB Keyboards (HID)
Any standard USB keyboard or numeric keypad can trigger video and lighting clips on the MVP -- no MIDI controller or DAW required.
***
## Connection
Plug a USB keyboard or numeric keypad into one of the MVP's **USB-A ports** on the rear panel.
The MVP detects keyboards automatically. If you plug one in while the system is running, it will be recognized within a few seconds.
***
## Key Mapping
### Video Triggers
Press a key to trigger the corresponding video clip:
| Keys | Clips |
| --------------------------------------- | -------------- |
| `1` `2` `3` `4` `5` `6` `7` `8` `9` `0` | Clips 1-10 |
| `Q` `W` `E` `R` `T` `Y` `U` `I` `O` `P` | Clips 11-20 |
| `A` `S` `D` `F` `G` `H` `J` `K` `L` | Clips 21-29 |
| `Z` `X` `C` `V` `B` `N` `M` | Clips 30-36 |
| `ENTER` | Black Out Clip |
### Lighting Triggers
Hold **Shift** and press a key to trigger the corresponding lighting (DMX) clip:
| Keys | Clips |
| ------------------------- | -------------------- |
| `Shift` + `1` through `0` | Lighting Clips 1-10 |
| `Shift` + `Q` through `P` | Lighting Clips 11-20 |
| `Shift` + `A` through `L` | Lighting Clips 21-29 |
| `Shift` + `Z` through `M` | Lighting Clips 30-36 |
| `Shift` + `Enter` | Black Out Clip |
***
## Visual Layout
The mapping follows the standard QWERTY keyboard layout, reading left-to-right, top-to-bottom:
```
┌───┬───┬───┬───┬───┬───┬───┬───┬───┬───┐
│ 1 │ 2 │ 3 │ 4 │ 5 │ 6 │ 7 │ 8 │ 9 │ 0 │ Clips 1-10
├───┼───┼───┼───┼───┼───┼───┼───┼───┼───┤
│ Q │ W │ E │ R │ T │ Y │ U │ I │ O │ P │ Clips 11-20
├───┼───┼───┼───┼───┼───┼───┼───┼───┼───┤
│ A │ S │ D │ F │ G │ H │ J │ K │ L │ │ Clips 21-29
├───┼───┼───┼───┼───┼───┼───┼───┼───┼───┤
│ Z │ X │ C │ V │ B │ N │ M │ │ │ │ Clips 30-36
└───┴───┴───┴───┴───┴───┴───┴───┴───┴───┘
```
> **Tip**: A small wireless numeric keypad makes a great compact 10-button trigger controller (keys 1-0 = clips 1-10).
***
## Dashboard Feedback
When you press a key, the Dashboard shows the trigger event in the **Input Monitor** just like a MIDI trigger:
* The **MIDI display** flashes with the corresponding note number
* The **Event Log** records the keystroke with a "KEYBOARD" label
* The **Status Display** on the device shows the key label and "KEYBOARD"
\[SCREENSHOT: Dashboard Input Monitor showing a keyboard trigger event in the event log]
***
## Enabling Keyboard Triggering
USB keyboard triggering is **always enabled** -- there is no setting to turn it on or off. Any connected USB keyboard will trigger clips immediately.
> **Note**: Keyboard triggering is listed in the **Beta Features** dialog in [System Settings](/6.-configuration/system-settings) for informational purposes, but it is always active regardless of whether beta features are enabled.
***
## Limitations
* **36 clips maximum**: The keyboard layout maps to clips 1-36 only. For clips 37-99, use MIDI triggers.
* **Simultaneous with MIDI**: Keyboard triggers work alongside MIDI and timecode. However, when timecode is actively driving playback, keyboard triggers (like any manual trigger) are suppressed.
* **Key repeat**: Holding a key down does not re-trigger the clip continuously.
***
## Use Cases
* **Backup trigger method**: Keep a small USB keypad connected as a fallback if your MIDI controller has issues.
* **Simple shows**: For shows with 10 or fewer clips, a wireless numeric keypad is all you need.
* **Crew control**: Hand a labeled keypad to a stage crew member for simple video/lighting cue triggering without MIDI knowledge.
* **Tech rehearsal**: Quickly test clips during setup without needing to open a DAW.
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign video files to clip slots
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign DMX clips to lighting slots
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods compared
* [Hardware Controllers](/5.-triggering/hardware-controllers) -- Standalone MIDI controller setup
# MIDI CC Trigger Mode
MIDI CC Trigger Mode is an alternative way to trigger video and lighting clips using **MIDI Control Change messages** instead of MIDI Notes. This is useful when your controller or show system sends CC messages but not note messages.
***
## How It Works
When enabled, **MIDI CC #110** acts as a clip trigger:
| CC #110 Value | Action |
| ------------- | ----------------------------------------------------------------- |
| 1-99 | Trigger the clip assigned to that number (same as MIDI note 1-99) |
| 100 | Trigger blackout (same as MIDI note 0) |
| 0 | Ignored |
| 101-127 | Ignored |
The trigger channel follows the same rules as MIDI note triggers:
* **CC #110 on the Video MIDI channel** triggers video clips
* **CC #110 on the Lighting MIDI channel** triggers lighting clips
***
## Enabling CC Trigger Mode
1. Open [System Settings](/6.-configuration/system-settings) (gear icon in the top-right corner, then select **System**).
2. Expand the **MIDI CC Trigger Mode** panel.
3. Toggle the switch to **Enable**.
***
## Example
Assume your Video MIDI channel is set to Channel 1 and CC Trigger Mode is enabled:
| MIDI Message | Result |
| ----------------------------- | ---------------------------------------------------------------------------------- |
| CC #110, Value 5, Channel 1 | Plays the video assigned to Note 5 |
| CC #110, Value 42, Channel 1 | Plays the video assigned to Note 42 |
| CC #110, Value 100, Channel 1 | Video blackout |
| CC #110, Value 5, Channel 3 | Plays the lighting clip assigned to Note 5 (if Channel 3 is your lighting channel) |
***
## UI Feedback
When a clip is triggered via CC #110, the Dashboard **Input Monitor** and the device **Status Display** show:
* The CC value that was received
* A **"MIDI CC"** label (instead of a note name)
This helps you distinguish between note-triggered and CC-triggered clips during monitoring.
***
## Notes
* CC Trigger Mode works **alongside** regular MIDI note triggers -- enabling it does not disable note triggering.
* Only CC #110 is used for clip triggering. Other CC numbers are unaffected.
* The CC trigger uses the same clip assignments as MIDI notes -- there is no separate configuration. CC value 5 triggers the same clip as MIDI note 5.
* When timecode is actively driving playback, CC triggers (like all manual triggers) are suppressed.
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign clips to note/CC slots
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign DMX clips
* [Triggering Overview](/5.-triggering/triggering-overview) -- All trigger methods compared
* [MIDI Reference](/8.-reference/midi-reference) -- Complete MIDI CC and note reference
# MIDI Transport (Prev / Next)
Notes 101 and 102 step backward and forward through the assignments in the active configuration slot.
The MVP now responds to two dedicated MIDI notes that step backward and forward through the assignments in your currently active Configuration Slot. This turns any MIDI controller with two free buttons or pads into a show navigator.
These two notes are **hardcoded** and cannot be reassigned. They live outside the 1–99 trigger range so they never collide with your clip assignments.
| Function | MIDI Note |
| -------- | --------- |
| Previous | **101** |
| Next | **102** |
***
### How It Works
When the MVP receives Note 101 or 102 on the **Video Channel**, it steps the video transport. When it receives them on the **Lighting Channel**, it steps the DMX transport. The two domains are independent. You can advance video without disturbing the running DMX clip and vice versa.
Stepping always operates within the **currently active Configuration Slot** (A through E). The transport will:
* **Skip empty assignments** — if Note 3 is empty and you press Next from Note 2, the system jumps directly to Note 4.
* **Wrap around** — pressing Next on the last assignment returns you to the first; pressing Prev on the first goes to the last.
* **Stay inside the active slot** — Prev/Next never crosses into another slot.
If nothing is currently playing on the channel (blackout, default video, or boot) Prev/Next starts from the first non-empty assignment in the active slot.
***
### Where to Find It
There is **no toggle** — the Prev/Next notes are always active. Documentation for the feature is mirrored in **System Settings → MIDI Transport (Prev / Next)** so you have a quick on-device reference.
***
### Repeated Notes: The Drumstick Problem
Hardware MIDI controllers can sometimes be very sensitive, and unintentionally send the same note **twice within a few milliseconds** when struck. Without protection, a single drumstick hit could advance two clips.
To prevent this, the MVP enforces a **300 ms delay** per direction:
* After receiving Note 102 (Next), any further Next notes within 300 ms are ignored.
* The Prev direction debounces independently — you can press Prev right after Next without one blocking the other.
300 ms is long enough to absorb every double-trigger we've seen from real hardware, but short enough that intentional rapid stepping (three or four clips in a row) still feels responsive.
***
### Interaction with Other Features
* **Timecode** — when LTC or MTC is actively driving playback, Prev/Next is suppressed. The timecode source owns the transport. Stopping timecode re-enables Prev/Next.
* **Autoplay** — Prev/Next is treated as autoplay navigation, not as a "disable autoplay" command. After stepping with Prev/Next, autoplay continues to advance at the next end-of-clip.
* **Loop Mode Override** — independent of transport. Prev/Next steps to the next clip regardless of how the current clip is configured to behave at end-of-video.
* **Blackout (Note 0)** — clears the current position. The next Prev or Next starts fresh at the first non-empty assignment.
***
### Related Pages
* [Autoplay](/6.-configuration/autoplay) — Automatic advance at end-of-clip
* [Configuration Slots](/6.-configuration/configuration-slots) — How A–E slots organize your shows
* [MIDI Reference](/8.-reference/midi-reference) — Full MIDI note / CC / HID mapping
# 6. Configuration
Adjust device-level settings, configure display output and network MIDI, and save complete configurations for different shows or venues.
***
#### In This Section
* [**System Settings**](/6.-configuration/system-settings) — Display brightness, status LED, and other device preferences
* [**Autoplay**](/6.-configuration/autoplay) — Automatic sequential playback of the active slot
* [**Network MIDI Interface**](/6.-configuration/network-midi-interface) — Choose Ethernet or Wi-Fi for RTP-MIDI
* [**Display Settings**](/6.-configuration/display-settings) — HDMI resolution and refresh rate, saved per display
* [**Display Calibration**](/6.-configuration/display-settings/display-calibration) — Position and resize the output on screen
* [**Configuration Slots** ](/6.-configuration/configuration-slots)— Save and recall full device configurations (slots A–E)
# System Settings
The **System Settings** dialog contains device-level preferences. To open it, click the **gear icon** in the top-right corner of any page and select **System**.
***
## Status Display Brightness
Controls the brightness of the front-panel LCD screen.
* **Range**: 1 (dimmest) to 255 (brightest)
* **Default**: 200
* Drag the slider to adjust in real time
> **Tip**: In dark venues, lowering the brightness prevents the display from being a distraction on stage.
***
## Status LED
A toggle to enable or disable the front-panel LED indicator.
| Setting | Behavior |
| --------------------- | --------------------------------------------------------- |
| **Enabled** (default) | LED provides visual feedback for current mode (see below) |
| **Disabled** | LED is completely off |
### LED Behavior When Enabled
| Mode | Steady State | On Trigger |
| -------------------------- | ------------ | ----------------------------------- |
| **Standard** (no timecode) | Blue LED on | Red flashes briefly on each trigger |
| **Timecode active** | Red LED on | Blue flashes once per second |
***
## MIDI CC Trigger Mode
An expandable panel with a toggle to enable or disable CC-based clip triggering. When enabled, **MIDI CC #110** can trigger video and lighting clips as an alternative to MIDI notes.
This is useful for controllers that send CC messages but not note messages.
For full details on how CC triggering works, clip mapping, and important usage warnings, see the dedicated [MIDI CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode) page.
***
## MIDI Transport (Prev / Next)
A reference panel documenting the two hardcoded transport notes: **Note 101 (Previous)** and **Note 102 (Next)**, which step backward and forward through the assignments in the active configuration slot. There is nothing to configure; the notes are always active.
See [MIDI Transport (Prev / Next)](/5.-triggering/midi-transport-prev-next) for full details.
***
## Autoplay
An expandable panel with two independent switches — **Video** and **Lighting** — that make the MVP automatically advance to the next non-empty assignment in the active configuration slot at the end of every clip. The panel header shows the current state at a glance: `Off`, `Video`, `Lighting`, or `Video + Lighting`. Changes apply immediately; there is no Apply button.
For advance logic, boot behavior, the 5-second still-image timer, and how autoplay interacts with timecode and per-clip overrides, see the dedicated [Autoplay](/6.-configuration/autoplay) page.
***
## Network MIDI Interface
An expandable panel that controls which network connection, **Ethernet** or **Wi-Fi**, the MVP's RTP-MIDI session uses. This prevents duplicate MVP entries from appearing in RTP-MIDI clients when both interfaces are connected to the same network.
Switching restarts the RTP-MIDI system, so existing RTP-MIDI sessions are dropped and clients must reconnect. For full details and troubleshooting, see the dedicated [Network MIDI Interface](/6.-configuration/network-midi-interface) page.
***
## Display Settings
An expandable panel for choosing the HDMI output's resolution and refresh rate, and for opening the Display Calibration tool. The panel header shows the currently active mode (for example `1920×1080 @ 60 Hz`). The MVP remembers settings **per display**, identified by EDID, so every TV, projector, or processor you plug in is recognised automatically.
For resolution selection modes (Auto / Advanced / Forced), per-display profiles, and hotplug behavior, see [Display Settings](#display-settings). For positioning and resizing the video output on the physical display, see [Display Calibration](/6.-configuration/display-settings/display-calibration).
***
## Beta Features
A link at the bottom of System Settings opens the **Beta Features** dialog, where you can enable experimental features like [Effects Mode](/2.-video-setup/effects-mode).
Beta features are experimental and may change in future updates. When the **Enable Beta Features** toggle is on, additional options become available elsewhere in the UI (for example, "Effects" appears in the Video Mode dropdown on the Videos page).
***
## Status Display Views
The front-panel color Status Display switches automatically between three views based on activity:
### HOME View (Default)
Shown at idle and on startup. Displays connection status for all interfaces:
| Row | Shows |
| --------------- | ------------------------------------ |
| **HDMI** | Resolution and connected device name |
| **ETH** | IP address and subnet mask |
| **WIFI** | IP address and SSID |
| **MVP VERSION** | Current firmware version |
Disconnected interfaces show "NOT CONNECTED." If an MVP update is available, a pulsing green banner appears at the bottom.
A scrolling ticker along the bottom edge continuously displays connection details for HDMI, Ethernet, Wi-Fi, and MIDI devices.
### LIVE MIDI View
Appears automatically when a MIDI note, CC trigger, or keyboard trigger is received. Shows two side-by-side boxes:
| Box | Color | Content |
| ------------ | ------ | ------------------------------------- |
| **VIDEO** | Teal | Trigger info for the video channel |
| **LIGHTING** | Purple | Trigger info for the lighting channel |
Each box adapts its display based on the trigger source:
* **MIDI Note**: Shows the note name (e.g., "C3") and note number
* **MIDI CC** (CC Trigger Mode): Shows the CC value and "MIDI CC" label
* **USB Keyboard**: Shows the key label (e.g., "Q") and "KEYBOARD" label
Below the trigger boxes, playback rows show the currently playing filename and playback position for both Video and Lighting. An animated gradient stripe indicates active playback.
### LIVE TC (Timecode) View
Appears automatically when timecode is received. Displays a large timecode clock in HH:MM:SS:FF format with the active configuration slot name above it. Below the timecode, playback rows show currently playing files.
The FPS label below the timecode shows the source type and frame rate (e.g., "LTC 30fps"). It turns red if a frame rate mismatch is detected, and displays "No Signal" when timecode stops.
### Display Timeout
After 2 minutes of inactivity (no MIDI, playback, or timecode), the display automatically returns to the HOME view.
***
## Related Pages
* [Autoplay](/6.-configuration/autoplay) -- Automatic sequential playback of the active slot
* [Network MIDI Interface](/6.-configuration/network-midi-interface) -- Choose Ethernet or Wi-Fi for RTP-MIDI
* [Display Settings](/6.-configuration/display-settings) -- Resolution selection and per-display profiles
* [Display Calibration](/6.-configuration/display-settings/display-calibration) -- Reposition and resize the video output
* [Configuration Slots (A-E)](/6.-configuration/configuration-slots) -- Save and switch between full setups
* [MIDI CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode) -- Full CC triggering guide
* [MIDI Transport (Prev / Next)](/5.-triggering/midi-transport-prev-next) -- Notes 101/102 transport
* [Effects Mode (Beta)](/2.-video-setup/effects-mode) -- Real-time video effects
* [Hardware Connections & Specs](/1.-getting-started/hardware-connections-and-specs) -- Port-by-port guide
# Configuration Slots
The MVP supports **5 independent configuration slots** (A through E) for Video, Lighting, and Timecode. Slots let you prepare multiple show configurations and switch between them instantly -- even during a live performance.
***
## What Are Slots?
Each slot is a separate bank of MIDI note-to-clip assignments. For example:
* **Slot A**: Verse visuals and ambient lighting
* **Slot B**: Chorus visuals and high-energy lighting
* **Slot C**: Acoustic set with different video clips
* **Slot D**: Backup configuration
* **Slot E**: Rehearsal/test clips
When you switch from Slot A to Slot B, all the MIDI note assignments change to Slot B's configuration. Note 1 might trigger "ocean.mp4" in Slot A but "fireworks.mp4" in Slot B.
***
## Independent Slots
**Video, Lighting, and Timecode slots are fully independent.** You can have:
* Video on Slot B
* Lighting on Slot D
* Timecode on Slot A
Each media type has its own A-E slot selection, stored independently on the device.
***
## Switching Slots from the UI
On the Video, Lighting, and Timecode pages, click the **slot name** in the header to expand the slot selector. Click any slot to switch.
### Video and Lighting Slots
* After switching, click **"Sync Changes to Playback"** to apply the new slot's assignments.
* If you have unsaved changes, you'll be prompted to Sync, discard, or cancel.
### Timecode Slots
* Slot switches take effect **immediately** -- saving auto-syncs to playback. There is no separate "Sync Changes" step.
* If you have unsaved changes on the current slot, they are saved automatically before switching.
### Renaming Slots
Click the **pencil icon** next to a slot to rename it. Names can be up to **30 characters** using letters, numbers, spaces, underscores, dashes, dots, parentheses, and ampersand.
***
## Switching Slots via MIDI (Live Performance)
During a live show, you can switch **Video and Lighting** slots using **MIDI CC #119** without touching the browser:
| CC #119 Value | Slot |
| ------------- | ------ |
| 10 | Slot A |
| 20 | Slot B |
| 30 | Slot C |
| 40 | Slot D |
| 50 | Slot E |
**Important details:**
* Send CC #119 on the **video MIDI channel** to switch the video slot
* Send CC #119 on the **lighting MIDI channel** to switch the lighting slot
* Video and lighting switch **independently** based on which channel receives the CC
* **Value 0 is ignored** (common DAW reset value that would otherwise cause unintended switches)
* **Only the exact values above are accepted** -- values like 11, 25, or 35 are ignored
* If the requested slot is already active, the switch is silently skipped
* **Timecode does not support MIDI CC slot switching** -- timecode slots can only be changed from the UI
### Example: Switching Slots from a DAW
In your DAW's MIDI track:
1. At the point where you want to switch to Slot B, insert a **CC #119 message with value 20** on the video MIDI channel.
2. The MVP will switch to Slot B immediately -- subsequent MIDI note triggers will use Slot B's assignments.
### Example: Switching Slots from a Controller
If your MIDI controller has knobs or buttons that send CC messages:
1. Assign a button to send **CC #119** on the appropriate channel.
2. Set the value for each button: 10 for A, 20 for B, etc.
3. Press the button during the show to switch slots.
***
## What Happens When You Switch Slots?
* The new slot's MIDI assignments become active **immediately** -- no loading delay
* The currently playing clip **continues playing** (it doesn't stop or restart)
* The next MIDI note trigger will use the new slot's assignments
* A "Slot Changed" toast notification appears on the physical Status Display
* The Dashboard shows the new active slot
### Slot Status Indicators
When a MIDI CC #119 switch changes the active slot during a show, the Dashboard shows a **lightning bolt icon** next to the slot name with the tooltip "Slot changed via MIDI." The Lighting/Video page headers also display warning chips when the slot you're viewing in the UI differs from the slot that's actively being used for playback.
Timecode slots work more simply. Switching always takes effect immediately with no separate sync step.
***
## Editing Slot Contents
Each slot's assignments are edited independently:
1. Select the slot (A-E) on the relevant page
2. Enable **Edit Mode**
3. Make your assignments (assign files to MIDI notes, or place clips on the timeline)
4. **Video/Lighting**: Click **Sync Changes to Playback**
5. **Timecode**: Click **Save Changes** (auto-syncs)
Changes to one slot do not affect other slots.
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Video slot setup
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Lighting slot setup
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor) -- Timecode slot setup
* [MIDI Reference](/8.-reference/midi-reference) -- CC #119 reference
* [Triggering Overview](file:///5753738/5.-Triggering/triggering-overview.md) -- All trigger methods
# Autoplay
Turn your MVP into a sequential playback server: Automatically advance to the next clip at the end of every video or lighting clip.
**Autoplay** turns the MVP into a sequential playback server. With one switch, the device automatically advances to the next clip in the active Configuration Slot at the end of every video or DMX clip. No triggering, no operator intervention, and no laptop required.
This is the feature you reach for when:
* You're running **walk-in, intermission, or pre-show ambience** and want a continuous loop of clips with zero touch.
* You want a **standalone kiosk or installation** that boots, starts the show, and runs forever.
* You're touring without a dedicated playback operator and need a "set it and forget it" mode.
Autoplay is **per-domain**: you can enable it for Video, for Lighting, for both, or for neither. The two domains advance independently — your video clips can autoplay while your DMX clips stay on direct-trigger, or vice versa.
***
### Where to Find It
1. Click the **gear icon** in the top-right corner of any page.
2. Select **System** to open the System Settings dialog.
3. Expand the **Autoplay** panel (play-circle icon).
The panel header shows the current state at a glance — `Off`, `Video`, `Lighting`, or `Video + Lighting`.
Inside the panel are two switches, **Video** and **Lighting**. Flipping either switch is applied to the device immediately; you don't need to click a separate Apply or Save button.
***
### How Autoplay Advances
When a clip finishes naturally, autoplay searches for the **next non-empty assignment** in the **currently active Configuration Slot** and starts it.
The advance logic is identical to the **Next** MIDI transport:
* **Empty assignments are skipped.** If your active slot has clips at notes 1, 2, 4, and 7, autoplay advances 1 → 2 → 4 → 7 → 1 → 2 → ...
* **Wraps within the active slot.** After the last assignment, it returns to the first. Autoplay never crosses into another slot.
* **Anchored on the current clip.** If you manually triggered Note 5 mid-show, the next advance is from Note 5 — not from wherever autoplay left off the last time.
If the active slot is **empty**, autoplay idles silently. It will not start anything until you add an assignment or switch to a different slot.
***
### Still Images Auto-Advance After 5 Seconds
To make autoplay work for slideshows, every still image is shown for **5 seconds** and then auto-advanced to the next assignment.
This duration is hardcoded. Re-triggering the same still resets the 5-second timer; manually changing to a different clip cancels the pending advance cleanly.
The 5-second timer is **only active when Autoplay → Video is enabled**. With autoplay off, stills behave the way they always have: they stay on screen until you trigger something else.
***
### Boot Behavior
When **Autoplay** is enabled at startup, the device skips the default video and instead starts the **first non-empty assignment** in the active Configuration Slot.
This makes the MVP suitable for unattended use: connect HDMI, connect power, and the show runs.
* If Autoplay → Video is on at boot, the first non-empty video assignment starts playing as soon as HDMI is detected.
* If Autoplay → Lighting is on at boot, the first non-empty DMX assignment starts as soon as the artnet daemon is up.
* If both are on, both start simultaneously and run independently.
* If the active slot has no assignments, the device idles in blackout / black until you assign something or switch slots.
***
### Manual Triggers Do Not Disable Autoplay
This is a deliberate design choice. With autoplay on, you can still:
* Trigger any individual clip by MIDI note (or HID keyboard, or UI play button)
* Step manually with **Prev / Next** (Notes 101 / 102)
* Use the dashboard playback controls
Each of these plays the clip you asked for. **Autoplay does not turn itself off** — at the next end-of-clip, the show keeps advancing from wherever you landed.
***
### Interaction with Other Features
* **Prev / Next** — treated as autoplay navigation, not as a "disable autoplay" command. After stepping, autoplay continues from the new position.
* **Loop Mode Override** — **autoplay wins.** Even if a clip has a per-video override set to Loop, Freeze, or Blank, autoplay advances at the natural end of the clip. Loop Mode Override only applies when autoplay is off.
* **Timecode (LTC / MTC)** — autoplay is suppressed while timecode is actively driving playback. The timecode source owns the transport. When timecode stops, autoplay resumes responsibility at the next end-of-clip.
* **Blackout (Note 0)** — clears the current position. Autoplay will not auto-start from blackout — trigger a clip manually (or wait for the next boot / config change) to resume sequencing.
***
### Related Pages
* [MIDI Transport — Previous / Next](/5.-triggering/midi-transport-prev-next) — Hand-driven equivalent of Autoplay advance
* [Loop Mode Override](/2.-video-setup/loop-mode-override) — Per-clip end-of-stream behavior (when Autoplay is off)
* [Configuration Slots](/6.-configuration/configuration-slots) — How A–E slots organize your shows
* [Timecode Overview](/4.-timecode-setup/timecode-overview) — How timecode interacts with manual transport
# Network MIDI Interface
Choose which network interface to use for RTP-MIDI connections.
The **Network MIDI Interface** setting controls which of the MVP's network connections (Ethernet or Wi-Fi) advertises the RTP-MIDI session.
It lives in the **System Settings** dialog, under the **Network MIDI Interface** expandable panel.
### Choosing an Interface
| Option | Advertises on | When to use |
| ------------ | ------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Ethernet** | `eth0` | Default. Use for fixed installations, FOH-to-stage runs, and any show where latency and jitter must be minimised. |
| **Wi-Fi** | `wlan0` | Use when the MVP is connected over Wi-Fi and no Ethernet is available. |
> **Performance Note**: RTP-MIDI over Wi-Fi is more susceptible to latency and jitter than Ethernet. For critical live performances, select **Ethernet** whenever a hardwired connection is available. See [Network MIDI (RTP-MIDI) Setup](/5.-triggering/network-midi-rtp-midi-setup) for full network setup instructions.
***
### Security Considerations
When **Wi-Fi** is selected, anyone on the same Wi-Fi network can discover and connect to the MVP's RTP-MIDI session. Do not use RTP-MIDI over Wi-Fi on public or untrusted networks.
* On a trusted private Wi-Fi network (e.g., a dedicated show network), this is safe.
* On public Wi-Fi (e.g., a venue's guest network), use **Ethernet** instead, or ensure the Wi-Fi network is isolated and password-protected.
***
### Related Pages
* [Network MIDI (RTP-MIDI) Setup](/5.-triggering/network-midi-rtp-midi-setup) — Full setup guide for macOS and Windows
* [System Settings](/6.-configuration/system-settings) — All device-level settings
* [Wi-Fi Setup](/7.-networking/wifi-setup) — Connecting the MVP to a Wi-Fi network
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) — Ethernet IP configuration
* [IP Range Conflicts](/7.-networking/ip-range-conflicts) — What happens when Ethernet and Wi-Fi share a subnet
# Display Settings
Choose the HDMI output resolution and refresh rate. The MVP remembers your choice per display, identified by EDID.
The MVP automatically negotiates the best video mode with whatever display you plug into the HDMI port. For most users this works out of the box and needs no attention. The **Display Settings** panel inside System Settings lets you override that behavior when you need to: pick a specific resolution, force a known-good mode for finicky projectors, or reposition the output for irregular LED walls.
The MVP remembers your choices **per display**, fingerprinting each one by its EDID. The next time you plug the same TV, projector, or processor back in, your saved resolution and on-screen geometry are reapplied automatically, even if you've traveled between venues.
***
### Where to Find It
1. Click the **gear icon** in the top-right corner of any page in the MVP web interface.
2. Select **System** to open the System Settings dialog.
3. Expand the **Display Settings** panel (monitor icon).
The panel header shows a short summary of the currently active mode. For example, `1920×1080 @ 60 Hz`. So you can see at a glance whether the display is configured the way you expect.
If no display is connected, the panel shows **"No display connected. Plug in HDMI to configure resolution and** [**display calibration**](/6.-configuration/display-settings/display-calibration)**."** All controls become available as soon as HDMI is detected.
***
### What You'll See When a Display Is Connected
At the top of the panel, the MVP shows:
* **Detected**: The display's manufacturer/product name as reported in its EDID (e.g., "Samsung 4K TV"). Shows "Unknown" if the display doesn't report a name.
* **EDID**: The first 8 characters of the SHA-256 fingerprint of the EDID block. This uniquely identifies the connected display and is what the MVP uses to look up saved settings.
Below that is the **Mode** selector. A single radio group with three mutually exclusive options.
***
### Mode: Auto (Recommended)
**Auto** uses the display's preferred mode. The resolution and refresh rate the display itself reports as its native, best-looking configuration. This is the default for any newly-connected display.
In almost every case you should leave this set to **Auto**. Modern TVs and projectors advertise their native panel resolution as the preferred mode, so leaving the MVP on Auto guarantees a pixel-perfect, full-screen image with no scaling.
Pick **Auto** when:
* You're plugging in for the first time and want to verify the display works.
* You travel between venues and want each one to "just work" without manual tuning.
* The display's native mode is what you want, which is almost always.
***
### Mode: Advanced
**Advanced** reveals two dropdowns populated from the modes the display itself reports in its EDID:
* **Resolution** — every resolution the display supports, largest first (4K, 1080p, 720p, etc.)
* **Refresh** — every refresh rate the display supports at the selected resolution
Below these is a toggle:
* **Show legacy & interlaced modes** — off by default. When on, the dropdowns also list older VESA timings and interlaced modes (480i, 1080i, etc.), with a small tag showing the source (DTD / Std / CEA).
Use **Advanced** when:
* You want to lock the MVP to a specific resolution or refresh rate (e.g., 1080p @ 24 Hz for cinema content).
* The display is reporting a non-standard preferred mode and you'd rather use something different.
* You want a lower resolution to for a downstream device.
> ⚠ **Warning**: Selecting a mode the display claims to support but does not actually drive cleanly may result in loss of signal. If you lose signal, the MVP automatically reverts to the previous working mode after 15 seconds. Do not unplug or power-cycle the device.
***
### Mode: Forced (Universal Override)
**Forced** reveals a single dropdown of hard-coded safe modes that are independent of what the display claims to support. The list is:
| Mode |
| ------------------- |
| 1920 × 1080 @ 60 Hz |
| 1920 × 1080 @ 30 Hz |
| 1280 × 720 @ 60 Hz |
| 1280 × 720 @ 30 Hz |
| 3840 × 2160 @ 30 Hz |
These are the most broadly-compatible video modes. Almost every HDMI device will accept one of them. Use **Forced** when:
* A projector or processor has a broken EDID and reports the wrong native mode.
* You're routing through a switcher or scaler that needs a specific input timing.
A forced mode is **universal**: The MVP applies it regardless of which display is connected, including across hotplugs. Saved per-display profiles are ignored as long as a forced mode is active. To return to per-display behavior, switch back to **Auto** or **Advanced**.
***
### Applying Changes
The Display Settings panel is **explicit-apply**. Changing the radio button or a dropdown updates the local form but does *not* push to hardware until you click the **Apply** button that appears in the bottom-right of the panel.
Most mode changes take less than a second. You may see a brief black flash on the display while the HDMI link re-initializes.
***
### Display Profiles
The MVP creates a profile file for every display it sees, keyed by the EDID hash. These profiles store:
* Your chosen mode (Auto / Advanced / Forced reference)
* Your [Display Calibration](/6.-configuration/display-settings/display-calibration) geometry: where on the physical display the video is positioned
***
### Status Display & Dashboard
The Dashboard's **HDMI** card and the front-panel Status Display both show the currently active resolution and the connected device name. After a mode change, these update within a second to reflect the new state. A quick way to confirm a change took effect.
***
### Related Pages
* [Display Calibration](/6.-configuration/display-settings/display-calibration) — Reposition and resize the video output on the physical display
* [System Settings](/6.-configuration/system-settings) — Other device-level preferences (LCD brightness, LED, MIDI CC trigger)
* [Hardware Connections & Specs](/1.-getting-started/hardware-connections-and-specs) — HDMI port details
* [Show Day Checklist](/9.-show-day/show-day-checklist) — Verifying display output at the venue
# Display Calibration
Visually position and resize the video output on the physical display. For LED walls, scrims, and video processors.
**Display Calibration** is a visual tool for positioning and resizing the MVP's video output on the physical display. It exists for one main use case: **mapping the output onto irregular or non-standard surfaces** — LED walls, projection scrims, video processors that expect a specific window within a larger canvas, or any scenario where "full-screen at native resolution" isn't what you actually want on the wall.
Like [Display Settings](/6.-configuration/display-settings), every calibration setting is stored **per display** and automatically reapplied when the same display is reconnected.
***
### Where to Find It
1. Open **System Settings** (gear icon → System).
2. Expand the **Display Settings** panel.
3. Click the **Display Calibration…** button.
> The Display Calibration button is enabled only when an HDMI display is connected. If nothing is plugged in, connect a display first.
***
### The Calibration Canvas
The dialog is dominated by a large interactive canvas representing the connected display.
* **Outer rectangle** — the physical display, drawn at its full resolution and aspect ratio.
* **Inner blue rectangle** — the output rectangle. This is where the video actually appears on the display.
A small label in the dialog header shows the canvas size (the display's current resolution). The header label updates if you change the resolution from Display Settings and re-open the calibration dialog.
#### Manipulating the Output Rectangle
You can adjust the inner rectangle three ways:
1. **Drag the body** — click anywhere inside the rectangle and drag to move it around the display. The rectangle is constrained to the display bounds.
2. **Drag a corner handle** — the four square handles at the corners scale the rectangle. With **Lock aspect** on (default), corners scale proportionally; with it off, each corner moves independently.
3. **Drag an edge pill** — the four thin blue pills on each side resize along a single axis. With **Lock aspect** on, dragging an edge also scales the perpendicular axis proportionally about the rectangle's center.
The on-screen video updates **only when you release the mouse,** not during the drag.
#### Inspector Panel
To the right of the canvas is a numeric inspector with four fields:
* **X** / **Y** — top-left position of the output rectangle, in display pixels
* **Width** / **Height** — size of the output rectangle, in display pixels
You can type values directly, or hover over a field and scroll the mouse wheel:
* **Scroll wheel** — adjusts by ±1 per tick
* **Shift + scroll wheel** — adjusts by ±10 per tick
After a burst of scrolling stops for \~200 ms, the change is pushed to the display.
Below the inputs, two status lines show:
* **Aspect** — the rectangle's current aspect ratio (e.g., `16:9`). Turns orange and shows "(stretched)" when the rectangle's aspect ratio differs from the display's, which means the video will be horizontally or vertically distorted.
* **Coverage** — the percentage of the display's area covered by the output rectangle.
***
### Toolbar Buttons
Below the canvas:
| Button | What It Does |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Reset to 100%** | Returns the output rectangle to fill the entire display (no scaling, no offset). |
| **Match {aspect}** | Centers a rectangle of the display's own aspect ratio. When the display is, say, 16:9 and you've stretched the rectangle to 4:3, clicking **Match 16:9** restores a full-display 16:9 rectangle. Disabled when the rectangle is already a full-display match. |
| **Lock aspect** | Toggles aspect-ratio locking for drag operations. On by default. With lock on, corner and edge drags preserve the rectangle's current aspect ratio. With lock off, every handle moves independently. |
***
### Applying Changes
The dialog has two action buttons at the bottom:
* **Cancel** — discards your changes and reverts the on-screen output to the previously-saved geometry.
* **Apply** — saves the current geometry to the display's profile and confirms the new output position. The button is disabled until you've made a change.
When you click **Apply**:
1. The geometry is persisted to the display's profile file.
2. A snackbar confirms "Display calibration saved."
3. The dialog closes.
The change has **already been applied to the screen** during your last drag/release or scroll burst — clicking Apply is what makes it permanent. If you close the dialog with Cancel after making changes, the screen reverts to the saved state.
***
### How the MVP Maps Video onto the Output Rectangle
The video frame is always mapped onto the full output rectangle you've drawn — the rectangle is purely a destination, not a crop. Whatever the video resolution is, the MVP stretches or shrinks it to fit your rectangle exactly.
This means:
* A 1920×1080 video shown in a 960×540 rectangle is scaled down 2× in each axis. No content is lost.
* A 1920×1080 video shown in a 1920×540 rectangle is squashed vertically — the same image, half as tall. Aspect ratio is stretched.
* An LED wall that takes its input from an HDMI source but only uses, say, the left 1200 pixels of a 1920×1080 signal — set the output rectangle to `X=0, Y=0, Width=1200, Height=1080` and the video fills exactly that area.
If you want the video to fill some part of the display without stretching, use **Lock aspect** while you drag, and the rectangle will always preserve the video's aspect.
***
### Related Pages
* [Display Settings](/6.-configuration/display-settings) — Resolution and refresh rate selection
* [System Settings](/6.-configuration/system-settings) — Open the gear menu to reach this dialog
* [Show Day Checklist](/9.-show-day/show-day-checklist) — Verifying display geometry at the venue
# 7. Networking
## 7. Networking
Connect your MVP to Wi-Fi for updates and stock video downloads, configure Ethernet for ArtNet lighting output, and troubleshoot IP conflicts.
***
#### In This Section
* [**Wi-Fi Setup**](/7.-networking/wifi-setup) — Connect to wireless networks for updates and remote access
* [**Ethernet & ArtNet Configuration**](/7.-networking/ethernet-and-artnet-configuration) — Configure wired networking and DMX-over-IP
* [**IP Range Conflicts**](/7.-networking/ip-range-conflicts) — Resolve subnet conflicts between Wi-Fi and ArtNet
# WIFI Setup
Connect your MVP to Wi-Fi for MVP updates, stock video downloads, device registration, and remote UI access.
***
## Wi-Fi Status Indicator
The top bar of the MVP web interface always shows a **Wi-Fi icon**:
* **Wi-Fi connected**: Default icon color, tooltip shows "Connected to WiFi: {SSID}"
* **Wi-Fi disconnected**: Red icon, tooltip shows "Connect to WiFi"
Click this icon to open the Wi-Fi dialog.
***
## Connecting to Wi-Fi
1. Click the **Wi-Fi icon** in the top bar.
2. The dialog opens and **automatically scans** for available networks.
3. Click the network you want to join.
4. If the network requires a password and you haven't connected before, a **password prompt** appears. Enter the Wi-Fi password and click OK.
5. A spinner appears on the network row while the connection is being established.
6. Once connected, the network row becomes elevated/bold and a **DISCONNECT** button appears.
If the network has been connected before (saved profile), clicking it reconnects **without** prompting for a password.
***
## Wi-Fi Dialog Details
Each network in the list shows:
| Field | Description |
| ------------------------ | ---------------------------------------------------------- |
| **Network Name (SSID)** | The Wi-Fi network name |
| **Signal Strength Icon** | Wi-Fi bars icon (1-4 bars based on signal quality) |
| **Security Type** | Security protocol (e.g., WPA2) |
| **Rate** | Connection speed |
| **Signal %** | Numeric signal strength percentage |
| **Bookmark Icon** | Appears on saved networks that are not currently connected |
***
## Actions
| Action | How |
| -------------- | ------------------------------------------------------------------------- |
| **Connect** | Click any network row |
| **Disconnect** | Click the **DISCONNECT** button on the connected network |
| **Re-Scan** | Click **RE-SCAN** in the dialog title bar |
| **Forget** | Click the **bookmark icon** on a saved network (confirms before removing) |
### Password Validation
Passwords are validated: WPA2 requires **8-64 characters** of printable ASCII. If the password is wrong or the connection fails, you'll see a **"Failed to connect to {SSID}"** error message.
### Forget Network
When you forget a network, the MVP deletes the saved password. A confirmation dialog appears before it is removed.
***
## Scanning Feedback
* A **spinning indicator** appears in the title bar during network scanning.
* Scanning is triggered automatically when the dialog opens, and can be manually triggered with the **RE-SCAN** button.
***
## Remote Access via Wi-Fi
Once connected to Wi-Fi, access the MVP's web interface from any device on the same network:
1. Find the MVP's Wi-Fi IP address (shown on the Dashboard Wi-Fi card, or on the physical Status Display)
2. On any device connected to the **same Wi-Fi network**, navigate to that address:
Anytime your MVP is powered on and connected to your WIFI router, you can use that IP address in your browser
***
## When Do You Need Wi-Fi?
| Feature | Wi-Fi Required? |
| ----------------------- | ------------------------------- |
| MVP Feature updates | Yes (or Ethernet with internet) |
| Stock video downloads | Yes (or Ethernet with internet) |
| Device registration | Yes (or Ethernet with internet) |
| Remote UI access | Yes (or Ethernet) |
| Video/lighting playback | No |
| MIDI triggering | No |
| ArtNet output | No (uses Ethernet) |
| Timecode sync | No |
***
## Status Display
The physical Status Display on the MVP shows your Wi-Fi connection status on the HOME screen:
* **Connected**: Shows the SSID and IP address
* **Not Connected**: Shows "NOT CONNECTED" in red text
***
## Security Recommendations
* **Use a private network** when possible. Avoid open/public Wi-Fi at venues.
* The MVP's web interface is accessible to anyone on the same network.
* For performances, you can disconnect Wi-Fi entirely -- it is not needed for playback.
***
## Tips
* **Wi-Fi is not required for shows**: Once configured, the MVP operates entirely over USB and Ethernet. Wi-Fi is only needed for updates and downloads.
* **Venue Wi-Fi can be unreliable**: Consider using a mobile hotspot from your phone if you need internet access at a venue.
* **IP address may change**: If the MVP reconnects to Wi-Fi after a reboot, the DHCP-assigned IP address may change if connecting to different Wi-Fi routers. Check the Dashboard or Status Display for the current IP.
***
## Related Pages
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Wired network setup
* [IP Range Conflicts](/7.-networking/ip-range-conflicts) -- Resolving Wi-Fi/Ethernet subnet conflicts
* [Updating Your MVP](/1.-getting-started/updating-your-mvp) -- Firmware updates (requires internet)
# Ethernet & ArtNet Configuration
The MVP's Ethernet port serves two purposes: **ArtNet output** (DMX lighting over network) and **wired network access** if necessary (browser UI, RTP-MIDI). This page covers Ethernet IP configuration for both use cases.
***
## Accessing Ethernet Settings
1. Click the **Settings gear** icon in the top-right corner of the web interface.
2. Select **"Ethernet | Artnet"**.
The dialog title is "Ethernet | Artnet" and contains two tabs for switching between DHCP and Static modes.
***
## DHCP vs. Static IP
### DHCP (Automatic)
The MVP requests an IP address from a DHCP server on the network (e.g., your router). All fields are populated automatically and **cannot be edited**. A **Refresh** button is available to renew the DHCP lease.
* **Best for**: Internet access, RTP-MIDI, situations where ArtNet isn't being used
### Static IP (Manual)
You manually specify the IP address, subnet mask, and optional gateway.
* **Best for**: ArtNet operation (ArtNet requires predictable IPs on a specific subnet)
**Fields:**
| Field | Description | ArtNet Recommended |
| --------------- | --------------------------------------------------- | ------------------ |
| **IP Address** | The MVP's Ethernet IP | `2.0.0.111` |
| **Subnet Mask** | Network mask | `255.0.0.0` |
| **Gateway** | Router address (optional -- leave blank for ArtNet) | *(blank)* |
Click **Apply IP Settings** to save. Changes are **not** auto-saved -- you must explicitly click the button.
> **Tip**: For ArtNet playback, leave the Gateway field blank.
### Cable Disconnected
If no Ethernet cable is connected, all controls are **disabled**. The dialog indicates the cable is unplugged and the fields cannot be edited until a cable is detected.
***
## What Happens When You Change Ethernet Settings
When you apply a new IP configuration (or switch between DHCP and Static), the MVP automatically updates its ArtNet output and network configuration to use the new settings. This takes a few seconds. You do not need to reboot. ArtNet output resumes on the new network automatically.
***
## ArtNet Configuration
### How ArtNet Output Works
The MVP broadcasts ArtNet data on its Ethernet interface:
* **Up to 16 universes** simultaneously (Universe 0-15)
* **UDP broadcast** to the network's broadcast address
* **Port 6454** (standard ArtNet port)
The MVP automatically determines the correct broadcast address based on your IP and subnet settings.
ArtNet nodes on the same subnet receive these broadcasts and convert them to DMX output.
### Standard ArtNet IP Range
The Art-Net protocol traditionally uses the **2.x.x.x** IP range:
| Device | IP Address | Subnet |
| --------------- | ---------- | --------- |
| **MVP** | 2.0.0.111 | 255.0.0.0 |
| **ArtNet Node** | 2.x.x.x | 255.0.0.0 |
All devices on the ArtNet network must share the same subnet.
***
## USB-ArtNet Passthrough
When recording DMX from lighting software running on your computer, ArtNet data travels over the USB-C connection:
1. Your lighting software sends ArtNet data to the MVP over USB-C
2. The MVP bridges the ArtNet traffic out through the Ethernet port
3. Your ArtNet nodes receive the data -- you can record and preview simultaneously without a network switch
This works automatically with both Mac and Windows computers. The MVP detects your computer type and handles the routing. When the MVP is playing its own DMX clips, the USB-ArtNet Passthrough automatically pauses.
> *For full recording setup:* [*Recording ArtNet -- Lighting Software*](/3.-lighting-setup/recording-artnet-lighting-software)
***
## USB-C Host Status
The Dashboard shows a **USB-C Host** status card indicating:
* Whether a host computer is connected
* The host type (Mac or PC)
* The MVP's USB IP address
* The host computer's IP address
This is useful for verifying the USB-ArtNet passthrough connection.
***
## Related Pages
* [Wi-Fi Setup](/7.-networking/wifi-setup) -- Wireless network configuration
* [IP Range Conflicts](/7.-networking/ip-range-conflicts) -- Resolving Wi-Fi/Ethernet subnet conflicts
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- DMX clip setup
* [Recording ArtNet -- Lighting Software](/3.-lighting-setup/recording-artnet-lighting-software) -- USB-ArtNet recording
* [Recording ArtNet -- Lighting Desk](/3.-lighting-setup/recording-artnet-lighting-desk) -- Console-based recording
# IP Range Conflicts
The MVP warns you when your Wi-Fi and Ethernet connections share the same IP subnet. This page explains why it matters and how to fix it.
***
## What Is the Problem?
When both Wi-Fi and Ethernet are connected and share the same network subnet, the operating system can't reliably determine which network interface to use to communicate with the MVP. This specifically affects **ArtNet output.** The ArtNet broadcast may be routed incorrectly.
***
## How Conflict Detection Works
The MVP compares the **network ranges** of both interfaces. If they overlap, a conflict exists.
For example:
* **Ethernet**: 192.168.1.111 / 255.255.255.0 → network 192.168.1.0
* **Wi-Fi**: 192.168.1.50 / 255.255.255.0 → network 192.168.1.0
* **Result**: Same network address → **Conflict detected**
The conflict warning appears **only** when **all** of these conditions are true:
1. Ethernet **is connected** (cable plugged in)
2. Ethernet is in **Static** mode
3. Wi-Fi **is connected**
4. Both interfaces have valid IP and subnet values
5. The computed network addresses are **equal**
The warning does **not** appear when:
* Only one interface is connected
* Ethernet is in DHCP mode
* The interfaces are on different subnets (e.g., Wi-Fi on 192.168.1.x, Ethernet on 2.0.0.x)
***
## How the Warning Is Displayed
When a conflict is detected, an **"IP Range Warning"** button appears in the Ethernet dialog with an information icon.
Clicking the warning button opens a secondary dialog titled **"ArtNET IP Range Warning"** that explains:
* ArtNet/DMX users should take action; others can safely ignore the warning
* "Your Ethernet and Wi-Fi connections are both on the same IP range/subnet, which can prevent ArtNET playback from working properly."
The dialog then presents recommended solutions.
***
## How to Fix It
### Use the Standard ArtNet Range (Recommended)
Set the Ethernet to the standard Art-Net IP range, which doesn't conflict with typical Wi-Fi networks:
| Field | Value |
| --------------- | --------------- |
| **IP Address** | 2.0.0.111 |
| **Subnet Mask** | 255.0.0.0 |
| **Gateway** | *(leave blank)* |
This is the recommended approach for ArtNet operation. The 2.x.x.x range is the traditional Art-Net standard and is extremely unlikely to conflict with any Wi-Fi network.
## Related Pages
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Full Ethernet setup guide
* [Wi-Fi Setup](/7.-networking/wifi-setup) -- Wi-Fi configuration
* [Troubleshooting](/8.-reference/troubleshooting) -- Other common issues
# 8. Reference
Quick-reference material, supported formats, and solutions for common issues.
***
#### In This Section
* [**MIDI Reference** ](/8.-reference/midi-reference)— Channel assignments, note mappings, and CC numbers
* [**Supported Video Formats**](/8.-reference/supported-video-formats) — Codecs, containers, resolutions, and frame rates
* [**Troubleshooting**](/8.-reference/troubleshooting) — Common issues and solutions for video, lighting, MIDI, and connectivity
* [**FAQ**](/8.-reference/faq) — Frequently asked questions
* [**MVP Release Notes**](/8.-reference/mvp-release-notes) — Version history and what's new
# MIDI Reference
A complete reference for all MIDI notes, CC messages, and channels used by the MVP.
***
## MIDI Channels
| Channel | Default Assignment | Configurable? |
| -------------------- | ------------------------------------- | ------------------------------ |
| **Video Channel** | Channel 1 (MIDI channel 0 internally) | Yes (1-16, in System Settings) |
| **Lighting Channel** | Channel 3 (MIDI channel 2 internally) | Yes (1-16, in System Settings) |
Video and Lighting channels are configured independently. Channels are reloadable at runtime -- changing the setting takes effect immediately.
***
## MIDI Notes -- Clip Triggers
Sent on the **Video** or **Lighting** MIDI channel:
| Note | Action |
| ----------- | ---------------------------------------------------------------------------------------------------------- |
| **0** | **Blackout** -- Video: loads blank video (black screen) / Lighting: loads DMX blackout (all channels to 0) |
| **1-99** | Trigger the clip assigned to that note number |
| **100** | *(unused)* |
| **101** | **Previous** -- step to the previous non-empty assignment in the active slot (video or lighting channel) |
| **102** | **Next** -- step to the next non-empty assignment in the active slot (video or lighting channel) |
| **103-109** | *(unused)* |
| **110** | Reset ALL Effects Mode properties to defaults (video channel only) |
| **111** | Reset Brightness to 0 (video channel only) |
| **112** | Reset Contrast to 1.0 (video channel only) |
| **113** | Reset Hue to 0 (video channel only) |
| **114** | Reset Saturation to 1.0 (video channel only) |
| **115** | Reset Rotation Z to 0 (video channel only) |
| **116** | Reset Scale to 1.0 (video channel only) |
| **117** | Reset Translation X to 0 (video channel only) |
| **118** | Reset Translation Y to 0 (video channel only) |
| **119-126** | *(unused)* |
| **127** | **Config Reload** -- Video channel: reload video config / Lighting channel: reload lighting config |
### Note Handling Details
* **Velocity**: Any velocity > 0 triggers the clip. The specific velocity value does not matter.
* **Velocity 0**: Treated as Note Off and ignored.
* **Note Off**: Completely ignored -- the MVP does not respond to Note Off messages.
* **Re-trigger**: Sending the same note while a clip is playing restarts it from the beginning.
* **Timecode suppression**: When timecode is active, MIDI note triggers for video and DMX are suppressed.
* **Transport debounce**: Notes 101 and 102 are debounced at **300 ms per direction** to absorb accidental double-triggers. Prev and Next debounce independently.
* **Transport scope**: Prev/Next always wrap within the **currently active configuration slot** and never cross into another slot. Empty assignments are skipped.
***
## MIDI CC -- Effects Mode Controls
Sent on the **Video** MIDI channel only. Requires **Effects Mode** (transform video mode) to be active.
| CC # | Control | Default Value | Behavior |
| ------ | ------------- | --------------- | -------------------------------------------------------- |
| **48** | Brightness | 64 (normal) | 0 = darkest, 64 = normal, 127 = brightest |
| **49** | Contrast | 64 (normal) | 0 = minimum, 64 = normal, 127 = maximum |
| **50** | Hue | 64 (normal) | 0 = full shift left, 64 = normal, 127 = full shift right |
| **51** | Saturation | 64 (normal) | 0 = grayscale, 64 = normal, 127 = oversaturated |
| **52** | Rotation Z | 0 (no rotation) | 0 = no rotation, 127 = full 360° rotation |
| **53** | Scale X/Y | 64 (100%) | 0 = smallest, 64 = normal size, 127 = 200% zoom |
| **54** | Translation X | 64 (centered) | 0 = far left, 64 = centered, 127 = far right |
| **55** | Translation Y | 64 (centered) | 0 = far up, 64 = centered, 127 = far down |
Effects are grouped into two categories:
* **Color adjustments**: Brightness, Contrast, Hue, Saturation (CC 48-51)
* **Spatial transforms**: Rotation Z, Scale, Translation X/Y (CC 52-55)
***
## MIDI CC -- Slot Switching
Sent on the **Video** or **Lighting** MIDI channel:
| CC # | Value | Action |
| ------- | ----- | ------------------------------------- |
| **119** | 10 | Switch to Slot A |
| **119** | 20 | Switch to Slot B |
| **119** | 30 | Switch to Slot C |
| **119** | 40 | Switch to Slot D |
| **119** | 50 | Switch to Slot E |
| **119** | 0 | *(ignored -- common DAW reset value)* |
**Important details:**
* CC #119 on the **video** channel switches the **video** slot only
* CC #119 on the **lighting** channel switches the **lighting** slot only
* **Only the exact values above are accepted** -- values like 11, 25, or 35 are silently ignored
* If the requested slot is already active, the switch is silently skipped
* **Timecode does NOT support CC #119 slot switching** -- timecode slots can only be changed from the UI
***
## MIDI CC -- CC Trigger Mode
Must be enabled in [System Settings](/6.-configuration/system-settings) (CC Trigger Mode toggle).
Sent on **either** the Video or Lighting MIDI channel:
| CC # | Value | Action |
| ------- | ------- | ---------------------------------------- |
| **110** | 1-99 | Trigger the clip assigned to that number |
| **110** | 100 | Trigger blackout (maps to note 0) |
| **110** | 0 | *(ignored -- default/off value)* |
| **110** | 101-127 | *(ignored -- out of range)* |
> **Warning**: Do not use with faders or knobs (continuous controllers) -- use buttons only. Each distinct value fires a clip change immediately.
***
## MIDI Note Numbering Conventions
Different DAWs and controllers use different octave numbering. The MVP uses raw MIDI note numbers (0-127). Here's how they map across common conventions:
| MIDI Note # | C-2 Convention | C-1 Convention | C3 Convention |
| ----------- | -------------- | -------------- | ------------- |
| 0 | C-2 | C-1 | C-2 |
| 12 | C-1 | C0 | C-1 |
| 24 | C0 | C1 | C0 |
| 36 | C1 | C2 | C1 |
| 48 | C2 | C3 | C2 |
| 60 | C3 | C4 | C3 |
> **Tip**: If you're unsure which note number your controller is actually sending, check the MVP Dashboard's **Input Monitor** -- it always shows the raw MIDI note number regardless of naming convention.
***
## MIDI Machine Control (MMC)
Received via any MIDI input when MTC is active (SysEx and timing messages are unfiltered):
| MMC Command | Effect |
| --------------- | -------------------------------------------------------- |
| **Stop** | Freeze video on current frame, lighting holds last state |
| **Play** | Resume playback from current or pending Locate position |
| **Pause** | Same as Stop -- freezes current state |
| **Locate/GoTo** | Seek to specific timecode position |
***
## MTC Routing
MTC messages are handled separately from regular note/CC messages:
* **Timecode data**: Continuous timecode tracking for synchronized playback
* **Position jump**: Sent when your DAW scrubs or locates, provides immediate absolute position
* **Transport commands (MMC)**: Stop, Play, Pause, and Locate for controlling the MVP's playback state
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Assign clips and channels
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Assign DMX clips and channels
* [Effects Mode](/2.-video-setup/effects-mode) -- CC 48-55 real-time controls
* [CC Trigger Mode](/5.-triggering/midi-cc-trigger-mode) -- CC #110 clip triggering
* [Configuration Slots](/6.-configuration/configuration-slots) -- CC #119 slot switching
* [MIDI Transport (Prev / Next) ](/5.-triggering/midi-transport-prev-next)-- Notes 101/102 in detail
* [Autoplay](/6.-configuration/autoplay) -- Automatic advance using the same logic
# Supported Video Formats
A complete reference for all file formats supported by the MVP for video playback and lighting output.
***
## Video Files
### Supported Codecs
| Codec | Common Names | Notes |
| --------- | ------------------- | ------------------------------------------------------------------ |
| **H.264** | AVC, MPEG-4 Part 10 | Most widely used. Best compatibility. Recommended. |
| **H.265** | HEVC | Better compression than H.264. Same quality at smaller file sizes. |
| **VP8** | WebM Video | Open format by Google. Less common. |
| **VP9** | WebM Video 2 | Successor to VP8. Good compression. |
| **MJPEG** | Motion JPEG | Each frame is a JPEG image. Large files but simple decoding. |
All supported codecs are **hardware-accelerated** for smooth playback.
### Supported Containers
| Extension | Format | Upload Accepted |
| --------- | ------------------- | --------------- |
| **.mp4** | MPEG-4 Part 14 | Yes |
| **.mov** | Apple QuickTime | Yes |
| **.m4v** | iTunes/Apple MPEG-4 | Yes |
| **.mkv** | Matroska Video | Yes |
| **.webm** | WebM (VP8/VP9) | Yes |
### Still Images
| Extension | Format | Behavior |
| --------- | ------ | ----------------------------------------------- |
| **.jpg** | JPEG | Displayed as a persistent still image on screen |
| **.jpeg** | JPEG | Same as .jpg |
Still images are triggered and assigned exactly like video files. The image persists on screen until another clip is triggered or blackout is sent.
### Resolution Limits
| Mode | Max Resolution | Notes |
| ----------------------- | -------------------------- | ---------------------------------------- |
| **Fast Trigger** | Up to 4K (3840x2160) | Recommended for most use cases |
| **Effects (Transform)** | 1080p (1920x1080) at 60fps | 4K videos are not supported in this mode |
### Audio in Video Files
The MVP **does not play audio** from video files. Audio streams are ignored during playback.
The 3.5mm audio input is used exclusively for LTC (timecode) reception.
### All-Intra Encoding
For [timecode synchronization](/4.-timecode-setup/timecode-overview), videos should be encoded with **GOP=1** (All-Intra) for frame-accurate seeking. The MVP can convert files on-device using its built-in hardware encoder, or you can export with GOP=1 from your editing software.
See [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) for details, or the [All-Intra Export Guide](/4.-timecode-setup/exporting-all-intra-from-editing-software) for instructions on exporting GOP=1 from your editing software.
### Filename Requirements
* **Allowed characters**: Letters (a-z, A-Z), numbers (0-9), dashes (-), underscores (\_), dots (.), spaces
* **Not allowed**: Special characters, emoji, non-ASCII characters
* Files with invalid characters are **rejected** during upload.
***
## Storage Capacity
The MVP has **100GB** of internal storage.
Approximate capacity by content type:
| Content | Estimated Capacity |
| ---------------------------------- | ------------------ |
| 4K video (H.264, \~30 Mbps) | \~10 hours |
| 1080p video (H.264, \~10 Mbps) | \~27 hours |
| 1080p All-Intra (H.264, \~50 Mbps) | \~5 hours |
| Still images (JPEG, \~5 MB each) | \~20,000 images |
| DMX clips (16 universes) | Thousands of clips |
***
## Related Pages
* [Video Configuration](/2.-video-setup/video-configuration) -- Upload and assign videos
* [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) -- GOP=1 encoding for timecode
* [Lighting Configuration](/3.-lighting-setup/lighting-configuration) -- Record and assign DMX clips
# Troubleshooting
Common issues and solutions for the MVP.
***
## Video Issues
### No video output on the display/projector
1. **Check HDMI connection**: Ensure the HDMI cable is firmly seated in both the MVP and your display.
2. **Check the Dashboard**: Navigate to `http://mvp.local` and look at the **HDMI** status section. It should show "Connected" with the device name, resolution, and framerate.
3. **Check the Status Display**: The physical LCD on the MVP shows HDMI connection status on the HOME screen. If it shows "NOT CONNECTED," the HDMI cable isn't detected.
4. **Try a different HDMI cable**
5. **Check display input**: Make sure your projector/display is powered up and set to the correct HDMI input.
6. **Trigger a clip**: The MVP starts with blackout. Send a MIDI note or press a keyboard key to trigger a clip.
***
### Video stutters or drops frames
* **4K in Effects Mode**: Effects Mode is limited to **1080p 60fps**. 4K videos will not play in this mode.
* **Corrupt file**: Try re-uploading the video file.
***
### Video only fills part of the screen, or is offset
The display's saved calibration geometry is wrong for this screen — usually because the profile was carried over from a display of a different resolution.
Open **System Settings → Display Settings → Display Calibration…**, click **Reset to 100%**, then **Apply**.
> *See:* [*Display Calibration*](/6.-configuration/display-settings/display-calibration)
***
### A clip advances instead of freezing / looping at the end
**Autoplay is on.** Autoplay overrides both the system-wide Playback Option and any per-clip Loop Mode Override. Turn off **System Settings → Autoplay → Video**, or accept that this clip will advance.
> *See:* [*Autoplay*](/6.-configuration/autoplay) *|* [*Loop Mode Override*](/2.-video-setup/loop-mode-override)
***
## Lighting / DMX Issues
### No DMX output to fixtures
1. **Check Ethernet**: Ensure an Ethernet cable connects the MVP to your ArtNet node. Check the Dashboard **Ethernet** status card for IP info.
2. **Check ArtNet IP range**: The MVP and your ArtNet node must be on the same subnet. The standard ArtNet range is `2.x.x.x` with subnet `255.0.0.0`. See [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration).
3. **Check universe mapping**: Ensure your ArtNet node is listening on the same universe(s) the clip was recorded on (0-15).
4. **Trigger a clip**: DMX output starts when a clip is triggered. Send a MIDI note on the lighting channel (default: Channel 3) or use Shift+key on a USB keyboard.
5. **Check for dual-source conflict**: If both the MVP and your lighting software/console are broadcasting ArtNet on the same universe, fixtures receive conflicting data causing a "glitch" effect. Stop or mute your lighting software before testing MVP playback.
### DMX output looks wrong ("glitch" effect)
If your fixtures are flickering or showing unexpected behavior, check whether **both** the MVP and your lighting desk are broadcasting ArtNet simultaneously. When two sources send ArtNet, fixtures receive conflicting data frame-by-frame.
**Solution**: Disconnect the lighting desk's ethernet cable, or disable artnet in your lighting desk's settings before testing MVP playback.
### Recorded clip doesn't match the original
DMX clips record raw channel values. If you change your fixture setup (different fixtures, different DMX addresses), the same channel values produce different results. Re-record clips for the new fixture configuration.
### Recording produces an empty clip
If a recording completes but the MVP shows "No DMX data received," check that:
* Your ArtNet source is actively broadcasting
* The ArtNet source is on the same subnet as the MVP
***
## Browser / Connection Issues
### Browser won't load `mvp.local`
1. **Wait 10-15 seconds** after connecting USB. The MVP needs time to load.
2. **Try the direct IP**:
* Mac: `http://192.168.3.1`
* Windows: `http://192.168.2.1`
3. **Clear DNS cache**:
* Mac: `sudo dscacheutil -flushcache` (in Terminal)
* Windows: `ipconfig /flushdns` (in Command Prompt)
4. **Try a different browser**.
5. **Check USB cable**: Try a different USB-C cable. Not all USB-C cables carry data (some are charge-only). Use the HOST USB-C port, not the power-only port.
### DAW doesn't see the MVP as a MIDI device
1. **Check USB connection**: The MVP must be connected via the **HOST** USB-C port.
2. **Re-plug the cable**: Disconnect and reconnect the USB cable, then restart your DAW.
3. **Try a different USB port** on your computer.
### "Session Conflict" overlay appears
Another browser tab is already connected to the MVP. The MVP only allows one controlling browser at a time.
* Click **"Take Over"** to claim the session from the other browser tab.
* Or close the other browser tab first.
***
## MIDI Issues
### MIDI notes aren't triggering clips
1. **Check the Dashboard Input Monitor**: Are MIDI events appearing? If not, the MVP isn't receiving MIDI at all (connection issue).
2. **Check MIDI channel**: The note must arrive on the correct channel. Video clips respond to the video channel (default: 1), lighting to the lighting channel (default: 3).
3. **Check note numbers**: Verify the note number matches an assigned clip (1-99). Note 0 is blackout. The Dashboard Input Monitor shows the exact note number received.
4. **Check Sync**: Did you click **"Sync Changes to Playback"** after making assignment changes on the Video or Lighting page?
5. **Timecode active?**: When timecode is driving playback, MIDI note triggers are **suppressed**.
### MIDI octave numbering confusion
Different DAWs and controllers number octaves differently. "C3" in one DAW might be a different MIDI note number than "C3" in another.
The MVP uses raw MIDI note numbers (0-127). Always check the Dashboard **Input Monitor** to see the actual note number -- don't rely on note name labels.
See the [MIDI Reference](/8.-reference/midi-reference) for a note numbering comparison table.
### Effects faders (CC 48-55) aren't working
1. **Check video mode**: Effects controls only work in **Effects Mode**, not Fast Trigger Mode. Check [System Settings](/6.-configuration/system-settings).
2. **For APC Mini/MK2**: Each fader requires its **toggle button** to be activated first. Press the corresponding toggle button above each fader (notes 64-71 on v1, notes 100-107 on MK2) to enable the fader. The toggle LED will blink when active.
3. **Check channel**: Effects CCs only work on the **video** MIDI channel. Sending CC 48-55 on the lighting channel has no effect.
***
## Power Issues
### MVP doesn't turn on via USB
* **Not all USB ports provide enough power**: Some computers limit USB-C power output. Try:
1. A different USB port on your computer
2. Connecting the MVP **first** (before other USB devices)
3. Disconnecting other USB devices
4. Using a powered USB hub
* **Use the DC adapter as backup**: Connect the included power adapter to the barrel jack for reliable power, even alongside the USB connection.
### MVP reboots or behaves erratically
* **Insufficient USB power**: The most common cause. Use the DC power adapter alongside USB for stable operation, especially if running USB controllers on the USB-A ports.
***
## Update Issues
### "Update failed" or update process hangs
* **Do NOT power off** during an update. If the update is still in progress (progress bar moving), wait for it to complete.
* **Try again**: If the download failed, retry the update from the Update dialog.
* **Contact support**: If you're having problems getting the update, contact `support@4cast.world`.
***
## Network Issues
### Wi-Fi and Ethernet on the same subnet (IP conflict)
The MVP warns you when Wi-Fi and Ethernet share the same IP subnet. This can prevent ArtNet output from reaching your fixtures.
See [IP Range Conflicts](/7.-networking/ip-range-conflicts) for detailed resolution steps.
***
## Timecode Issues
### Timecode not syncing
1. **LTC**: Check the Dashboard Input Monitor for LTC signal meters. The LTC Volume meter should show green at a moderate level (-20dB to -1dB). Below -40dB is treated as no signal.
2. **MTC**: Check that your DAW's MTC output is routed to the MVP and that MTC/Sync is enabled (not just MIDI note output).
### Timecode drops or loses sync
* If the timecode signal is briefly interrupted, the MVP continues playing smoothly
* If the signal is lost for longer then one second, playback pauses (video goes to black, lighting holds last state)
* When signal returns, the MVP verifies the signal and resumes sync automatically
* Check cable quality, audio levels (LTC), or MIDI routing (MTC)
***
## Still Stuck?
* **Check the Dashboard**: The Input Monitor, HDMI status, Ethernet status, and Wi-Fi status cards provide real-time diagnostic information.
* **Check the Status Display**: The physical LCD shows connection status, MIDI events, and timecode at a glance.
* **Contact support**: Email `support@4cast.world` with a description of the issue and screenshots of the Dashboard.
* **Read through this site**: Check to make sure you're doing everything correctly, as documented.
***
## Related Pages
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard) -- Real-time system monitoring
* [Hardware Connections & Specs](/1.-getting-started/hardware-connections-and-specs) -- Port reference
* [MIDI Reference](/8.-reference/midi-reference) -- Note and CC mapping
* [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration) -- Network setup
# FAQ
Frequently asked questions about the MVP.
***
### What is the MVP?
The MVP (Multimedia Visual Performer) is a hardware device that triggers video playback and DMX lighting clips from MIDI signals, USB keyboard input, or timecode. It is designed for live performances -- concerts, touring productions, worship services, theatre, corporate events, and any scenario where video and lighting need to be triggered reliably and instantly.
***
### What comes in the box?
* MVP unit in a travel case
* USB-C to USB-A cable
* USB-C to USB-C cable
* DC power adapter
* 4x M2 mounting screws (VESA compatible)
***
### How much storage does the MVP have?
100GB of internal storage with 10GB reserved for system operations (90GB usable for your content).
| Content Type | Estimated Hours |
| ----------------------- | --------------- |
| 4K video (H.264) | \~10 hours |
| 1080p video (H.264) | \~27 hours |
| 1080p All-Intra (H.264) | \~5 hours |
Actual capacity depends on codec, bitrate, and compression.
***
### What video formats are supported?
* **Codecs:** H.264, H.265, VP8, VP9, MJPEG
* **File types:** .mp4, .mov, .m4v, .mkv, .webm
* **Still images:** .jpg, .jpeg (displayed as persistent stills)
* **Max resolution:** Up to 4K
See [Supported File Formats](/8.-reference/supported-video-formats) for full details.
***
### Does the MVP play audio?
No. The MVP does not play audio from video files. The MVP plays video only -- audio streams in video files are ignored during playback. The 3.5mm audio input is used exclusively for LTC (timecode) reception.
***
### What is DMX / ArtNet?
**DMX** (DMX512) is the standard protocol for controlling stage lighting fixtures -- setting brightness, color, position, and other parameters by sending values (0-255) on numbered channels.
**ArtNet** is a protocol that carries DMX data over Ethernet networks instead of dedicated DMX cables. The MVP outputs ArtNet data on its Ethernet port, which an ArtNet node converts to DMX for your fixtures.
The MVP supports up to **16 DMX universes** (8,192 channels) simultaneously.
***
### Do I need a computer to use the MVP?
No. The MVP can operate standalone with just a MIDI controller (USB or 5-pin DIN) or USB keyboard for triggering. You'll need a computer to access the web UI for configuration, but once configured, the MVP runs independently.
You'll need the DC power adapter when running without a computer (USB-C from a computer provides both power and data).
***
### How do I stop video/lighting playback?
Send **MIDI Note 0** on the video or lighting channel. This is the dedicated **blackout** command:
* **Video**: Loads a blank video (black screen)
* **Lighting**: Loads the DMX blackout clip (all channels to 0)
Stopping your DAW does **not** automatically stop the MVP playback. It continues playing the last triggered clip. You can also use CC #110 with value 100 (if CC Trigger Mode is enabled) to trigger blackout.
***
### Can I restart a clip from the beginning?
Yes. Triggering the same MIDI note while a clip is already playing restarts it from the beginning instantly.
***
### How long does setup take?
Basic setup (connect, upload videos, assign to MIDI notes, trigger from a DAW) takes **under 10 minutes**. The [Quick Start Guide](file:///5753738/Quick-Start/quick-start-guide.md) walks through it.
More complex setups with timecode sync, lighting, and multiple slots take longer depending on your show complexity.
***
### What hardware do I need alongside the MVP?
**Required:**
* HDMI display (for video output)
* MIDI source: computer with DAW, MIDI controller, or USB keyboard
**For lighting:**
* ArtNet node (converts ArtNet to DMX)
* Ethernet cable
* DMX fixtures
**For timecode:**
* LTC source + 3.5mm audio cable, or MTC source + MIDI connection
***
### Can I use the MVP with multiple displays?
The MVP has a single HDMI output. For multiple displays, use an HDMI splitter or video distribution amplifier. All displays show the same content.
***
### Can I control video and lighting independently?
Yes. Video and lighting use separate MIDI channels (configurable, default: video on Channel 1, lighting on Channel 3), separate configuration slots (A-E), and separate clip assignments. You can trigger video and lighting simultaneously with different clips on each channel. Slot switching via CC #119 is also independent per channel.
***
### What is All-Intra encoding? Do I need it?
All-Intra encoding (GOP=1) makes every frame a complete image, enabling frame-accurate seeking. You **need it for timecode synchronization** (so the MVP can jump to any exact frame). You **don't need it for regular MIDI triggering** (clips always start from the beginning).
All-Intra files are **2-5x larger** than standard encoding. The MVP can convert files on-device using its built-in hardware encoder (H.265), or you can export with GOP=1 from your editing software.
See [All-Intra Video & Timecode Sync](/4.-timecode-setup/all-intra-videos) for details.
***
### What does the physical Status Display show?
The Status Display on the front of the MVP has three views:
* **HOME**: HDMI status, Ethernet IP, Wi-Fi SSID, firmware version
* **LIVE MIDI**: Last triggered note/key for video and lighting, playing filename, with flash animation
* **LIVE TC**: SMPTE timecode clock (7-segment display), FPS status, playing files
The view switches automatically based on activity. Notifications appear for HDMI/MIDI device connections.
***
### How often are MVP updates released?
Updates are released several times per year with new features and improvements. The MVP checks for updates when connected to Wi-Fi and shows a notification in the Dashboard when one is available. The Status Display also shows a pulsing "UPDATE AVAILABLE" banner.
***
### Why is the MVP a hardware device and not software?
**Reliability for live shows.** The MVP is a dedicated appliance that:
* Loads to a known state every time
* Doesn't share resources with other applications
* Won't be interrupted by OS updates, notifications, or other software
* Has hardware-acceleration with minimal latency
* Can be powered from a single USB cable and fits in your pocket
A laptop running video software can do similar things, but a dedicated device eliminates the variables that cause live show problems.
***
### How big is the MVP?
The MVP measures **1.25" x 6" x 3.3"** (H x W x D) -- about the size of a smart phone, but thicker. It fits easily in any bag. The unit is VESA compatible with the included M2 screws for permanent mounting.
***
### Where can I get help?
* **Documentation**: You're reading it!
* **Email**:
***
## Related Pages
* [Quick Start Guide](/quick-start-guide-videos) -- Get started in 5 minutes
* [Troubleshooting](/8.-reference/troubleshooting) -- Common issues and solutions
# MVP Release Notes
### Version 1.3.3
*Release Date: 2026-08-04*
You asked, We listened. The MVP's **"Summer Update"** is packed with the requested features you've all been asking for, as well as number of performance and stability improvments
**Autoplay** ([learn more](/6.-configuration/autoplay))
Turn the MVP into a sequential playback server. Enable Autoplay for Video, Lighting, or both, and the device advances to the next clip in the active slot at the end of every cue. No triggering, no operator, no laptop. Still images auto-advance after 5 seconds, and the show starts automatically at boot.
**MIDI Transport — Prev / Next** ([learn more](/5.-triggering/midi-transport-prev-next))
Two hardcoded notes — **101 (Previous)** and **102 (Next)** — step through the assignments in the active configuration slot. Empty assignments are skipped, stepping wraps within the slot, and a 300 ms debounce absorbs accidental double-triggers.
**Display Settings & Display Calibration** ([learn more](/6.-configuration/display-settings))
* **Resolution & refresh rate control** — Auto (use the display's preferred mode), Advanced (pick any mode the display reports), or Forced (five universally-compatible timings that bypass EDID entirely).
* **Display Calibration** — a visual tool for positioning and resizing the video output anywhere on the screen surface, for LED walls, projectors, and video processors.
* **Per-display profiles** — the MVP fingerprints each display by EDID and reapplies your resolution and geometry automatically on reconnection. Set each venue up once.
**Loop Mode Override** ([learn more](/2.-video-setup/loop-mode-override))
Set **Loop**, **Freeze**, or **Blank** behavior on an individual video, overriding the system-wide playback option. The override is saved with the file, so it follows the clip between MIDI notes, slots, and timecode timelines.
**Effects Mode: Crossfade (Beta)** ([learn more](/2.-video-setup/effects-mode/effects-mode-crossfade))
Effects Mode can now crossfade between clips instead of cutting, with a configurable 0.1–5.0 second fade. Blackout fades too. Timecode playback stays instant for frame accuracy.
**Network MIDI Interface Setting** ([learn more](/6.-configuration/network-midi-interface))
Choose whether **Ethernet** or **Wi-Fi** advertises the MVP's RTP-MIDI session.
**Performance and Stability Improvements**
* Resolved an edge-case power behavior when operating via a dedicated PSU.
* Improved upload stability, and speed for Safari users.
* Improved USB-C Host hotplugging stability.
***
### Version 1.3.1
*Release Date: 2026-05-20*
Welcome to our **"Spring Update"**. Continuing the 4CAST mission of providing intuitive and powerful professional production tools, this release brings major enhancements to your show control capabilities. Version 1.3.1 introduces full SMPTE timecode synchronization alongside a built-in NLE timeline editor, expands your playback flexibility with new MIDI CC and USB keyboard triggering options, and delivers key UI improvements including a native Dark Mode, resumable file uploads, and a complete LCD display makeover.
**Timecode Show Control** ([learn more](https://support.4cast.world/4.-timecode-setup/timecode-overview))
Full SMPTE timecode synchronization with a built-in NLE timeline editor for frame-accurate show playback.
* [**New Timeline Editor**](https://support.4cast.world/4.-timecode-setup/the-timeline-editor) — Drag-and-drop media onto the timeline. Save up to 5 show configurations/slots.
* **LTC & MTC** — Continuous sync and variable-speed tracking for DAWs, CDJs, and more.
**New Triggering Options**
* [**MIDI CC Trigger Mode**](https://support.4cast.world/5.-triggering/midi-cc-trigger-mode) — Use MIDI CCs just like MIDI notes to trigger your media.
* [**USB HID Keyboards**](https://support.4cast.world/5.-triggering/usb-keyboards-hid) — Use any standard USB keyboard or numpad and trigger your media with the press of a key.
**UI Improvements**
* **Dark mode** — Full dark theme, now the default. Toggle in the app bar.
* **Resumable uploads** — Large file uploads survive page navigation and connection drops.
* **LCD display makeover** — The small screen now shows all connection states and details, and all real-time actions.
***
### Version 1.2.2
*Release Date: 2025-12-20*
* **Bug Fix: SLOT Configuration:** Resolved an issue where changing the active slot via MIDI and then editing a different slot in the UI could overwrite the active slot’s configuration.
***
### Version 1.2.1
*Release Date: 2025-11-17*
Celebrating our **"Thanksgiving Update"**, this release adds a number of really great new features and UI refinements that you've all been asking for. We also have some major new features in the works for the upcoming "Spring Update", so definitely stay tuned.
> **Video Overview:** [4CAST MVP v1.2 New Features Overview](https://www.youtube.com/watch?v=jZflx3PwS1M)
#### New Features & Improvements
* **Free Stock Video Downloads:** Search through half a million royalty-free stock videos, and download them directly to your MVP within seconds.
* **Expanded Cue Capacity:** Now supports up to **500** video and lighting cue assignments (slots/banks), giving you far more flexibility for complex shows.
* **Name & Save Configurations:** Save and recall labeled slot/bank configurations. Switch in the UI, or on the fly with MIDI CC.
* **More Video Formats Supported:** Video Codecs include H.264 / H.265 / MJPEG / VP8 / VP9. Video Files include .mp4 .mov .mkv .webm.
* **Still Image Support:** Upload and use JPEG images in your show.
* **Detailed Video File Info:** Now shows video codec, file type, resolution, framerate, and duration.
* **Record DMX over USB‑C:** Record DMX directly via USB‑C without the need for an Ethernet switch or extra cables.
* **Various UI Improvements**
***
### Version 1.1.2
*Release Date: 2025-08-05*
#### Bug Fixes
* **ArtNet / Ethernet Settings:** Added IP range conflict detection between Ethernet and Wi-Fi connections.
***
### Version 1.1.1
*Release Date: 2025-07-03*
Continuing the 4CAST mission of providing intuitive professional-level video and lighting production tools, this release expands ArtNET recording and playback to 16 universes, introduces a new Effects Mode for video playback controlled via MIDI CC, delivers a real-time Dashboard for device status, supports larger video uploads (up to 60 GB), adds flexible MIDI channel assignments, and includes performance improvements.
#### New Features
* **Beta Feature: Effects Mode:** MIDI CC control of 4 color effects and 4 transformation effects. Enable via *Settings Cog > Beta Features* in the UI. Assign to knobs, faders, or DAW for detailed, timed effects. More effects to come in future updates. *Note: 4K files are not supported in Effects Mode.*
* **New Dashboard – Real-time Device Status:** Includes "Currently Playing" clip name and playtime, real-time ArtNet viewer with all universe DMX data, WiFi/Ethernet connection status and IP details, HDMI connection status, display name, resolution, and framerate. Also features an Input Monitor for incoming MIDI notes and LTC timecode frames, and an MVP Version & Notification area showing available updates.
* **Lighting – Up to 16 Universes**
* **Assignable MIDI Channels:** Configurable, no longer locked to Channel 1 and 3.
* **Sync Changes to Playback Button:** Immediately syncs changes to the playback engine.
* **Reactive UI Updates:** Pages show which clip is currently playing.
* **Larger Video Uploads:** Up to 60 GB per file.
* **UI Single Session Enforcement:** Prevents conflicts when multiple tabs are open.
#### Improvements & Bug Fixes
* **Critical Bug Fix:** Prevents bricking from repeated failed boots due to underpowered USB ports.
* **Various minor bug fixes.**
* **Playback performance improvements.**
***
### Version 1.0.8
#### Bug Fixes
* **Lighting:** Fixed bug introduced in v1.0.6 where DMX clips would not trigger unless HDMI was connected at least once.
***
### Version 1.0.6
#### Bug Fixes
1. HDMI hotplug minor bug fix.
2. Ethernet Settings static IP minor bug fix.
***
### Version 1.0.5
#### Improvements & Bug Fixes
1. **DMX/Artnet: Playback Timing Fix:** Fixed a bug where ArtNet playback could drift out of sync over time. *Note: DMX Clips recorded with v1.0.1 will no longer be playable and should be deleted/re-recorded.*
2. **Wi-Fi:** Fixed issue with mixed mode WPA2/WPA3 connections.
3. **Ethernet Connection Dialog:** Now indicates when Ethernet cable is disconnected.
4. **Register MVP Dialog:** Registration now works over Ethernet connections.
5. **Various minor bug fixes.**
# 9. Show Day
You've configured your videos, lighting, and triggers — now it's time to set up at the venue. This section provides a step-by-step checklist for load-in
***
#### In This Section
* [**Show Day Checklist**](/9.-show-day/show-day-checklist) — Step-by-step venue setup from load-in to showtime
# Show Day Checklist
A practical guide for setting up the MVP at a venue on show day.
***
## 1. Load-In / Physical Setup
* [ ] Unpack the MVP from the travel case
* [ ] Position the MVP near your other gear
* [ ] Connect **HDMI** to your display or projector
* [ ] Connect **Ethernet** to your ArtNet node (if using lighting)
* [ ] Connect **USB-C** to your computer (HOST port) or **DC adapter** (standalone)
* [ ] Connect **MIDI** (USB-A controller, 5-pin DIN cable, or USB keyboard)
* [ ] Connect **3.5mm audio cable** (if using LTC timecode)
### Verify Power
* [ ] The physical Status Display (LCD) lights up and shows the HOME screen with HDMI, ETH, WIFI, and version info
* [ ] The blue status LED is solid blue
* [ ] The web interface loads at `http://mvp.local` (or direct IP)
***
## 2. Signal Confirmation
### HDMI
* [ ] Check Dashboard **HDMI card**: shows device name, resolution, and framerate
* [ ] Check Status Display HOME screen: HDMI row shows resolution (e.g., "1080p60") and device name
* [ ] Trigger a test clip and verify video appears on the display/projector
### MIDI
* [ ] Check Dashboard **Input Monitor**: trigger a note from your controller/DAW
* [ ] Verify the correct MIDI note number appears in the event log
* [ ] Check the Status Display: it should switch to LIVE MIDI view showing the triggered note
* [ ] Verify clips trigger correctly on both video and lighting channels
### Lighting / ArtNet
* [ ] Check Dashboard **Ethernet section**: correct IP and subnet (standard: 2.0.0.x / 255.0.0.0)
* [ ] Trigger a test DMX clip on the lighting channel
* [ ] Verify fixtures respond correctly
### Timecode (if applicable)
* [ ] **LTC**: Check Dashboard Input Monitor for the LTC Volume meter (green, -20dB to -1dB) and Frames Decoded meter (green, near 100%)
* [ ] **MTC**: Check Dashboard Input Monitor for MTC frame events appearing in the log
* [ ] Verify the SMPTE timecode display is running smoothly
* [ ] Check that the frame rate matches your configured rate (no "Framerate Mismatch" warning chip)
* [ ] Let the timecode run through at least one clip boundary to verify automatic file loading and sync
* [ ] The Status Display should switch to LIVE TC view showing the 7-segment timecode clock
***
## 3. Display Verification
* [ ] Set display/projector to the correct input
* [ ] Disable any display "eco" or auto-sleep modes -- the MVP may output black during gaps, which some displays interpret as "no signal"
* [ ] Disable motion interpolation / frame smoothing (adds latency)
* [ ] Enable "Game Mode" if available (minimizes processing delay)
* [ ] If using a projector, check keystone and focus
* [ ] **First time at this venue?** Open **System Settings → Display Settings** if you need to adjust the resolution, and **Display Calibration** if you need to adjust the position of the output on the screen surface. Both are stored per display, so return visits auto-apply.
***
## 4. Run-Through
### Full Show Test
* [ ] Verify all clip triggers match your set list
* [ ] If using timecode, let it run through the complete timeline if possible
* [ ] Verify slot switching works if using multiple slots (via CC #119 or the UI)
* [ ] Test blackout (Note 0) on both video and lighting channels
* [ ] Test clip re-trigger (same note restarts from beginning)
* [ ] Is your backup trigger method ready? (USB keyboard, a second controller, etc.)
***
## 5. Pre-Show
* [ ] Disconnect Wi-Fi if not needed (reduces potential interference, prevents update notifications)
* [ ] Verify correct slot is selected (A-E) for video, lighting, and timecode
* [ ] Trigger a blackout on both channels to start clean
***
## Quick Troubleshooting
| Issue | Quick Fix |
| ---------------------------------------- | ----------------------------------------------------------------------------- |
| **No video output** | Check HDMI cable and display input; check Dashboard HDMI card; trigger a clip |
| **No DMX output** | Check Ethernet cable and IP subnet; verify ArtNet node is on same network |
| **MIDI not responding** | Check MIDI channel; verify note number in Dashboard Input Monitor |
| **Timecode not syncing** | Check audio level (LTC: -20dB to -1dB) or MIDI routing (MTC) |
| **Display went to sleep** | Re-trigger a clip; disable display auto-sleep mode |
| **Wrong clips playing** | Check active slot (A-E); verify "Sync Changes to Playback" was applied |
| **Display shows only part of the video** | → Display Calibration → Reset to 100% → Apply |
> *Full troubleshooting:* [*Troubleshooting*](/8.-reference/troubleshooting)
***
## Related Pages
* [The MVP Dashboard](/1.-getting-started/the-mvp-dashboard) -- Real-time monitoring during the show
* [Troubleshooting](/8.-reference/troubleshooting) -- Detailed issue resolution
---
[Next Page](/llms-full.txt/1)
