Synchronized playback across players (PiSignage 5.6.0)
Make every player in a group show the same playlist item at the same moment, with one group setting.
Sync works on PiSignage 5.6.0 players within about one second, with no cabling, master player or extra server traffic. It suits screens that should look like one display: lobby banks, side-by-side menu boards, corridors of portrait screens, or retail shelves advertising the same product. For a short version see Quick start - Sync playback across players.
Each player follows its own clock, so players do not talk to each other. A rebooted player rejoins the others where they are.
What to expect:
- Players switch to the next image or video within about 0.3 to 1 second of each other.
- A player that boots, changes playlist or returns from an advert joins mid-item and seeks into the running video.
- Shuffle still works. All players use the same shuffled order, which changes every cycle.
- It is not a frame-accurate video wall. Splitting one video across screens needs dedicated hardware.
Sync also works across groups, as long as their playlists have the same duration in every row, in the same order. The assets can differ. Shuffle must be off for this, because the shuffled order comes from file names and would differ between playlists.
Requirements
| Requirement | Details |
|---|---|
| Player software | 5.6.0 or later on every player in the group. Older players ignore the setting |
| Server | pisignage.com, or a self-hosted server updated alongside 5.6.0, since the group setting must exist on the server |
| Clock | Each player must reach an NTP server, through normal internet or a local NTP server. A player with an unsynchronized clock plays unsynchronized until fixed |
| Playlist type | A regular playlist in the group's default or scheduled slot. Event, play-once and keypress playlists play outside the timeline, and the regular playlist then rejoins it |
| Playlist rows | Images, videos, web pages and widgets with fixed durations. No .mrss feed rows and no .local folder rows |
| Video settings | Time to stop video must stay at 0, because chunked playback cannot follow fixed slots |
| Video player | VLC or Chromium for mid-video joins. The GStreamer runner (mpv) joins at the start of the video |
| Content | The same playlist deployed to all players in the group, since players only match when rows and durations match |
Raspberry Pi boards have no battery-backed clock, so they rely on NTP after every boot. On networks that block outbound NTP, use a local NTP server. Players check timedatectl every minute and log when sync is gained or lost.
Every player works out the timeline itself, so there is no limit on group size and no extra server load.
Which content types take part
Any fixed-duration row takes a time slot, so players switch to and from it together. The difference is whether a player joining mid-slot can catch up inside the item.
| Content | Behaviour |
|---|---|
| Images, text, PDF pages | Synchronized. Switch together at the slot boundary |
| Video files (mp4, mkv) | Synchronized. A player joining mid-slot seeks to the same point on VLC and Chromium |
| HTML pages, web links, templates, widgets | Synchronized as a slot. Everything inside the page (animation, scrolling, clocks) runs on the page's own timing and is not aligned |
| YouTube videos | Synchronized with a larger offset. Stream address resolution can add a few seconds on first play. Mid-slot joins seek on VLC only. Not suitable where sub-second alignment matters |
| RTSP, UDP and live TV streams | Not applicable. The stream is live anyway, and players open and close it together |
RSS and media RSS feeds (.mrss) |
Not synchronized. Varying item counts mean no fixed timeline. Sync is turned off for the whole playlist while one is present |
Cloud folders (.local) |
Not synchronized, for the same reason as feeds |
| Background audio rows | Synchronized. The row starts and the playlist advances immediately, without holding a slot |
Setting up synchronized playback
It is one switch on the group's Playback tab, then a deploy. It assumes your players are already registered and placed in a group (see Screens and Groups).
Step 1: Update players to 5.6.0
- Open Players (Screens) in the web interface.
- Check the version chip beside each player's name, ID and IP. Every participating player must show 5.6.0 or later.
- For an older player, select it and use Update player to 5.6.0. Wait for it to report back online with the new version.
Step 2: Put players in one group
- Open Groups and select the group, or create a new one.
- On the Screens tab, confirm every player that should stay in step is listed. Players in other groups are not affected.
Step 3: Build a playlist with fixed durations
- Open Playlists and create or edit the group's playlist.
- Give every image, web page and widget a duration. Videos use their own length.
- Do not add
.mrssor.localrows. They have no fixed length, and sync turns off for the entire playlist if one is present. - Save the playlist.
Step 4: Turn on Sync playback across players
- Open the group and select the Playback tab.
- In the Playback Options card, find Sync playback across players, just below Shuffle content. Its description says sync applies to all playlists except those with RSS feeds or cloud folders.
- Turn the switch on.
- On the group's Settings tab, leave Time to stop video at 0. Shuffle may stay on.
- Click Save Changes.
Step 5: Assign the playlist and deploy
- On the Playlists tab, set the playlist as the group's default, or add it to the schedule.
- Click Deploy. A toast at the bottom right reading "Deploy done successfully" confirms the players received the settings and content.
Step 6: Check the screens
Stand where two or more screens are visible. Within a minute they should show the same item and advance together. A player that is still downloading joins once its files are complete. A rebooted player joins mid-item, seeking into a video already playing elsewhere.
To check remotely, open Screen Details for two players of the group on the Screens page and keep their Feed tabs open side by side. Both should show the same item and advance together.
Optional: confirm from the player log
The player log at /home/pi/forever_out.log records when sync starts and which timeline it follows. Search it with:
grep -ia "Sync playback" /home/pi/forever_out.log
A healthy player logs its timeline:
Sync playback: 6 slots, cycle 95s, timeline id 3a9f1c2e
If sync is on but cannot apply, one warning names the reason, for example:
Sync playback is enabled but not applied: system clock is not NTP synchronized
How it works
Each player turns the playlist into a fixed timeline and checks its clock for the current slot. There is no master player, server tick or player-to-player messaging. A player already playing the current slot carries on. A player arriving mid-slot starts the same item and seeks the video to the same offset.
- Fixed slots: each row's slot equals its duration. Slots repeat back to back from a fixed point in time, so boot or deploy time does not matter.
- Same answer everywhere: the current slot depends only on the clock and the playlist rows. Players with the same rows and NTP-synced clocks agree.
- Slots end on time: an item ends at its slot's absolute end, so a slow start shortens that item rather than delaying later ones.
- Shared shuffle: with Shuffle on, the order is drawn from a seed built from the playlist and cycle number. All players get the same order, changing each cycle.
- Other playlists step aside: event, play-once and keypress playlists and adverts play as usual, and the regular playlist rejoins the timeline afterwards.
- Clock watch: the player checks NTP status at start and every minute. Without a synced clock it plays unsynchronized and rejoins once the clock is good.
Limitations and troubleshooting
Sync keeps screens within about a second of each other and applies only to the main zone of a regular playlist. Side, bottom and other zones, tickers and widgets run as before.
| Symptom | Cause and fix |
|---|---|
| Players drift or play in a different order | A player is below 5.6.0. Update it on the Screens page and deploy again |
| One player is out of step, log shows "system clock is not NTP synchronized" | No route to NTP, or the player just booted. Allow NTP through the firewall or set a local NTP server. It rejoins automatically once synced |
Log says a .mrss or .local row "has no fixed duration" |
A feed or cloud folder row is present. Move that content to another playlist or group |
| Log says "timeToStopVideo plays videos in chunks" | Time to stop video is set on the group. Set it to 0 on the Settings tab |
| Videos start from the beginning after reboot, not mid-video | The player uses the GStreamer runner (mpv), which cannot seek. Use VLC or Chromium |
| Videos no longer merge or loop | Expected while sync is on. Each video ends at its slot boundary |
| Two groups out of step | A row duration differs between playlists, or Shuffle is on. Match durations and order, turn Shuffle off. Assets can differ |
| Images match but video lags about a second | Start latency differs by player model. Expected, accuracy is roughly 0.3 to 1 s |
What sync is not:
- Not a video wall. Videos cannot span screens and frame-level alignment is not attempted.
- Not a replacement for identical hardware. Mixed models stay in step, but slower models start items a little later.
- Not applied to side zones of multi-zone layouts.