# 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.md)
***
## 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.md), 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.md) for configuration.
***
## Related Pages
* [Timecode Overview](/4.-timecode-setup/timecode-overview.md) -- LTC vs. MTC comparison and sync capabilities
* [The Timeline Editor](/4.-timecode-setup/the-timeline-editor.md) -- Building your timecode show
* [LTC (Audio Timecode) Setup](/4.-timecode-setup/ltc-audio-timecode-setup.md) -- 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.md) -- Frame-accurate seeking for timecode
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://support.4cast.world/4.-timecode-setup/mtc-midi-timecode-setup.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.