Cisco Cisco StadiumVision Mobile Streamer
© 2010-2011 Cisco Systems, Inc. All rights reserved.
Page 26 of 47
•
Do not put important content, such as sponsored ads, into the first state or the
first few seconds of an event script. It takes several seconds for the event script
to appear while the DMP is initializing. Content may not appear on the display
during that initial starting time. Also, this content may or may not appear in proof
of play records.
to appear while the DMP is initializing. Content may not appear on the display
during that initial starting time. Also, this content may or may not appear in proof
of play records.
•
Do not use zero-duration items in a playlist with other items. Instead assign a
very long duration time to the item. (Note that this will prevent proof of play from
working for that item.)
working for that item.)
•
Changing the event script after it has started running can often cause the script
to become unstoppable via the Control Panel. Therefore, the StadiumVision
Director UI now prevents you from modifying an active script. If you need to
make changes to a script, you must first stop the script. To stop the event script
from the Control Panel, go to the Control tab, select the running event script, and
click Stop Script. To stop the event script from the Management Dashboard, go
to Tools > Advanced and select Reset Active Scripts.
Director UI now prevents you from modifying an active script. If you need to
make changes to a script, you must first stop the script. To stop the event script
from the Control Panel, go to the Control tab, select the running event script, and
click Stop Script. To stop the event script from the Management Dashboard, go
to Tools > Advanced and select Reset Active Scripts.
•
If you initiate an emergency state while in an ad hoc state, upon return from the
emergency state you are return to the previous sequential state, not to the ad
hoc state.
hoc state.
•
To protect against overflows in RSS feeds, Cisco StadiumVision Director trims
the number of RSS feed entries to a maximum message size of 15822 bytes.
Each RSS ticker text consumes the following number of bytes against this
maximum:
Each RSS ticker text consumes the following number of bytes against this
maximum:
-
32 bytes of message traffic overhead per ticker text
-
The size of the ticker text, after percent encoding (also known as URL
encoding). See this
that the particular details of the specific characters which are and are not
percent-encoded are those enforced by the java urlencode function. See
percent-encoded are those enforced by the java urlencode function. See
-
If more RSS data exists than can fit into the 15822 bytes, the data is
truncated. Extra entries will not be sent to the DMPs.
•
Content file names should not contain spaces. Certain browsers will not
recognize filenames with a space when uploading content. More importantly,
proof of play does not recognize files that contain spaces. Content files with
spaces in the name will not be accounted for in the proof of play data.
proof of play does not recognize files that contain spaces. Content files with
spaces in the name will not be accounted for in the proof of play data.
•
Including video in the first state may cause unexpected results. It is
recommended that you create a first state that only turns on the TVs. Then
create a second state in which video and other content are included.
create a second state in which video and other content are included.
•
The height of the ticker region in the single-height L-wrapper template is
incorrect. It is 1920x165 and should be 1920x166. This will be corrected in a
future release. As a workaround, you can create a custom template with the
correct size ticker.
future release. As a workaround, you can create a custom template with the
correct size ticker.