The New Amazon Elastic Transcoder : a new Opportunity to transcode your files.



Available since January 29, 2013, the New Amazon Elastic Transcoder, aims to make it easy for you to transcode video files in a scalable and cost-effective fashion.
For the first release the New Amazon Elastic Transcoder is supporting the MP4 container type, the H.264 video codec,
and the AAC (Advanced Audio Coding) audio codec.
For those who unfamiliar, transcoding is the process of converting a media file (audio or video) from one format, size, or quality to another.
The trend includes no start-up costs: costs are determined by the duration (in minutes) of your transcoded videos. Transcoding of Standard Definition (SD) video (less than 720p) costs $0.015 (one and a half cents) per minute in US East (Northern Virginia). High Definition (HD) video (720p or greater) costs $0.03 (three cents) per minute, also in US East. As part of the AWS Free Usage Tier, the first 20 minutes of SD transcoding or 10 minutes of HD transcoding are provided at no charge.
We also discover that, you can initiate transcoding jobs from the AWS Management Console or through the APIs, arrange to receive notification at various points in the transcoding process.
In regards to Transciding Model, the Amazon Elastic Transcoder takes input from an Amazon S3 bucket, transcodes it, and writes the resulting file to another S3 bucket. You can use the same bucket for input and output, and the buckets can be in any Region. If your transcoding jobs run in a particular Region and retrieve or place content in a different Region, you'll pay the usual AWS data transfer charges.
You will create or reference objects of five distinct types each time you transcode a file. You'll start with one or more Input Files, and create Transcoding Jobs in a Transcoding Pipeline for each file. Each job must reference a particular Transcoding Preset, and will result in the generation of a single Output File.
The Elastic Transcoder accepts Input Files in a wide variety of web, consumer, and professional formats. The Elastic Transcoder generates Output Files.
When you create the Pipeline you'll specify Input and Output Buckets, an IAM role, and four SNS topics. Notifications will be sent when the Elastic Transcoder starts and finishes each Job, and when it needs to tell you that it has detected an error or warning condition.
After you have created a Pipeline, you need to choose a Transcoding Preset  or create a custom one. A Preset tells the Elastic Transcoder what settings to use when processing a particular Input File. Presets are named, and can reference another Preset as a base. You can specify many settings when you create a Preset including the sample rate, bit rate, resolution (output height and width), the number of reference and keyframes, a video bit rate, some thumbnail creation options, and more.
The sequel is to create a Job .Each Job must specify a Pipeline, a Preset, and a pair of S3 keys (file names for Input and Output). The Elastic Transcoder can automatically detect the input frame rate, resolution, interlacing, and container type.
Jobs submitted to a Pipeline will be processed in submission order, but one Pipeline may process several of your Jobs simultaneously if resources are available.
Your application can monitor the status of each Job by subscribing to the SNS topics associated with the Pipeline. It can also use the ListJobsByStatus function to find all of the Jobs with a given status (e.g. "Completed") or the GetJob function to retrieve detailed information about a particular job.
Amazon Elastic Transcoder is available henceforth in the following AWS Regions:
  • US East (Northern Virginia).
  • US West (Oregon)
  • US West (Northern California)
  • Europe (Ireland)
  • Asia Pacific (Japan)
  • Asia Pacific (Singapore
AWS tools and SDKs henceforth include support for the Amazon Elastic Transcoder:
To learn more about Elastic Transcoder Pricing, you can read the Developer Guide .

Popular Posts