You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Xibo CMS version 4.*.*, modifying the duration of an image in the library does not reflect in playlists where the image has already been assigned. Instead, the image displays with a default duration (10 seconds) or any previously set duration on the players, regardless of the duration set in the library. This issue requires the image to be removed and re-added to the playlist to display with the updated duration.
Steps to Reproduce:
Add an image to the Xibo library and set a custom duration (e.g., one minute)
Assign this image to a playlist on the Layout Editor.
Schedule the Layout
Observe that the image playlist shows for 1 minute on the player.
Later, update the duration of the image in the library (e.g., increase it to two minutes).
Check the player to see if the updated duration is applied.
Observed Behaviour: The updated duration is ignored, and a previously set duration (e.g., 1 minute) is used instead of the new setting (e.g., 2 minutes).
These are the preferences that are set for the user:
An internal dev environment has a layout (ID 2522) showcasing the issue.
The text was updated successfully, but these errors were encountered:
In Xibo CMS version 4.*.*, modifying the duration of an image in the library does not reflect in playlists where the image has already been assigned. Instead, the image displays with a default duration (10 seconds) or any previously set duration on the players, regardless of the duration set in the library. This issue requires the image to be removed and re-added to the playlist to display with the updated duration.
Steps to Reproduce:
Observed Behaviour: The updated duration is ignored, and a previously set duration (e.g., 1 minute) is used instead of the new setting (e.g., 2 minutes).
These are the preferences that are set for the user:
An internal dev environment has a layout (ID 2522) showcasing the issue.
The text was updated successfully, but these errors were encountered: