> For the complete documentation index, see [llms.txt](https://help.atlas-control.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.atlas-control.app/show-settings/triggers/timecode.md).

# Timecode

{% hint style="info" %}
To assign cues to a timecode selection please see: [cuelist](/main-overview/cuelist.md)
{% endhint %}

<figure><img src="/files/dCYlhnssRiBL9DOXw9vS" alt=""><figcaption><p>Show Settings - Timecode window showing options</p></figcaption></figure>

### Enable Timecode

Selecting this option will allow Atlas to be triggered via incoming Midi Timecode.&#x20;

Atlas supports these timecode standards.&#x20;

### Allow Timecode to move playhead

Selecting this option will allow incoming timecode to progress the playhead within the cue list.&#x20;

{% hint style="info" %}
This option can be useful for shows using both operator and musically fired cues. The operator can progress the playhead locally for cues outside of timecode.&#x20;
{% endhint %}

### Timecode Frame Rate

Select the desired timecode frame rate from the dropdown menu. Common formats are listed in the initial menu; a full list is available on the sub menu.&#x20;

{% hint style="danger" %}
If opening an existing show file or switching between timecode formats Atlas may display the error: "Malformed Timecode". This error informs the user that the programmed format needs attention in order to preserve the show.&#x20;
{% endhint %}

### Clamp all cues to a valid Timecode

Selecting this button will clamp all invalid timecode cues to the nearest value for the selected frame rate.&#x20;


---

# 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://help.atlas-control.app/show-settings/triggers/timecode.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.