Skip to main content
All CollectionsKnown & Ongoing IssuesCurrent Issues
Samsung Tizen (Nested/Local Playlists used in Sync Groups not currently supported)
Samsung Tizen (Nested/Local Playlists used in Sync Groups not currently supported)
Ian Maison avatar
Written by Ian Maison
Updated yesterday

TL:DR - Too long, didn't read...

We know this issue impacts the use of Samsung Tizen panels, Sync and Nested/Local Playlists; there is a short-term workaround that is outlined below ("The Immediate Solution"). Our Development Team is prioritizing a fix in our next 1.32 Tizen client, scheduled for a February 2025 release.

The Latest as of mid-January 2025

Our Development Team has deployed support for Nested/Local Playlists and player synchronisation in the upcoming 1.32 Tizen client which is currently undergoing thorough regression testing by our QA Team. After these test results are in, next steps will be planned accordingly. It is imperative this client build undergoes extensive testing as it will be released on a global scale to all Samsung panels running the current 1.31 client.

The Current Limitation

Our Technical Team is aware of the issue affecting Samsung Tizen panels, where the combinations of Sync Groups and Nested/Local Playlists is not supported. When this combination of configurations is used, synchronisation will unfortunately not work.

Met Criteria:

Synchronisation will not work when the following elements are used in combination:

  • Samsung Tizen Player (Any version)

  • Sync (As configured through Signagelive)

  • Nested or Local Playlists (Client Side Feeds)

The Immediate Solution

For now, the only solution is to remove the use of Nested and Local Playlists from your scheduling, placing all media content in a single playlist. Doing so will immediately ensure that content synchronization works smoothly. We appreciate and acknowledge that in some cases this will not be a simple change, so if you require any guidance or support please reach out to our Support Team.

The Overall Solution

Rest assured, we’re aware of the issue, and our Development Team is already on it. We're committed to resolving this in the next Tizen Client 1.32, which we expect to release early in 2025, pending successful development and QA. Thank you for your patience!

Did this answer your question?