Client-side feeds support for all Tizen Players
We're changing the way in which Tizen Players interpret MRSS feeds - with the introduction of client-side feeds, MRSS content can now be synced in a JSON format to Tizen Players. This provides many benefits, from reducing the number of times our cloud needs to sync with an MRSS feed to detect changes, to Nested Playlists being able to play back content in a truly randomized order.
Historically, with Players that did not support client-side feeds, we have converted MRSS content within our cloud and served it up to a Player as a Playlist. The disadvantage of this process meant that setting the playback order to "Random" on Nested Playlists resulted in the same random order every loop.
Migration to the NENA endpoint [Tizen 2.4 Players only]
As per our previous communications, due to a change concerning Signagelive's Global Root Certificate, our primary endpoints will be changing. Part of this process involves us moving some of our older supported Players onto the NENA endpoint (including older versions of LG webOS and Tizen) meaning that if you have one of these Players you will need to ensure they can reach the relevant IPs and domains. Please ensure the following endpoints are reachable by your Players:
Tizen 2.4 players will ‘fall back’ to using the default URLs if the NENA endpoints are blocked. This ensures the NENA migration update does not break players which don’t have the NENA endpoints whitelisted yet.
Changes to Widget SDK:
Implementation of downloadFile, getDownloadedFile, removeDownloadedFile, listDownloadedFiles and clearDownloadedFiles
Fix for playVideo SDK method where if you set loop to false in the widget, it was still looping on the media player itself.
Fix for listDownloadedFiles SDK method where it wasn’t resolving this information to the full filepath.
Further changes where “public” location information has been updated to be more secure.