Encoding Templates are coming!

News
, ,
1

Bitmovin’s encoding APIs can be configured and customized for any workflow, but we know all of the available options and API calls can be a little bit daunting when you’re just getting started. We’ve taken your feedback and are excited to share a big step toward making it easier to get up and running.

Now available in closed beta, Bitmovin’s Encoding Templates allow you to use a single encoding API endpoint, with all configurations and encoding settings sent in a YAML formatted doc.

Example yaml encoding template:

metadata:
  type: LIVE # can be either `LIVE` or `VOD`
  name: Standard VOD Workflow

inputs:
  https:
    encoding_https_input: # user-defined name to be used for reference within the template
    	# `properties` indicates the request payload of a POST request
      properties: # refers to the `/encoding/inputs/https` endpoint
        host: bitmovin-sample-content.s3.eu-west-1.amazonaws.com
        name: Bitmovin Sample Content

configurations:
	video:
  	h264:
    	encoding_h264:
      	properties:
    			...

encodings:
  my-encoding:
    properties:
      name: Standard VOD Workflow
      cloudRegion: AUTO
      encoderVersion: STABLE

    streams:
      video_h264:
        properties:
          inputStreams:
            - inputId: $/inputs/https/encoding_https_input # reference from line 7
              inputPath: /bbb_sunflower_1080p_60fps_normal.mp4
          codecConfigId: $/configurations/video/h264/encoding_h264
          mode: PER_TITLE_TEMPLATE
          
    ...
    
    start: # exactly one Encoding per template is required
      properties:
        encodingMode: THREE_PASS
        perTitle:
          h264Configuration: {}

Please reach out to our support if you want to become an early adopter and try out this upcoming feature.

1 Like