> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-show-and-animation/depence-show-sequencer/depence-track-types/depence-any-scene-track.md).

# Any Scene Track

<div align="left"><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/py23pXGXeHKPRWGvSCBP/48398359.png" alt=""></div>

The Any Scene Track can hold different independent Scenes, which will be stored directly into the Show without any reference. So every block drawn represents a different scene. To add an Any Scene Track, right-click on the Track area of the timeline and select "New Any Scene Track".

## **Draw Scene EventBlock**

The Any-Scene Track will directly pick the values, marked to store, from the Programmer:

1. Select fixtures you want to create scenes for.
2. Make changes in the Programmer.
3. Draw into the Track with your left mouse button.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.depence.com/depence-show-and-animation/depence-show-sequencer/depence-track-types/depence-any-scene-track.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
