What you would like to accomplish: I would like the Transcoder API to have new job config options that allow it to dynamically determine the elementary stream video dimensions from the input video aspect ratio.
I have videos of various dimensions and frame rates that I want to transcode. I would like to use the same job template for all of these videos. The template includes multiple output variants for an HLS/DASH ABR ladder.
Some of the input videos are in landscape orientation, and some are in portrait. I would like to be able to provide a dimension size value and a dimension sizing behavior option to the Transcoder API. In other words, I want to be able to instruct the Transcoder API to take a provided size value for an elementary stream (e.g., 1080) and then automatically determine EITHER the width OR height depending on the input video's aspect ratio. Below are some examples:
Provided the following elementary stream configurations with these hypothetical options:
sizePixels: 360, sizeBound: 'lower'
sizePixels: 720, sizeBound: 'lower'
sizePixels: 1080, sizeBound: 'lower'
For an input video with dimensions of 1920x1080, I want the elementary streams to have dimensions 640x360, 1280x720, and 1920x1080, respectively.
For an input video with dimensions of 1080x1920, I want the elementary streams to have dimensions 360x640, 720x1280, and 1080x1920, respectively.
For an input video with dimensions of 1080x1080, I want the elementary streams to have dimensions 360x360, 720x720, and 1080x1080, respectively.
For an input video with dimensions of 1200x1400, I want the elementary streams to have dimensions 360x420, 720x840, and 1080x1260, respectively.
If those same elementary stream configs instead had sizeBound: 'upper':
For an input video with dimensions of 1920x1080, I want the elementary streams to have dimensions 360x202, 720x406, and 1080x608, respectively.
For an input video with dimensions of 1080x1920, I want the elementary streams to have dimensions 202x360, 406x720, and 608x1080, respectively.
For an input video with dimensions of 1080x1080, I want the elementary streams to have dimensions 360x360, 720x720, and 1080x1080, respectively.
For an input video with dimensions of 1200x1400, I want the elementary streams to have dimensions 308x360, 618x720, and 926x1080, respectively.
How this might work: Allow users the option to provide sizePixels and sizeBound to CodecSettings instead of widthPixels and heightPixels. This would not break any behavior for existing users, and would allow users to opt-in to this alternative sizing behavior if desired. The exact names of these options can be anything, I just made them up for demonstration.
If applicable, reasons why alternative solutions are not sufficient: Currently, developers need to fuss with finicky tools like ffmpeg in order to first extract the video dimensions and send a customized ad-hoc job config with each job request. While possible, this is an inferior, error-prone workaround. In my case, I am sending the Transcoder API job request from a Cloud Function, so I would first have to download the entire video file from Cloud Storage into the Cloud Function's memory, then inspect it with ffmpeg, before I can request the job. Not ideal.
Description
What you would like to accomplish: I would like the Transcoder API to have new job config options that allow it to dynamically determine the elementary stream video dimensions from the input video aspect ratio.
I have videos of various dimensions and frame rates that I want to transcode. I would like to use the same job template for all of these videos. The template includes multiple output variants for an HLS/DASH ABR ladder.
Some of the input videos are in landscape orientation, and some are in portrait. I would like to be able to provide a dimension size value and a dimension sizing behavior option to the Transcoder API. In other words, I want to be able to instruct the Transcoder API to take a provided size value for an elementary stream (e.g., 1080) and then automatically determine EITHER the width OR height depending on the input video's aspect ratio. Below are some examples:
Provided the following elementary stream configurations with these hypothetical options:
sizePixels: 360, sizeBound: 'lower'sizePixels: 720, sizeBound: 'lower'sizePixels: 1080, sizeBound: 'lower'If those same elementary stream configs instead had
sizeBound: 'upper':How this might work: Allow users the option to provide
sizePixelsandsizeBoundtoCodecSettingsinstead ofwidthPixelsandheightPixels. This would not break any behavior for existing users, and would allow users to opt-in to this alternative sizing behavior if desired. The exact names of these options can be anything, I just made them up for demonstration.If applicable, reasons why alternative solutions are not sufficient: Currently, developers need to fuss with finicky tools like ffmpeg in order to first extract the video dimensions and send a customized ad-hoc job config with each job request. While possible, this is an inferior, error-prone workaround. In my case, I am sending the Transcoder API job request from a Cloud Function, so I would first have to download the entire video file from Cloud Storage into the Cloud Function's memory, then inspect it with ffmpeg, before I can request the job. Not ideal.