Encoding with Azure Media Encoder
Updated: August 12, 2014
After your media has been uploaded into Azure Media Services you can encode it into one of Formats Supported by the Media Services Encoder. It is recommended to encode your asset into a set of adaptive MP4 or smooth streaming files. You can then use Dynamic Packaging to stream your media in one of the following formats: HLS, Smooth Streaming, MPEG-DASH, or HDS. For more information, see Delivering Content.
Encoding jobs are created and controlled using a Job. The Job contains metadata about the processing to be performed. Each Job contains one or more Tasks that specify an atomic processing task, its input Assets, output Assets, a media processor and its associated settings. For more information on encoder settings, see Encoder Guides and Encoder Schemas.
An encoding job is usually combined with other processing, for example, packaging, or encrypting the asset or assets generated by the encoder. Tasks within a Job can be chained together, where the output asset of one task is given as the input asset to the next task. In this way one job can contain all of the processing necessary for a media presentation.
|There is currently a limit of 30 tasks per job. If you need to chain more than 30 tasks, create more than one job to contain the tasks.|
For more information see the following topics:
ConceptsAzure Media Services Overview