Exporteren (0) Afdrukken
Alles uitvouwen
EN
Deze inhoud is niet beschikbaar in uw taal, maar wel in het Engels.

Azure Media Services Overview

Updated: June 19, 2014

Microsoft Azure Media Services Azure Media Services allows you to build scalable, cost effective, end-to-end media distribution solutions that can upload, encode, package, and stream media to iOS, Android, Adobe Flash, Windows, and other devices and platforms.

To learn more about Media Services read through this document or skip to the Getting Started with Azure Media Services topic.

Media Services offer the flexibility, scalability and reliability of a cloud platform to handle high quality media experiences for a global audience. Media Services includes cloud-based versions of many existing technologies from the Microsoft Media Platform and our media partners, including uploading, encoding, format conversion, content protection and both on-demand and live streaming capabilities. Whether enhancing existing solutions or creating new workflows, you can easily combine and manage Media Services to create custom workflows that fit every need.

This topic gives an overview of Media Services and also shows the most common workflows.

Overview

Service Level Agreement (SLA)

We guarantee 99.9% availability of REST API transactions for Media Services Encoding. On-Demand Streaming will successfully service requests with a 99.9% availability guarantee for existing media content when at least one On-Demand Streaming Reserved Unit is purchased. Availability is calculated over a monthly billing cycle. For more information, download the SLA document.

Uploading media

In order to encode, manage, and stream your videos, you must first upload your content into Azure Media Services. Media Services uses Azure Storage to store your media for processing and streaming. You can programmatically upload your content using the Media Services REST API or one of the available client SDKs. For more information about the client SDKs, see Developer Tools for Azure Media Services . These API allow for uploading one file at a time or bulk upload operations. Azure Media Services also provides for secure uploading of your content. Storage encryption encrypts your content locally and then uploads it to Azure Storage where it will be stored in an encrypted form. You can also take advantage of third-party fast upload providers like Aspera. For more information about uploading content, see Uploading Media

Encoding media

The following blog explains the difference between encoding and packaging: Encoding versus Packaging.

Encoding is the process of taking a video and compressing it into a format that can be consumed by your customers. Your customers may be using any number of devices to watch your videos: PC's, Mac’s, smart phones, tablets, XBox consoles, set-top boxes, or connected TVs. Each of these devices has features that affect the encoding needed. Smart phones have small screens and little storage, tablets have larger screens but less storage space when compared with PC and so on.If you have not already decided what device or devices you are targeting, see Choosing Your Media Experience. When choosing the encoding for a video, keep in mind all of the devices your customers will use. In some cases you may want to have multiple encodings to enable the best possible experience on a range of devices. For more information on encoding. See Encoding Media with Media Services

Packaging media (static and dynamic)

Once a video has been encoded it can be placed into many different file containers. The process of placing encoded media into a container is called packaging. For example, you can take an MP4 file and convert it into Smooth Streaming or HLS content by using the Azure Media Packager. The packager will place the encoded content into a different file container. For more information, see Encoding versus Packaging.

Media Services supports dynamic and static packaging. When using static packaging you need to create a copy of your content in each format required by your customers. With dynamic packaging all you need is to create an asset that contains a set of multi-bitrate MP4 files. Then, based on the specified format in the manifest or fragment request, the On-Demand Streaming server will ensure that your clients receive the stream in the protocol they have chosen. As a result, you only need to store and pay for the files in single storage format and Media Services service will build and serve the appropriate response based on requests from a client.

It is recommended to use dynamic packaging. However, there are some scenarios that currently require the use of static packaging. For example:

  • Validating existing multi-bitrate (adaptive bitrate) MP4 files.

  • Encrypting your content.

For information on how to use dynamic and static packaging, see Dynamic Packaging and Static Packaging.

Streaming Media

Streaming media is delivered to the client player application in small chunks. When encoding for a streaming format, the encoder breaks up the content into small chunks. The size of the chunks and how they are stored vary by streaming technology. When a client starts playing a video it can download the first chunk and display it quickly. After the player displays a chunk, it requests the next chunk from the server. Media Services supports a number of different streaming technologies:

  • Progressive Download - allows you to start playing media before the entire file has been downloaded

  • MPEG DASH is an international standard adaptive bitrate streaming protocol developed by the Motion Picture Experts Group (MPEG)

  • HTTP Live Streaming or HLS, is an adaptive bitrate streaming technology developed by Apple

  • Smooth Streaming is an adaptive bitrate streaming technology developed by Microsoft

Adaptive bitrate streaming

Adaptive bitrate streaming involves encoding a video into a number of different bitrates. When a player application is playing a video it can determine network bandwidth on the fly and switch to a higher or lower bandwidth chunk as network conditions change. This allows clients to receive the highest quality video when network conditions allow and when network conditions degrade the player can still play the view (although at a lower quality). Azure Media Services support streaming media using HTTP Live Streaming (HLS), MPEG-DASH, and Smooth Streaming.

Securing media

Media Services enables you to protect your media in a number of ways. You can upload your media using Storage Encryption. This protects your content while being uploaded into Media Services as well as when it is at rest in Storage. Media stored in this manner must be unencrypted prior to any processing for example, encoding, packaging, and streaming. At each step in the processing pipeline you have the ability to specify encryption options by passing parameters to the media processor being used (encoder, packager, and encryptor). Media services supports PlayReady DRM and AES 128-bit Envelope Encryption to protect content while streaming. For more information, see Securing Media.

Advertising

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.

Building client applications

AzureMedia services provides the tools you need to create rich, dynamic client player applications for most platorms including: iOS Devices, Android Devices, Windows, Windows Phone, Xbox, and Set-top boxes

For more information see Developing Video Player Applications

Content management

A video Content Management System (CMS) enables you to upload, store, organize, process, and publish media. Content Management Systems in general store files in a database and allow for metadata tagging, searching, and revision tracking.

While Media Services is not a CMS it does enable you to implement a video processing workflow. You can upload and store your content in Azure Storage, encode and package media into a variety of popular formats, and stream your videos online.

Media Services common workflows

This section gives an overview of Media Services common workflows.

Streaming non-encrypted content

  1. Upload a high-quality mezzanine file.

  2. Use the Media Services encoder to encode to H264 Adaptive Bitrate MP4 Set. See the list of all “H264 Adaptive Bitrate MP4 Set” presets in Media Services Encoder System Presets.

    -or-

    Use the Media Services encoder to encode to H264 Smooth Streaming. See the list of all “H264 Smooth Streaming” presets in Media Services Encoder System Presets.

    -or-

    If you want to use a set of adaptive bitrate (multi-bitrate) MP4 files that were not encoded with the Media Services encoder, you should validate your files before further processing. For more information, see Validating Multi-bitrate MP4s Encoded with External Encoders topic.

  3. Use Dynamic Packaging to deliver your content in any of the following formats: DASH/CSF, Smooth Streaming, HLS v3 or v4, HDS (available for Adobe PrimeTime/Access licensees only).

    You can optionally use Static Packaging to do format conversation, but it is recommended to use dynamic packaging.

See examples written in .NET and REST under the Creating Encoding Jobs topic.

Streaming PlayReady encrypted Smooth Streaming, DASH, or HLS (v3 and v4)

  1. Upload a high-quality mezzanine file.

  2. Use the Media Services encoder to encode to H264 Smooth Streaming. See the list of all “H264 Smooth Streaming” presets in Media Services Encoder System Presets.

  3. Use the Media Services encryptor to encrypt Smooth Streaming to PlayReady Smooth Streaming.

  4. Use Dynamic Packaging to deliver your content encrypted with PlayReady in any of the following formats: DASH/CSF + CENC, Smooth Streaming + PlayReady, HLS v3 or v4 + PlayReady.

    You have an option of using static packaging to encrypt HLS v3 with PlayReady. For more information, see Producing HLSv3 Encrypted with PlayReady.

See the following example: Protecting Smooth Streaming and MPEG DASH with PlayReady.

Streaming HLS v3 encrypted with Advanced Encryption Standard (AES)

  1. Upload a high-quality mezzanine file.

  2. Use the Media Services encoder to encode to H264 Adaptive Bitrate MP4 Set. See the list of all “H264 Adaptive Bitrate MP4 Set” presets in Media Services Encoder System Presets.

  3. Use the Media Services packager to convert your adaptive MP4s to Smooth Streaming.

  4. Use the Media Services packager to convert your Smooth Streaming into HTTP Live Streaming (HLS) encrypted with Advanced Encryption Standard (AES).

See the following example: Producing HLSv3 Encrypted with AES-128.

See Also


Build Date:

2014-07-18

Community-inhoud

Toevoegen
Weergeven:
© 2014 Microsoft