- Newest
- Most votes
- Most comments
hello!
MediaConvert supports clipping by HH:MM:SS:FF timecode on the input file, so that the clip applies to all output types made by the job.
Regarding your second question, yes MediaConvert can inherit many of the output settings from the input settings, such as aspect ratio, frame rate and other parameters. Target video bitrate and CODEC are two values you must specify. However we can automate those selections using Presets and Templates.
MediaConvert supports the use of pre-defined output settings, known as Output Presets. You can define these once, and use them on any or all future jobs you submit, to get consistent output.
Taking that concept one step further, MediaConvert supports Job Templates which can combine a variety of input settings, plus output settings, plus preferences for Job Queue, job priority and other job details into a giant 'preset' which would likely give you the level of automation you are looking for.
Many customers have implemented a 'job template chooser' Lambda function that decides which MediaConvert template to apply to a newly arrived file based on the output of a file analyzer such as mediainfo or ffmpeg; both of which can be run by the Lambda Function to gather information about the newly arrived file. Note, the runtime of a Lambda Fn is capped at 15 minutes; this includes transfer time to read the asset from S3. Larger files requiring longer transfer times can be analyzed the same way using a temporary EC2 instance.
I hope this answers your question. Have a great day!
Edited by: robclem on Nov 24, 2021 3:20 PM
Relevant content
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago