Posts by: mingfeiy

Using a Silverlight player with PlayReady and Token Authentication

Author: Christof Claessens – christoc@microsoft.com

Source code for this post is published at https://github.com/Azure/azure-media-services-samples/tree/master/SilverlightPlayerForAMSPlayReadyTokenAuth.
You could test the token Silverlight Player to playback PlayReady Encrypted Smooth Streaming here: http://sltoken.azurewebsites.net/.

Azure Media Services recently lighted up an exciting feature set related to Content Protection. More specifically, users have now the ability to protect their content with AES encryption or to leverage PlayReady. Both are enabled through a new key/licensing service, part of Azure Media Services.

We’ve written about how this works before and the documentation on MSDN should be pretty solid. What has not been completely clear so far though is the player side of the equation. For PlayReady however, the most convenient way to get started is to leverage Silverlight. The Silverlight Media Framework makes it very easy to get started playing Smooth Streaming protected with PlayReady. Except… in one case, which happens to be the scenario we’d expect most people to find themselves in for real production scenarios. Read More…

How to integrate Azure PlayReady License service with your own encryptor/streaming server

Azure Media Services announced the Public Availability of Azure Media Services Content Protection a month ago, which offers the capability to encrypt your media content with AES or PlayReady content protection. Now, with Media Services, you could ingest, encode, adding content protection and stream your content. However, there are customers who ask me the question, what if I want to just move my License/key delivery server onto Azure Cloud Platform first, and keep my encoding, encryptor and streaming server on premises, could I do it with Azure? The answer is yes, and this blog would walk you through the integration. I will use PlayReady as an example to explain the concept in this blog, however, the same logic applies to AES key server integration as well. Read more here

Dynamic Encryption vs. Static Encryption with Azure Media Services

In Azure Media Services, there are two ways to encrypt your content regardless you are applying common encryption (PlayReady) or envelope encryption (AES) onto your content: dynamic encryption or static encryption. This blog will explain to you the difference and when to use which.

Dynamic Encryption:

This is what we always recommend. Once you encode your file into multi-bitrate Mp4, you could configure the file to be encrypted by defining Content Key, Content Key authorization policy and asset delivery policy. The file is stored in clear in the storage, of course, you could put storage encryption on the container, which is optional. After configuration, our streaming server will apply sample level encryption on your media file on the fly. For example, if you configure AES dynamic encryption for HLS streaming protocol, our streaming server will encrypt your file on the fly with AES envelope encryption and deliver through HLS. Below is a diagram to show you how dynamic encryption works in Azure Media Services: Read more here

Android HLS playback via Azure media services

This blog shows you how to generate Http Live Streaming (HLS) version 3 via Azure Media Services, which is a new feature we recently added, in order to support HLS playback in a wider range of Android devices. According to Google, Android platform supports Http/Https Live streaming playback, with the following restrictions:

  • • MPEG-2 TS media files only
  • • Protocol version 4 (Android 4.4 Kitkat)
  • • Protocol version 3 (Android 4.0 and above)
  • • Protocol version 2 (Android 3.x)
  • • Not supported before Android 3.0

Read more here

Announcing PlayReady as a service and AES dynamic encryption with Azure Media Services

Azure Media Services is getting a big update this week in NABShow 2014. Now you have more options to secure your media delivery – by using AES clear key dynamaic encryption or Microsoft PlayReady content access and protection technology. This feature allows you to serve both encrypted HLS and Smooth Streaming to your client devices.

AES Clear Key Dynamic Encryption Feature explained

Now Azure Media Services allow you to deliver Http-Live-Streaming (HLS) and Smooth Streams encrypted with Advanced Encryption Standard (AES) (using 128-bit encryption keys). Media Services also provides the key delivery service that delivers encryption keys to authorized users. The diagram below demonstrate how this feature works.

AES Clear Key Dynamic Encryption

Read more here

Useful resources for Windows Azure Media Services

This blog provides some information and links to learn Windows Azure Media Services and I hope you found it useful.

If http://portageparkdistrict.org you are new to Windows Azure Media Services, here is how you could get started:

  • • Read the major features and scenarios through Windows Azure website
  • • .NET tutorial for getting started with Media services (link)
  • • Please ask questions on Windows Azure Media Services Forum (link)
  • • Pricing detail for Windows Azure Media Services (link)

Read more here

Using Windows Azure Media Services .NET SDK with key concepts explained

This blog explains the demo of using .NET SDK to complete a typical video-on-demand workflow – upload, encode, package and stream.

1. Create a C# console application through Visual Studio and install Nuget package: windowsazure.mediaservices.

2. I upload a little sample video file for you to use: http://mingfeiy.com/wp-content/uploads/2013/06/azure.wmv. And I put this video file under “C:\tr\“. Therefore, I suggest you create the same folder under your C drive so you don’t need to change input video file path.

3. Here are two config XML you are going to use as video presents: Smooth Streaming Config xml and Http-live-streaming config xml. Similarly, I put them under “C:\ty\”. Certainly, you could get this config from MSDN but since it is a very long string, it is easy to just read from a xml file. Read more here

Announcing Windows Azure Media Services .NET SDK Extensions Version 2.0

I am excited to announce that our Windows Azure Media services Extension SDK version 2.0 just released! If you were using the first version of extension SDK, please pay attention because this version includes a few breaking changes – we had a round of redesign for our existing extension APIs.

What is extension SDK?

This extension SDK is a great initiative by developer Mariano Conveti from our partner Southworks. This SDK extension library contains a set of extension methods and helpers for the Windows Azure Media Services SDK for .NET. You could get the source code from Github repository or install Nuget package to start using it. Read more here

Introducing Extensions for Windows Azure Media Services .NET SDK

I am excited to introduce this great open source project – Extensions for Windows Azure Media Services by Mariano Converti from Southworks. Microsoft has been working with Southworks for many projects and as mentioned by Mariano in his blog, the motivation for this project is that “I wanted to have it <SDK> available in a more consumable and reusable way instead of having to search/copy/paste/tweak the code every time.”

This SDK extension library contains a set of extension methods and helpers for the Windows Azure Media Services SDK for .NET. Here are some major functions such as: Read more here

1 2 3 4 5 6  Scroll to top