# 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. *** ## 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.md). 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.md) 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.md). 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.md) 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.md) -- Real-time system monitoring * [Hardware Connections & Specs](/1.-getting-started/hardware-connections-and-specs.md) -- Port reference * [MIDI Reference](/8.-reference/midi-reference.md) -- Note and CC mapping * [Ethernet & ArtNet Configuration](/7.-networking/ethernet-and-artnet-configuration.md) -- Network setup --- # 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/8.-reference/troubleshooting.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.