> 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-fixture-group-tracks.md).

# Fixture Group Tracks

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

Fixture Group-Tracks are equal to the [Any Scene Tracks](https://syncronorm.atlassian.net/wiki/spaces/D2D/pages/48037940/Any+Scene+Track), but only store values for a specific fixture group, which will be selected automatically once the Track is selected. This Track covers the best workflows for lighting programming as it combines the group organization with tracking workflow programming.

To add a Fixture-Group Track navigate to your [Selection Groups](https://syncronorm.atlassian.net/wiki/spaces/D2D/pages/40927296/Selection+Groups) Window and drag a Group into the Track-View of the Timeline.

## **Draw Scene EventBlock**

The Fixture Group Track will directly pick the values, marked to store, from the Programmer:

1. Select your Track (which also select the fixture group).
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-fixture-group-tracks.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.
