Skip to content

Transcode Requests

There are currently three types of transcode request, mezzanine & proxy, wav or pluto passthrough. Regardless of the type being requested, creating the request is basically the same.

The key points of a transcode request are:

  • Asset ID - the asset that needs transcoding. This information can be found in the pending_transcode view
  • GCD MOS - if a file is using the pluto_tv profile, or creating mezz & proxy for sub conform, then the Foo ID for the media order is required. This information can be found in the gcd_mos tab and using the adhoc view to filter accordingly
  • Required Language - the language required for the transcode
  • Profile & Proxy - this will be one of mezzanine, wav or pluto_tv. If mezzanine is selected, proxy_required will need to be ticked
  • Status - all requests must have pending status set
  • Release After Date - once all other fields are complete, a release date must be set. For example, if 26-Sept is set as the date, the files will not be sent to Hybrik until 27-Sept

Here is a table showing the individual requirements of each type of request:

Transcode Type Profile Proxy? GCD MOS ID?
Straight to order Pluto TV NO YES
Mezzanine and Proxy (for audio conform) Mezzanine YES NO
Mezzanine and Proxy (for sub conform) Mezzanine YES YES
Conformed audio and mezzanine transcode (straight to order) Pluto TV NO YES

Creating a Transcode request

For transcode requests, these will be created once an asset has been synced back from logging. Once synced back, assets can be found in pending_transcode view.

To setup a new transcode request, the source assets need to be connected by copying and pasting the Asset ID into a new request.

If the assets are using the pluto_tv profile or need to go through sub conform, it is important to provide the Foo ID for the media order. This means that once the request is complete, the transcoded file or mezzanine will download/copy directly to the order rather than into a s3 bucket where it will wait to get manually trafficked across to GCP.

The loom below shows the transcode request process for audio transcode requests with trim. This is using source audio files that already match to the OV and need 1 second removed top/tail:

Loom recording

The loom below shows the transcode request process for mezzanine & proxy transcode requests for sub conform:

Loom recording