Cisco Cisco StadiumVision Mobile Streamer Quick Setup Guide

Use an ad-hoc state to display a moment of exclusivity such as a touchdown,

goal, stoppage in play or a sponsor venue domination.

If you want to display different content using the same template in different zones /

groups, you can save time by copying assigned actions from one zone / group to

another. You can then select different content to display in the template in the

copied zone / group.

It is important that you allow media players to load the runtime and get into a ready

state to receive and process new script actions. Therefore, be sure to define an

empty script state (without any actions or commands) as the first state in all event

scripts, and configure it to run for a duration of at least two minutes (120 seconds)

before changing to a different state.

TIP: The actual duration for the empty state depends on the

number of media players in the system and the amount of time it

takes to stage any content. Manually staging content before you

run a script can help reduce this time.

Do not change an event state more frequently than the following:

SV-4K and DMP-2K media players: 15 seconds minimum

DMP 4310G: 60 seconds minimum

If you are supporting an environment with mixed DMPs that use the same script, it

is important to allow for 60 seconds for an event state change.

Play the event scripts to visually verify each state and ad hoc states within a

venue.

How to Set Up Event Scripts

This section includes the following topics:

206 of 331