> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/player-app/gapless-playback.md).

# Gapless Playback

Xibo supports gapless playback for selected Player apps and supported hardware.

Content within a Playlist or schedule loop will play the 'next' item as the current one is finishing to create a gapless change between content, removing the brief black flash or flicker when a Layout reloads. Gapless playback is also supported for video content for selected Player apps.

{% hint style="info" %}
Android requires devices to support multiple decoders.
{% endhint %}

{% embed url="<https://docs.google.com/spreadsheets/d/e/2PACX-1vRMlLA1A40YBipC4Vx8bEjoQflGNy0AKtXa2Uc7e2UlZGnTvN5Mut7aTfbU9-6uAPvoZI3cbAc3Xdsm/pubhtml>" %}

If you experience issues with Gapless playback for videos, change the setting for multiple video decoders to On:

1. Click on **Display Settings** under the **Displays** section of the main CMS menu
2. Use the row menu for a **Display Profile**, click **Edit**
3. From the **Advanced** tab, scroll down to the **Use Multiple Video Decoders** field
4. Use the drop down menu and select **On**
5. Click to **Save**


---

# 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.xibosignage.com/kb/player-app/gapless-playback.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.