MK.IO
understanding
Transforms & Jobs

Transforms & Jobs

Offerings are differentiated based on input type. There are two main input types: Transforms (file-based / VOD processing) and Live Events (live ingest and processing).

Transforms

Transforms are for static (file-based / VOD) content stored in your connected cloud storage (for example, Azure Blob Storage containers or Amazon S3 buckets).

For on-demand content, a Transform acts as a template for the tasks to be performed, and a Job connects a Transform to input content (for example, an Asset or an HTTPS URL) and produces an output Asset.

A Transform is like a recipe. It helps you create the recipe once (Step 1), and submit Jobs using that recipe (Step 2).

You can:

  1. Create a Transform.
  2. Submit Jobs under that Transform.
  3. List Transforms.
  4. Delete a Transform, if you are not planning to use it in the future.

Use Transforms to configure common tasks for processing video or audio files (for example encoding, thumbnail generation, track insertion, asset conversion, or AI processing).

Jobs

A Job is the actual request to apply the Transform to a given input video or audio content. Once the Transform has been created, you can create Jobs in the Video Processing page or using the API.

A Job specifies information such as the location of the input content and the destination for the output. You can specify the input content using HTTPS URLs (including SAS URLs), or existing Assets.