Azure Media Services provides the tools you need to create rich, dynamic client player applications for most platforms including: iOS Devices, Android Devices, Windows, Windows Phone, Xbox, and Set-top boxes. This topic also provides links to SDKs and Player Frameworks that you can use to develop your own client applications that can consume streaming media from Azure Media Services.
When your AMS account is created a default streaming endpoint is added to your account in the Stopped state. To start streaming your content and take advantage of dynamic packaging and dynamic encryption, the streaming endpoint from which you want to stream content has to be in the Running state.
Azure Media Player
Microsoft Azure Media Services allows for content to be served up with DASH, Smooth Streaming, and HLS streaming formats to play back content. Azure Media Player takes into account these various formats and automatically plays the best link based on the platform/browser capabilities. Microsoft Azure Media Services also allows for dynamic encryption of assets with PlayReady encryption or AES-128 bit envelope encryption. Azure Media Player allows for decryption of PlayReady and AES-128 bit encrypted content when appropriately configured.
For more information:
- Azure Media Player
- Azure Media Player Documentation
- Azure Media Player Getting Started Blog
- Sign up to stay up to date with the latest from Azure Media Player
- Add new feature requests, ideas, feedback
Other Tools for Creating Player Applications
You can also use any of the following SDKs:
- Smooth Streaming Client SDK
- Smooth Streaming Windows Store App
- Microsoft Media Platform: Player Framework
- HTML5 Player Framework Documentation
- Microsoft Smooth Streaming Plugin for OSMF
- Licensing Microsoft® Smooth Streaming Client Porting Kit
- XBOX Video Application Development
Azure Media Services provides support for ad insertion through the Windows Media Platform: Player Frameworks. Player frameworks with ad support are available for Windows 8, Silverlight, Windows Phone 8, and iOS devices. Each player framework contains sample code that shows you how to implement a player application. There are three different kinds of ads you can insert into your media:
Linear – full frame ads that pause the main video
Nonlinear – overlay ads that are displayed as the main video is playing, usually a logo or other static image placed within the player
Companion – ads that are displayed outside of the player
Ads can be placed at any point in the main video’s time line. You must tell the player when to play the ad and which ads to play. This is done using a set of standard XML-based files: Video Ad Service Template (VAST), Digital Video Multiple Ad Playlist (VMAP), Media Abstract Sequencing Template (MAST), and Digital Video Player Ad Interface Definition (VPAID). VAST files specify what ads to display. VMAP files specify when to play various ads and contain VAST XML. MAST files are another way to sequence ads which also can contain VAST XML. VPAID files define an interface between the video player and the ad or ad server. For more information, see Inserting Ads.
For information about closed captioning and ads support in Live streaming videos, see Supported Closed Captioning and Ad Insertion Standards.
Media Services learning paths
You can view Azure Media Services learning paths here:
Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. You can also go directly to one of the following categories:
- Azure Media Player
- Client SDK libraries
- Encoding and processing
- Live Streaming
- Media Analytics
- Azure portal
- REST API and platform
- VOD Streaming