> For the complete documentation index, see [llms.txt](https://support.4cast.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.4cast.world/archive-v12-userguide/technical-archive/device-i-o.md).

# Device I/O

<details>

<summary>USB-C Host</summary>

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.).

</details>

<details>

<summary>HDMI Out</summary>

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.

</details>

<details>

<summary>Ethernet (ArtNet)</summary>

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.

</details>

<details>

<summary>5V 2A power (optional)</summary>

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.

</details>

<details>

<summary>MIDI In</summary>

Receive MIDI input from any MIDI controller or source.

</details>

<details>

<summary>USB-A x 2</summary>

Receive MIDI input from any MIDI controller or source.

</details>

<details>

<summary>1/8" In/Out</summary>

Audio in for LTC timecode triggers (beta). Audio out for future implementations.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://support.4cast.world/archive-v12-userguide/technical-archive/device-i-o.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.