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:

Cisco StadiumVision Director displays the default video channel / non-event state

on the media players when an event script is not running on it.

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.

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.

When a zone contains multiple groups, and if you configure script actions for a

particular group, those actions will apply only to that group.

Cisco StadiumVision Director supports only one RS-232 command per event

state.

Table 15

describes some guidelines for general script support in Cisco StadiumVision

Director.

NOTE: While these limits have been tested with basic Cisco
StadiumVision Director operation, the combination of maximum
values and complexity of your system and content can potentially
impact the actual limit. Therefore, be sure to test your script
content for expected behavior before using in production.

Table 15. Script Guidelines and Limitations

Script Guideline

Limit

Maximum number of simultaneous scripts (when per-script multicast is in use).

Maximum number of event states per script.

Maximum number of items per event script.

2,200

Groups and Zones

Groups and zones allow you to apply attributes to a number of screens with a single

action. They simplify the control of advertisements in sponsored areas of the stadium,

30 of 48