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
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.
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
Azure Media services just announced the public preview of its Live streaming service. This tutorial will show you how to set up live streaming with Azure Media Services .NET SDK. You can download full source code in our GitHub. Meanwhile, if you want to skip the coding part, please check out Getting Started with Live Streaming Using the Azure Management Portal. Read more here
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
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.
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)
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
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
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.”
It has been over 8 months since the last Build was held in Seattle. I am preparing my Build presentation and started to realize how much progress our services made. Here is some major new features I want to share with you. As I promised, all code demo are available here for download: http://sdrv.ms/17lzuUL.
Dynamic Packaging with MPEG-DASH live profile streaming support
What is Dynamic packaging?
This is a feature we shipped since Feb this year, which enables you to reuse your encoded video (Mp4 or Smooth streaming) to delivery multiple adaptive streaming formats such as Http-live-streaming or Smooth Streaming, by simply changing the streaming URL. Therefore, you no longer need to go through an intermediate step which packages video asset into various streaming format. And you save costs for storing them – you just need to store the encoded video once. Below it’s a diagram that demonstrates the concepts I described above. And I have a separate blog on dynamic packaging feature.