> 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/webos-gapless-playback.md).

# Gapless Playback webOS

It should be noted that gapless playback capabilities between Widgets will vary when:

* Widgets are added to play in a sequence.

  or
* Widgets are added to different Layouts to play one after the other when either scheduled as separate Layouts or included as part of a Campaign.

## Widgets set in Sequence

Widgets should be added after a Widget of the same type for best results:

* HTML
* HTML Package
* Image
* Local Video
* Video
* Video-In

However, there are still sequences where certain Widgets will show black frames as shown in the matrix below:

#### Sequence Matrix

| Widgets          | **HTML** | **HTML Package** | **Image** | **Local Video** | **Video** | **Video-In** |
| ---------------- | :------: | :--------------: | :-------: | :-------------: | :-------: | :----------: |
| **HTML**         |     ✅    |         ✅        |     ✅     |        ✅        |     ✅     |       ✅      |
| **HTML Package** |     ✅    |         ✅        |     ✅     |        ✅        |     ❌     |       ✅      |
| **Image**        |     ✅    |         ✅        |     ✅     |        ✅        |     ✅     |       ✅      |
| **Local Video**  |     ✅    |         ✅        |     ✅     |        ❌        |     ✅     |       ❌      |
| **Video**        |     ✅    |         ✅        |     ✅     |        ✅        |     ✅     |       ✅      |
| **Video-In**     |     ✅    |         ❌        |     ✅     |        ✅        |     ❌     |       ❌      |

The 1st column represents the Widget that is currently playing. The rows represent the next Widget to play in sequence.

✅- Successful transition expected for the Widget type in sequence.

❌- Black frames expected for this Widget type in sequence.

## Widgets added to Layouts

Different Widgets added to separate Layouts when scheduled to play one after the other or added to a Campaign will give best results if ordered to play after a Widget of the same Widget type.

There are still limitations to this which are detailed in the matrix below:

#### Layout Matrix

| Widgets          | **HTML** | **HTML package** | **Image** | **Local Video** | **Video** | **Video-In** |
| ---------------- | :------: | :--------------: | :-------: | :-------------: | :-------: | :----------: |
| **HTML**         |     ✅    |         ✅        |     ✅     |        ❌        |     ✅     |       ❌      |
| **HTML Package** |     ✅    |         ✅        |     ✅     |        ❌        |     ✅     |       ❌      |
| **Image**        |     ✅    |         ✅        |     ❌     |        ❌        |     ✅     |       ❌      |
| **Local Video**  |     ✅    |         ❌        |     ✅     |        ❌        |     ✅     |       ✅      |
| **Video**        |     ✅    |         ✅        |     ✅     |        ❌        |     ✅     |       ❌      |
| **Video-In**     |     ✅    |         ✅        |     ❌     |        ❌        |     ❌     |       ❌      |

The first column represents the Widget in a Layout that is currently playing . The first row represents the next Widget to play in the next Layout.

✅- Successful transition expected for the Widget type to play next .

❌- Black frames expected for this Widget type to play next.


---

# 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/webos-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.