Skip to content

Latest commit

 

History

History
110 lines (70 loc) · 5.89 KB

README.md

File metadata and controls

110 lines (70 loc) · 5.89 KB
Raw

PlayReady sample

Shows several common scenarios to playback protected content with PlayReady.

Note: This sample is part of a large collection of UWP feature samples. If you are unfamiliar with Git and GitHub, you can download the entire collection as a ZIP file, but be sure to unzip everything to access shared dependencies. For more info on working with the ZIP file, the samples collection, and GitHub, see Get the UWP samples from GitHub. For more samples, see the Samples portal on the Windows Dev Center.

C# Scenarios

Scenario 1: Reactive License Request(C#):
This example shows the basics of configuring the MediaElement's MediaProtectionManager property to support PlayReady and reactively handle license service requests. In this configuration license service requests are triggered automatically by PlayReady when the DRM does not have a media license available.

Scenario 2: Proactive License Request(C#):
This example shows how an application can actively manage DRM license requests and the individualization process. Individualization is a onetime configuration process that enables an application to able to make license requests for protected playback.

Scenario 3: Hardware DRM(C#):
This example shows how to configure a device to use either software or hardware DRM. Hardware DRM provides higher security and performance whereas software based DRM provides better compatibility on older devices.

Scenario 4: Secure Stop(C#):
Secure Stop enables a service to better manage concurrent streams for an account. The application can send a secure stop message from PlayReady that notifies a service that playback has stopped and a temporary playback license is no longer available.

JavaScript Scenarios

Scenario 1: Reactive License Request(JS):
This example shows the basics of configuring the MediaElement's MediaProtectionManager property to support PlayReady and reactively handle license service requests. License service requests are triggered automatically by when PlayReady does not have a media license available.

Scenario 2: Reactive License Request(JS):
This example shows how an application can actively manage DRM license requests and the individualization process.

Scenario 3: License Request via EME(JS):
This example uses W3C standards based Encrypted Media Extensions (EME) to enable protected playback. This is useful for Hosted Web Applications where protected playback is configured the same way it would be in the browser.

Scenario 4: Secure Stop EME(JS):
This example uses EME for requesting a license and sending a secure stop message. This sample could also be used to provide secure stop capabilities in a web application in Microsoft Edge.

Note The Windows universal samples require Visual Studio 2017 to build and Windows 10 to execute.

To obtain information about Windows 10 development, go to the Windows Dev Center

To obtain information about Microsoft Visual Studio and the tools for developing Windows apps, go to Visual Studio

Related topics

Samples

AdaptiveStreaming

Reference

Windows.Media.Protection namespace
Windows.Media.Protection.PlayReady namespace
Windows.Media.Streaming.Adaptive namespace

Conceptual

PlayReady DRM
Hardware DRM
Adaptive Streaming with PlayReady

System requirements

Client: Windows 10

Phone: Windows 10

XBox One: In order to use PlayReady DRM within a Universal Application on Xbox One, an additional needs to be added to the app manifest. The capability will need to be added manually to the manifest as a setting is not yet available from within the App Manifest Designer.

To configure:

  • Right-click on the package.appxmanifest from Visual Studio and edit with the XML (text) Editor.
  • Add the following and save:
<Capabilities>
    ...
    <DeviceCapability Name="6a7e5907-885c-4bcb-b40a-073c067bd3d5" />
</Capabilities>

Build the sample

  1. If you download the samples ZIP, be sure to unzip the entire archive, not just the folder with the sample you want to build.
  2. Start Microsoft Visual Studio 2017 and select File > Open > Project/Solution.
  3. Starting in the folder where you unzipped the samples, go to the Samples subfolder, then the subfolder for this specific sample, then the subfolder for your preferred language (C++, C#, or JavaScript). Double-click the Visual Studio Solution (.sln) file.
  4. Press Ctrl+Shift+B, or select Build > Build Solution.

Run the sample

Note Ensure that the CPU is selected that matches the machine running the sample. For example, if its Windows on x64 then x64 needs to be selected. If it does not match than the Protected Media Path will not work and playback will fail.

The next steps depend on whether you just want to deploy the sample or you want to both deploy and run it.

Deploying the sample

  • Select Build > Deploy Solution.

Deploying and running the sample

  • To debug the sample and then run it, press F5 or select Debug > Start Debugging. To run the sample without debugging, press Ctrl+F5 or select Debug > Start Without Debugging.