DEV Community: Bisrategebriel Fisseha

Getting Started with Azure Media Services

Bisrategebriel Fisseha — Mon, 18 Mar 2024 13:47:28 +0000

Setting up Azure Media Services and AMP on your project

Hi folks, in today's blog, we'll go over how to set up media services on the Azure portal. Azure media services power your streaming services, which include content streaming, encoding and transcoding, content protection, and digital rights management (DRM).

Azure Media Services (AMS) is a cloud-based platform offered by Microsoft Azure that allows you to create, manage, and distribute media content at large scale. Its primary goal is to make it easier to create, process, deliver, and monetize a variety of media content, such as video, audio, and streaming services.

Azure Media Services enable you to build media applications using low-latency live streaming, batch encoding, content-protection/DRM, and deliver streaming content to millions of viewers on any device.

To setup Azure Media Services (AMS), there are basically six steps.

1. - Step 1: Create Azure Media Services (AMS)
2. - Step 2: Manage (Upload) Assets
3. - Step 3: Add Job
4. - Step 4: Set/add content protection policy [optional if no DRM]
5. - Step 5: Add streaming locator
6. - Step 6: Use the generated streaming URLs to stream video

Step 1: Create Azure Media Services

This is the first step in creating the necessary resource that is required to setup Azure Media Services (AMS) for our project. It's fine if you have an existing resource group or else go head and create a resource.

Create a Resource Group

After creating a resource group, now is the time to create Azure Media Services. To do that, simply go over the azure portal and search media services on the search bar. And select media services from the results filtered.

Create Azure Media Services Resource

At this stage there is a lot to configure as we have to specify the media service account name, location and storage account to name a few. Below is shown the complete configuration setup.

Specify resource group that you created earlier. [use existing if there is]

Specify media service account name

Choose location

Create new storage account [most of the time it is v2 general purpose]

Create new user assigned managed identity

Now we will click on the 'Review + create' button to create our media service account.

At this point, Azure will validate the required fields, and if we have filled out all of the fields correctly, we will be able to create our media service account instantly.

Upon the successful deployment of our media service account, it is time to move on managing our assets on the media service account.

Click on the 'Go to resource' as shown on the image above and head over to the media service page. As you can see, we don't have any asset to consume or process, thus let's upload the assets we are going to work with.

Step 2: Manage Assets

This step focuses on managing assets by uploading files or using external links in order to prepare the assets (audio, video, etc.). In this tutorial we focus on managing video assets.
To upload assets to our media service account, go to the left side bar and select 'Assets' link.

The Assets Page is empty as it is our first time working with it so, go and click Upload to upload our video.

This stage is pretty straight forward. Select the file you want to upload and then click on 'I agree, upload and close'. It will take some time depending up on how large your file is.

Now our video is uploaded to the blob storage of our media service storage account which we create earlier.

Step 3: Add Job

Welcome to step 3 champ 🏆I guess you are following along, and everything is going well for you. This step is very crucial as it is the main part of configuring the media service processing that includes encoding.

Select the checkbox of the asset you uploaded and click on 'Add Job'.

To clarify things here, there are two key words in this step. Transform and Job. A "Job" refers to a task or process that is performed on media assets using the Azure Media Services platform. These jobs can encompass a variety of tasks such as encoding, transcoding, packaging, encrypting, analyzing, or transforming media files. Whereas "Transform" refers to a set of predefined configurations or presets that define how media content should be processed or transformed. This can include specifications for encoding settings, transcoding formats, bitrate, resolution, audio settings, and more.

Transforms allow users to apply consistent processing settings across multiple media assets, simplifying the workflow and ensuring uniform output quality.

When you create a job in Azure Media Services, you typically associate it with a transform, specifying which transform configuration to apply to the media assets being processed. This allows you to efficiently manage and automate the processing of your media content according to predefined settings.

Create Transform

Specify transform name

Choose transform type

Choose built-in preset name [choose adaptive streaming to get multi bitrate]

Configure Job

Specify output name

Choose asset storage account [ leave it as it is if there is only one storage account ]

Specify job name

Specify job priority [ mostly leave it on 'Normal' but it depends on your processing type ]

Select create

Step 4: Set/add Content Protection Policy

Content Protection Policy is a set of rules and configurations that define how your media content is protected against unauthorized access and piracy. These policies are applied to your media assets to ensure that they are securely delivered to only authorized users or devices.

To setup a content protection policy, click on 'Content key policies' on the left side bar.

Specify content key policy name

Add Digital rights management (DRM)

Add Google Widevine, Apple FairPlay, or Microsoft PlayReady [you can include one or more DRM]

we will use Microsoft PlayReady DRM policy in our case.

Add AES clear key to protect your content with AES-128 encryption [optional configuration]

Setting up the AES clear key encryption is the same approach as setting up DRM.

Specify policy name [ optional ]

Select Yes for use token restriction

Select JWT or SWT for token type

Specify issuer [ eg. myIssuer ]

Specify audience [ eg. myAudience ]

Click Add and finish creating content key policy

Step 5: Add Streaming Locator

Now, it is time to add a streaming locator. A streaming locator is a resource that provides access to streaming endpoints for your media content. It essentially serves as a pointer or URL that clients can use to access the media content securely over the internet.

Go to the uploaded media

Add new streaming locator

Specify name

Choose Streaming policy [ there are different policies ]

Choose Predefined_MultiDrmCencStreaming and MutltiDrmStreaming for encrypted videos

Choose Predefined ClearStreamingOnly and DownloadAndClearStreaming for downloadable unencrypted videos

Choose content key policy

Choose add and finish streaming locator

One thing to notice here is that the default streaming endpoint is inactive by default at the time of creation. So, we need to manually start it to begin streaming. After the endpoint is turned on or started the billing process also starts counting up.

At this stage, processing the media i.e. encoding, encrypting etc. has been completed successfully. What remains would be getting the streaming URLs to stream our video. This would lead us to the last step on setting up Azure Media Services to stream our video.

Step 6: Use the generated streaming URLs to stream video

All is done now! we have our video processed for us to be consumed and streamed. This step guides you to get the streaming URLs of the video asset we have been working with till now. After getting the streaming URL, one can use the URL to stream the video on the Azure Media Player.

Go to the media output file

Click view locator Find the streaming and download URLs [You can also find the streaming URLs on the Playback section]

Copy it to use it on the web page you want your video streamed.

You can play the video on the embedded Azure Media Player inside Azure.

🎉Congrats!! 🎉you have made it to the end but not the very end 😁. On the next blog, I will show you how to add Azure Media Services Video to a Web Page/ Using AMS video on your project.
Stay tuned and let me know what you think down in the comment section!! 😉

References

1. Content Key Policies in Media Services - Azure | Microsoft Learn
2. Transforms and Jobs in Media Services | Microsoft Learn
3. Streaming Policies in Azure Media Services | Microsoft Learn
4. Encoding video and audio with Media Services | Microsoft Learn

Updated Notice: Azure Media Services is being retired on 30 June 2024

HTTP Status Codes 101

Bisrategebriel Fisseha — Sun, 24 Oct 2021 16:25:37 +0000

The Hypertext Transfer Protocol is an application protocol for distributed, collaborative, hypermedia information systems that allows users to exchange data on the World Wide Web. It was developed by Tim Berners-Lee and is now coordinated by the W3C. HTTP, as a request-response protocol, allows users to interact with web resources like HTML files by sending hypertext messages between clients and servers. Then, HTTP clients typically communicate with servers using Transmission Control Protocol (TCP) connections.

HTTP status codes are used on the internet to signify whether a given HTTP request has been successfully completed. When a web page or other resource fails to load properly, the codes assist in determining the source of the problem. The term HTTP status code is actually the common term for the HTTP status line that includes both the HTTP status code and the HTTP reason phrase. HTTP status codes are sometimes called browser error codes or internet error codes.

According to the information message they represent and transmit, these response codes are classified into five categories. Namely,

1.Informational responses (100–199)

2.Successful responses (200–299)

3.Redirection messages (300–399)

4.Client error responses (400–499)

5.Server error responses (500–599)

As for introduction let’s see the most commonly used response codes.

1. Informational Responses(100–199)

Among the HTTP status codes accessible in the field of informational responses. The most common status codes are 100 and 101.

Continue(100)

This interim response indicates that the client should continue the request or ignore it if the request has already been completed.

Switching Protocol(101)

This code is supplied in response to a client upgrade request header and identifies the protocol to which the server is switching.

2. Successful Responses(200–299)

200 is the status code that is being commonly referred to in this category.

OK(200)

This is the ideal status code for a typical, daily, well-working page.

3. Redirection Messages(300–399)

You were redirected to another page. The request was received, but there is some sort of redirection. For example, the page you have been looking for has changed its source and may have been altered, in which case these signals will be examined. The common status codes in this category include 301, 302 and 304.

Moved Permanently(301)

A 301 redirect should be used if one URL has to be permanently redirected to another. In a 301 redirect, visitors and bots that land on that page will be passed to the new URL.

Found(302)

Unlike a 301 response a 302 response code means that the URI of requested resource has been changed temporarily.

Not Modified(304)

This is used for caching purposes. It tells the client that the response has not been modified, so the client can continue to use the same cached version of the response.

4. Client Error Responses

These status codes features an error on the website’s side of the conversation and often appears when a web page could not be reached or doesn’t exist. 400, 401 and 404 are the common one’s in this category.

Bad Request(400)

It appears that the server was unable to understand the request due to improper syntax detected on the client side.

Unauthorized(401)

Semantically this response means “unauthenticated”. That is, the client must authenticate itself to get the requested response.

Not Found(404)

This signifies that the server was unable to locate the file or page that the browser was requesting. 404s do not tell if the missing page or resource is gone forever or just for a short time. By entering a URL that does not exist, you can see what this looks like on your site. It’s like running into a brick wall. As you’ve probably noticed, when your visitors arrive at a page with a 404 error, they’ll either try again (if they’re lucky) or go to another site that provides the information they’re looking for.

5. Server Error Responses(500–599)

The last response category in the HTTP status codes is the server error responses. These response codes indicate a server-side failure. That means, the client made a valid request, but the server failed to complete it. In this class, the most prevalent response codes are 500, 502, and 503.

Internal Server Error(500)

A 500 is a common server error that will prevent visitors from accessing your website. Instead of a problem with missing or unfound pages, this status code indicates a server problem.

Bad Gateway(502)

This error response indicates that the server received an invalid response while acting as a gateway to obtain the response required to handle the request. Simply, it means that the server has received an invalid response from another server.

Service Unavailable(503)

A 503 response, which is a variant of the 500 series, indicates that the server is unavailable due to temporary overload or maintenance. This response code ensures that the search engines know to come back soon because the page or site is only going to be down for a short time.

Last words

Last but not least you can check the status code of any website you are browsing using the network section of the developer’s tool of your browser. And the major importance of HTTP status codes is for Search Engine Optimization (SEO.) It’s worth learning — and committing to memory as they provide direct information on the health of a website and help pinpoint possible problems with the requested content.