Cisco Cisco StadiumVision Mobile Streamer Release Notes
© 2011 Cisco Systems, Inc. All rights reserved.
19 of 26
has not yet run.
•
If conflicting event scripts continue to run, SV Director will wait up to 4 hours before transitioning
the blocked event script to the “Past” state. Similarly, if an event script is continuously staging,
SV Director will wait up to 4 hours to transition it from “Staging” to “Past.” You can change this
estimated duration by setting a value for the script.defaultEstimatedDuration key in the
Dashboard registry. This registry key does not exist in a factory configuration, so you need to
add it to the registry.
the blocked event script to the “Past” state. Similarly, if an event script is continuously staging,
SV Director will wait up to 4 hours to transition it from “Staging” to “Past.” You can change this
estimated duration by setting a value for the script.defaultEstimatedDuration key in the
Dashboard registry. This registry key does not exist in a factory configuration, so you need to
add it to the registry.
•
The endTime for an event script is calculated based on the planned startTime, not the actual
time that the event script started. So if an event script is blocked for 30 minutes and you set an
estimated event script duration of 1 hour, the event script will run only for 30 minutes. The same
behavior applies for event script staging.
time that the event script started. So if an event script is blocked for 30 minutes and you set an
estimated event script duration of 1 hour, the event script will run only for 30 minutes. The same
behavior applies for event script staging.
•
The warning icon of the Active Script which has DMPs in the critical state is not implemented in
Release 2.3.
Release 2.3.
See the Creating and Editing Event Scripts Guide for more information.
Manual Staging of Content Ahead of a Scheduled Event
You can schedule staging of event scripts ahead of time. When you start the event script, a dialog
box displays so you can specify the staging time. For example, if an event script is scheduled at 2:00
PM, you can set the pre-staging time to 120 minutes, and the staging will start at 12:00 PM.
box displays so you can specify the staging time. For example, if an event script is scheduled at 2:00
PM, you can set the pre-staging time to 120 minutes, and the staging will start at 12:00 PM.
It is up to the user to determine how long to allow for staging. The event script will not start until
staging has completed. This means that if you set the pre-staging time to 0 minutes and then start
the event script, staging will begin immediately (this was the behavior in R2.2). The event script will
not start until staging is complete.
staging has completed. This means that if you set the pre-staging time to 0 minutes and then start
the event script, staging will begin immediately (this was the behavior in R2.2). The event script will
not start until staging is complete.
Simplified Event Scripting
The Control Panel Schedule tab was redesigned to provide a more efficient workflow for event
scripting. The new design reduces the number of clicks and the time it takes to create an event
script.
scripting. The new design reduces the number of clicks and the time it takes to create an event
script.
The following enhancements were implemented:
•
The state and action configuration screens were combined into one screen, allowing event
states to be easily copied within a script or across multiple scripts at the same time.
states to be easily copied within a script or across multiple scripts at the same time.
•
Events can be duplicated directly from the Event table.
•
Search capabilities have been improved, allowing you to search on the assigned zone/group,
actions and playlists.
actions and playlists.
•
The Event State Details view provides an at-a-glance view of the zones and groups, assigned
actions, and playlists used by the event script. This enables fast, visual error checking.
actions, and playlists used by the event script. This enables fast, visual error checking.
•
Functionality was added to allow you to easily copy actions assigned to a zone/group and assign
them to other zones/groups within the same event state or different event states within the event
script.
them to other zones/groups within the same event state or different event states within the event
script.
•
A new “Edit Actions” dialog box has been added, allowing you to preview the screen template
and playlist, and also to filter the playlist based on the screen template region.
and playlist, and also to filter the playlist based on the screen template region.
Note: Depending on how the zones and groups are assigned, the Event State Details view may not
provide details for all zones and groups in the venue.
provide details for all zones and groups in the venue.