> 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/playing-videos-on-ifx-screens/configuring-the-screen-for-the-presentation.md).

# Configuring the screen for the presentation

1. On the timeline, select the cog icon for the *Video Screen (Flat External URL)* IFX.
2. The second recording finishes speaking at around `00:02:27`, so enter this as the **Start Time**.
3. In the Video URL field, enter <https://unity-cdn.engagevr.io/engage_online_root/featured/vids/EngageTut/Engage_Presentation_01.mp4>
4. The video is 2 minutes 20 seconds in length. To ensure that the video is displayed only for as long as necessary, in the **End Time** field, enter `00:04:47`.
5. Select **Save Effect**.

Because the presentation is silent, the experience file includes an audio IFX that provides background music. It should now roughly align with the IFX screen on the timeline. Adjust the audio IFX on the timeline if required.

{% hint style="info" %}
An *External URL video* IFX update as you move the playhead. In contrast, videos played through the *Play Shared Screen Video* IFX update on screens only when you play the experience. External URL video IFX can therefore be useful if you want to synchronize other events to a video, such as animations.
{% 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://docs.engagevr.io/engage/experience-editor/tutorials/introductory-presentation/playing-videos-on-ifx-screens/configuring-the-screen-for-the-presentation.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.