Introduction

The primary reason for encoding is to ensure universal playback across all devices, players and browsers. For instance, a video uploaded in MP4 format is transcoded to HLS for playback on iOS devices. On the other hand, transcoding also solves bandwidth congestion and video quality issues. If a 720p video is ingested, a transcoder will derive its multiple renditions such as 480p, 360p, and 240p. These renditions will be delivered to the end user as per their local bandwidth allowance overcoming network congestion.


Encoding Providers in VIDIZMO

By default, VIDIZMO offers the following four Encoding Providers. However, organizations can utilize any encoding provider of their choice through some configuration and customization by VIDIZMO Support.


1. VIDIZMO Cloud Encoder:

By default, all media uploaded on VIDIZMO is transcoded using the VIDIZMO Cloud Encoder. The encoder converts media files into multiple formats and renditions for enabling the user to play it on multiple devices/platforms. VIDIZMO Cloud Encoder implements scaling algorithms that automatically scales the necessary resources to process files simultaneously and fast. 


2. Azure Media Services (AMS Standard and Premium): 

Azure Media Services enables SaaS clients to deliver content globally on any virtual device using cloud computing. AMS offers services such as live and on-demand streaming, encoding, transcriptions, audio and video indexing and content protection. AMS transcodes media files in limited formats and renditions. AMS provides storage and transcoding as well as service endpoints.


3. VIDIZMO On Premise Encoder: 

For customers opting to deploy VIDIZMO behind their company's firewall, VIDIZMO offers them on-premise encoding service, allowing all content to be encoded and streamed in a highly secure environment.


4. AWS MediaConvert: 

VIDIZMO customers who are using Amazon S3 storage can configure AWS Elemental MediaConvert for transcoding their media. MediaConvert allows them to easily create video-on-demand (VOD) content for broadcast and multiscreen delivery at scale.


Configuring Encoding Providers in VIDIZMO

In Control Panel > Encoding > Encoding Providers, users can update settings of already-configured Encoding Provider in VIDIZMO.

In order to learn how to configure your Encoding Provider in the process of setting up your account, read more about it here: Understanding Setup Wizard.


VIDIZMO Cloud Encoder

Below are some of the parameters shown in order to re-configure VIDIZMO Cloud Encoder:

  • Encoding Providers: This displays the name of the Encoding Provider that you configured initially through Setup Wizard.
  • API User ID: The ID of the account which has been registered on VIDIZMO Cloud Encoder.
  • API User Key: The Key generated by your account on the Cloud Encoder service.
  • End Point: The URL on your Encoding account that helps act as an API between application and Cloud Encoder.
  • Encoding Web Login: The Email Address of your account on Cloud Encoder.
  • Password: The respective password of your account.





AMS Standard Encoder

Below are some parameters shown in order to re-configure settings of AMS Standard Encoder:

  • Encoding Providers: This displays the name of the Encoding Provider that you configured initially through Setup Wizard.
  • Media Service Name: The name of the media service in your Azure storage against which encoding shall be initiated.
  • Azure AD Tenant Domain: The domain of the dedicated instance for your respective organization's active directory.
  • Azure AD EndPoint: The Azure AD tenant endpoint at which requests can be made for user authentication following which Azure AD issues a token to access resources. 
  • Rest API EndPoint: The URL via which the application makes REST API calls (HTTP requests) to Azure Media Services.
  • Application ID: The respective Application ID of your Account. This can be found in Azure portal. 
  • Client Secret Key: The Client Secret generated against your Client/Application ID in your Azure portal. The client ID and client secret are required to get the access token in this scenario.
  • Resource Group: Enter your resource group name which you have created in your Azure Portal.
  • Media Account: Enter your Media Account.
  • Automatic Processing: If you On your automatic processing then the content will be process automatically into multiple rendition which you set prior. When you keep it off then you have to do it manually in each uploaded content.  



On-Premise Encoder

For an On Premise Encoder, there are no additional configurations allowed, but you may re-configure your provider by exploring other options in the Setup Wizard.

  • Automatic Processing: If you On your automatic processing then the content will be process automatically into multiple rendition which you set prior. When you keep it off then you have to do it manually in each uploaded content.   


Amazon MediaConvert

Following are the editable parameters for AWS Standard Encoder (MediaConvert) that VIDIZMO provides for configurations: To see the step by step process of configuring Amazon MediaConvert click, to see: How to View and Edit Configured AWS Elemental MediaConvert Encoder

  • Media Role ARN: Amazon Resource Names (ARNs) uniquely identify AWS resources. VIDIZMO requires an ARN to specify a resource unambiguously across all of AWS such as MediaConvert and API calls.
  • Media Convert API End Point: To connect VIDIZMO programmatically/API to AWS storage and MediaConvert, you need to enter an endpoint.


Contributions were made by Perwasha Khan & Saim Pasha.