> 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-repository/depence-scenes/scene-fade-delay-path.md).

# Scene Fade / Delay Path

With Fade / Delay Path settings, more complex scene calls such as "*Move in Black*" can be realized.\
A FadePath describes how a single channel behaves when fading in and out of a scene. The delay time and the fade-in time can be set as a percentage of the scene fade time.

The in-fade and out-fade behavior of each scene in the repository or within a sequence (show) can be adjusted individually for each parameter.

To do this, right-click on a scene button or in the Sequencer on the corresponding scene and then select "**Edit Scene Fade Path**".

<figure><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/gqdc7oUxAkhKLXEDhte4/image.png" alt=""><figcaption></figcaption></figure>

In the upper line, you can choose whether you want to set the fade behavior for the start or for the end of a scene.

Order by Fixture combines all the same function types of a scene. Changes to the Delay and Fade faders change the fader rate or delay rate of all the same functions.

<figure><img src="https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/eimuPTBnpaYQskS3V1Tp/image.png" alt=""><figcaption></figcaption></figure>

Order by Function shows all functions of all channels contained in the scene.

![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/4hXY8jwb5aZFcVTb3Uxz/image.png)

![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/rtUntJDUuC9US1bjKcOq/image.png)

{% hint style="danger" %}
The channel delay is used for effect runs and has no use for the fade path
{% 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 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-repository/depence-scenes/scene-fade-delay-path.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.
