Povratne informacije

Dynamic packaging

  • Članak
  • 2 min. za čitanje

media services logo

Note

Update your Azure Media Services REST API and SDKs to v3 by 29 February 2024. Version 3 of Azure Media Services REST API and client SDKs for .NET and Java offers more capabilities than version 2. We’re retiring version 2 of the Azure Media Services REST API and client SDKs for .NET and Java.

Action Required: To minimize disruption to your workloads, review the migration guide to transition your code from the version 2 API and SDKs to version 3 API and SDK before February 29th, 2024. After February 29th, 2024, Azure Media Services will no longer accept traffic on the version 2 REST API, the ARM account management API version 2015-10-01, or from the version 2 .NET client SDKs. This includes any 3rd party open-source client SDKS that may call the version 2 API. Learn about the latest version, starting with the Media Services v3 Overview.

Microsoft Azure Media Services can be used to deliver many media source file formats, media streaming formats, and content protection formats to a variety of client technologies (for example, iOS, XBOX, Silverlight, Windows 8). These clients understand different protocols, for example iOS requires an HTTP Live Streaming (HLS) V4 format and Silverlight and Xbox require Smooth Streaming. If you have a set of adaptive bitrate (multi-bitrate) MP4 (ISO Base Media 14496-12) files or a set of adaptive bitrate Smooth Streaming files that you want to serve to clients that understand MPEG DASH, HLS or Smooth Streaming, you should take advantage of Media Services dynamic packaging.

With dynamic packaging all, you need is to create an asset that contains a set of adaptive bitrate MP4 files or adaptive bitrate Smooth Streaming files. Then, based on the specified format in the manifest or fragment request, the On-Demand Streaming server will ensure that you receive the stream in the protocol you 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.

The following diagram shows the traditional encoding and static packaging workflow.

Static Encoding

The following diagram shows the dynamic packaging workflow.

Dynamic Encoding

Common scenario

  1. Upload an input file (called a mezzanine file). For example, H.264, MP4, or WMV (for the list of supported formats see Formats Supported by the Media Encoder Standard.
  2. Encode your mezzanine file to H.264 MP4 adaptive bitrate sets.
  3. Publish the asset that contains the adaptive bitrate MP4 set by creating the On-Demand Locator.
  4. Build the streaming URLs to access and stream your content.

Preparing assets for dynamic streaming

To prepare your asset for dynamic streaming, you have the following options:

Audio codecs supported by dynamic packaging

Dynamic Packaging supports MP4 files, which contain audio encoded with AAC (AAC-LC, HE-AAC v1, HE-AAC v2), Dolby Digital Plus(Enhanced AC-3 or E-AC3), Dolby Atmos, or DTS (DTS Express, DTS LBR, DTS HD, DTS HD Lossless). Streaming of Dolby Atmos content is supported for standards like MPEG-DASH protocol with either Common Streaming Format (CSF) or Common Media Application Format (CMAF) fragmented MP4, and via HTTP Live Streaming (HLS) with CMAF.

Note

Dynamic Packaging does not support files that contain Dolby Digital (AC3) audio (it is a legacy codec).