Cisco Cisco StadiumVision Director
15
Release Notes for Cisco StadiumVision Director Release 3.2
New and Changed Information in Cisco StadiumVision Director Release 3.2
•
•
•
•
•
•
•
API Support
This section summarizes the Application Programming Interfaces (APIs) that are supported in Cisco
StadiumVision Director Release 3.2. Any enhancements in Release 3.2 are identified.
StadiumVision Director Release 3.2. Any enhancements in Release 3.2 are identified.
•
•
•
•
Note
All APIs in Cisco StadiumVision Director are made available by special agreement. Contact your Cisco
Systems representative for more information.
Systems representative for more information.
Event Trigger API
Cisco StadiumVision Director Release 3.2 supports an HTTP-based Representational State Transfer
(REST) API that a software or hardware contact closure source can use to trigger one or more actions
by the Cisco StadiumVision Director software. For more information about support for external input
triggers, see the
(REST) API that a software or hardware contact closure source can use to trigger one or more actions
by the Cisco StadiumVision Director software. For more information about support for external input
triggers, see the
guide.
Note
If you want to control external triggers from a software application, you can contact your Cisco Systems
representative to obtain the Event Trigger API that is made available by special agreement.
“TriggerSVD” is an example of a third-party demo application for the Event Trigger API on iOS
(supporting Apple iTouch, iPhone, and iPad products) and is available as a free download from the
iTunes store.
representative to obtain the Event Trigger API that is made available by special agreement.
“TriggerSVD” is an example of a third-party demo application for the Event Trigger API on iOS
(supporting Apple iTouch, iPhone, and iPad products) and is available as a free download from the
iTunes store.
Media Planner Import API
Cisco StadiumVision Director Release 3.2 supports the Media Planner Import API that is used to import
external, third-party generated playlists. The API can be used to support automatic updates to an already
imported playlist that has been placed in a script, or an external playlist can be manually imported.
external, third-party generated playlists. The API can be used to support automatic updates to an already
imported playlist that has been placed in a script, or an external playlist can be manually imported.
The Media Planner API supports the following features:
Import Playlist Functionality
•
Automatically creates playlist and populates it with existing content.
•
Automatically links missing content to playlist after each missing content item is uploaded.