Cisco Cisco StadiumVision Mobile Streamer Maintenance Manual
Guidelines for Event States and Event Scripts
Consider the following guidelines when creating event states and event scripts:
l
Cisco StadiumVision Director displays the default video channel / non-event state
on the media players when an event script is not running on it.
l
When you use Proof of Play content in your playlist, and especially when your
PoP content is included near or up to the end of the playlist, you should define a
final script state (without any PoP content) that runs for at least 60 seconds so that
all PoP data has time to be captured by Cisco StadiumVision Director. This last
event state is commonly set up to turn off the displays in the venue.
l
When you configure a script action for a zone, then by default all groups within
that zone inherit the defined action. You can override this inheritance by
configuring a script action for a particular group within that zone.
l
When a zone contains multiple groups, and if you configure script actions for a
particular group, those actions will apply only to that group.
l
Cisco StadiumVision Director supports only one RS-232 command per event
state.
l
Maximum number of simultaneous scripts (when per-script multicast is in use) is
20.
Prerequisites for Event Script Creation
Before you create event scripts, be sure that the following conditions are met:
l
DMPs have been successfully added to the SV Director database and are in
'production' state.
o
DMPs and IP phones are defined and added for Local Control Areas.
o
If used, third party touch panels are defined and associated for local TV control
(DMP 4310G only).
l
DMPs are linked to locations.
l
Zones and groups have been created.
l
Content has been added and playlists created.
l
Channels have been assigned.
© Cisco Systems, Inc. All rights reserved.
181 of 285