--- title: "TV Playlists: Control What Each Screen Plays" description: "A **playlist** is the ordered list of layouts a device plays during normal playback. If a **layout** is one screen, a **playlist** is the loop that tells the TV: - which layouts to show - in what order to show them - how long each one…" url: "https://twinnoverse.com/docs/tv-playlists-control-what-each-screen-plays/" updated: "2026-06-18" category: Dashboard Builder / Dashboard Builder delivery --- # TV Playlists: Control What Each Screen Plays A **playlist** is the ordered list of layouts a device plays during normal playback. If a **layout** is one screen, a **playlist** is the loop that tells the TV: - which layouts to show - in what order to show them - how long each one stays visible --- ## 1. What a Playlist Does Each playlist defines: - the layouts included in playback - the sequence of those layouts - the duration of each layout in seconds Each device can be assigned to **one playlist at a time**. When the reader app is running on a claimed device, it uses the assigned playlist as its normal playback source. --- ## 2. When You Need a Playlist Use a playlist when: - one TV should rotate between multiple dashboards - the same dashboard set should be reused across devices - you want a stable default playback layer underneath campaigns and events If you only have one layout, you still usually place it in a playlist so the device has a normal playback source. --- ## 3. What You Need Before You Create One Before you build a playlist, make sure you already have: - at least one saved layout - a claimed device if you want to test playback on a real screen - the correct data source connected to the layouts that need live or manual data The playlist does not create layouts or data. It only controls playback. --- ## 4. Create a Playlist 1. Open **Playlists** from the admin shell. 2. Click **Create New Playlist**. 3. Enter a clear playlist name. 4. Add one or more layouts from the available list. 5. Arrange them in the order you want them to play. 6. Save the playlist. Choose names that describe the audience or area, for example: - `Operations` - `Warehouse North TVs` - `Reception Rotation` --- ## 5. Set Layout Durations Each playlist item has a duration. This controls how long that layout stays on screen before the playlist moves to the next item. Each item must have a duration greater than `0` seconds. Practical guidance: - short, urgent dashboards: 10 to 20 seconds - standard KPI boards: 20 to 60 seconds - detailed executive dashboards: 45 to 90 seconds - Think about viewing distance and reading speed: - simple KPI screens can rotate faster - dense tables and detailed charts usually need more time - if a screen is meant to stay up most of the time, use one layout in one playlist with a longer duration The total cycle time is the sum of all item durations. If a playlist has four layouts at `15` seconds each, the full loop takes about `60` seconds before it returns to the first layout. --- ## 6. Assign a Playlist to a Device 1. Open **Devices**. 2. Edit the target device. 3. Select the playlist from the device assignment field. 4. Save the device. The reader will use that playlist as its normal playback source. Important behavior: - the device must already be claimed - a device can only have one playlist assignment at a time - changing the assignment replaces the previous playlist for that device - clearing the assignment removes normal playlist playback from that device If a layout is deleted or no longer available, it will not be used in reader playback. --- ## 7. How Playlists Interact with Campaigns and Events The playlist is the **default layer**. - **Scheduled campaigns** can temporarily interrupt or overlay the playlist. - **Event-driven layouts** can temporarily interrupt or overlay the playlist. - When the campaign or event ends, playback returns to the playlist. This means you should treat the playlist as the baseline experience for the device. If you are designing the normal day-to-day screen, start with a playlist. If you need temporary interruption content, then add campaigns or event triggers on top of that baseline. --- ## 8. Best Practices ### Do - keep playlists focused on one audience or area - use clear names - test the total cycle time from the point of view of someone standing at the screen - keep one fallback playlist per area - keep related layouts together so the screen tells one consistent story ### Avoid - adding too many layouts to one playlist - mixing unrelated departments on the same playlist - using campaigns as a replacement for normal playlist planning - setting very short durations on layouts with dense content --- ## 9. Example A simple shopfloor setup might look like this: - `Layout 1`: production KPI summary for `20` seconds - `Layout 2`: downtime and alerts for `15` seconds - `Layout 3`: shift target vs actual for `15` seconds This creates a `50` second loop that repeats continuously on the assigned TV.