> 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/resources-archive/quickstart/ltc-configuration-beta.md).

# LTC Configuration (Beta)

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 %}


---

# 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/resources-archive/quickstart/ltc-configuration-beta.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.