> 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-audio-track.md).
# Audio Track
The Show Sequencer can also playback audio files synchronized to your show. To add an Audio Track right-click on the Track area and choose "New Audio Track".
## **Add Audio Files**
Audio files will be also organized within the Repository and once they are imported, they will be also copied into the Project folder to prevent dead file links, when sharing your project. See [Audio & Video Files](https://syncronorm.atlassian.net/wiki/spaces/D2D/pages/48103425). To add an existing audio file to the timeline, just drag the audio file from the Repository into the Audio Track.
### **Cut Left / Right**
If selected, an Audio Event Block can be cut with the help of the two vertical blue bars on each side. The audio output will now play from a later point of the audio stream or will be shortened at the end.
### **In Fade and Out Fade**
The audio output can be faded in or out with the help of the snap points above the audio Event Block.
---
# 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-audio-track.md?ask=&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.
