> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/introductory-presentation/closing-the-presentation/adjusting-the-timing-of-the-transition.md).

# Adjusting the timing of the transition

When you use the Fade to Color IFX, it’s important to understand when the fades will occur. The fade-in starts when the playhead reaches the IFX, and the fade-out starts after the playhead passes the IFX.

<figure><img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-283ff6cf70031ba3b8a7a51b4c6421fbc23a8e6a%2Ffade_transition.jpg?alt=media&amp;token=ffda107f-2ce6-4499-b5d5-ab8157fd17ab" alt=""><figcaption><p>Transition times</p></figcaption></figure>

Between the end of the fade-in and the start of the fade-out, a user’s screen will be filled with the solid color that you’ve chosen.

By default, IFX are added to the timeline with a length of 30 seconds. This means that currently you will have 29.5 seconds of a black screen. To make the transition more reasonable, complete the following steps:

* Go to the effect options for the *Fade to Color* IFX, and then set the End Time to be 2 seconds after the Start Time.


---

# 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://docs.engagevr.io/engage/experience-editor/tutorials/introductory-presentation/closing-the-presentation/adjusting-the-timing-of-the-transition.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.
