Cisco Cisco StadiumVision Director
© 2010-2011 Cisco Systems, Inc. All rights reserved.
Page 27 of 47
•
With long-lived (multi-day) events, where the start times are more than 26 hours
in the past, the content will be removed by the rsync task and TVs may go black
depending on the configured content.
depending on the configured content.
This is because event scripts were originally designed to be short-lived (running
only for a few hours). The active repository is not a long- lived area. Instead, its
contents are generated “from scratch” based on the pending and current event
scripts. And only the event script start time is accounted for, not the event's
duration. The current algorithm synchronizes content for events which will start
or have started in the next / previous 26 hours (24 hours + a 2 hour window).
Any scripts that do not fall within this window are excluded from the active area
(and thus their contents are removed from the DMPs when the content is
staged).
only for a few hours). The active repository is not a long- lived area. Instead, its
contents are generated “from scratch” based on the pending and current event
scripts. And only the event script start time is accounted for, not the event's
duration. The current algorithm synchronizes content for events which will start
or have started in the next / previous 26 hours (24 hours + a 2 hour window).
Any scripts that do not fall within this window are excluded from the active area
(and thus their contents are removed from the DMPs when the content is
staged).
This behavior will change in upcoming releases. To address this issue in the
existing release, you can remove the rsync task from the ScheduledTask list (as
long as you are not depending on the scheduled event script starting) and
instead use the Dashboard to immediately synchronize content and start the
event scripts.
existing release, you can remove the rsync task from the ScheduledTask list (as
long as you are not depending on the scheduled event script starting) and
instead use the Dashboard to immediately synchronize content and start the
event scripts.
Video Playlists
•
There is a 2GB limitation on the size of local files on the DMP. Therefore,
prepositioned videos cannot be more than 2GB.
•
When using video playlists, you must specify the entire URL/path of the file that
has been prepositioned on the DMP. No content validation is done, however, so
be careful not to point to a file that corrupts the DMP.
be careful not to point to a file that corrupts the DMP.
•
The use of video content and video playlists in an ad-hoc state is not supported.
•
Do not include spaces in the names of groups that you plan to use with the
Video Distribution Manager.
Local Control Areas
•
The default setting for the tvguide.autolaunch is incorrectly set to 1. Prior to
version 2.2.1, the default was set to 0. Therefore, when you upgrade to 2.2.1,
you must change the setting in the registry.
you must change the setting in the registry.
•
It is recommended that you avoid assigning a DMP to multiple Luxury Suites. If
a DMP is assigned to more than one Luxury Suite, it will use the Per-Area
Channel Guide associated with the last Luxury Suite to which it was assigned.
For example if a DMP is added to Suite 1 and then added to Suite 2, it will use
the Channel Guide defined for Suite 2.
Channel Guide associated with the last Luxury Suite to which it was assigned.
For example if a DMP is added to Suite 1 and then added to Suite 2, it will use
the Channel Guide defined for Suite 2.
•
If the user changes the channel via an IP phone, IR remote, or 3rd-Party
remote, the channel chosen by the user will override the currently playing video
playlist with the selected video.
playlist with the selected video.