Offerings are differentiated based on input type. There are two main input types, Transforms and Live Events.

Transforms

Transforms are for static content that is uploaded to Azure blob storage. They support re-encoding as well as a file copy into their blob storage.

For on-demand content, a Transform acts as a template for the tasks to be performed, and a Job connects a Transform to content in blob storage to create an 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 encoding or managing video. Each Transform describes a recipe or a workflow of tasks for processing your video or audio files.

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 submit jobs using MK.IO APIs, or any of the published SDKs.

The Job specifies information such as the location of the input video and and the destination for the output. You can specify the the input video location using HTPS URLs, SAS URLs, or existing Assets.