Roku Developer Program

Developers and content creators—a complete solution for growing an audience directly.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
stefanb
Level 7

Streaming Player does not send Request to DRM Server

Hello,

we are currently testing our PlayReady DRM server with roku box .
We experience a strange behaviour: while all relevant links from offical Microsoft Testpage work fine, our own Server (which works fine everywhere else) does not receive a request from the Player:

Excerpt from protection header (Base64 encoded):

[1][1]<WRMHEADER xmlns="http://schemas.microsoft.com/DRM/2007/03/PlayReadyHeader" version="4.0.0.0"><DATA><PROTECTINFO><KEYLEN>16</KEYLEN><ALGID>AESCTR</ALGID></PROTECTINFO>
<KID>[...]</KID>
<LA_URL>SERVER_URL/CSM/RightsManager</LA_URL>
<LUI_URL>http://SERVER_URL/CSM/RightsManager</LUI_URL>
<CHECKSUM>[...]</CHECKSUM></DATA></WRMHEADER>

But no call is made...

As I said, with official MS links it works fine. We traced, and we see, that no call to the license Server is made
0 Kudos
4 REPLIES 4\
stefanb
Level 7

Re: Streaming Player does not send Request to DRM Server

The message we get: 11, 0: Unkown or unsupported sample encryption.
0 Kudos
stefanb
Level 7

Re: Streaming Player does not send Request to DRM Server

According to tests with the Servers developers, ROKU Box can't handle the { } around the systemID in the protection header, although this is officially documented standard. Is this correct?
0 Kudos
steve_1ms
Level 7

Re: Streaming Player does not send Request to DRM Server

We are also trying to get PlayReady working on ROKU and get the exact same error. Were you able to confirm that the { } around the systemID in the manifest is the cause of the the playback error?
0 Kudos
cdkelly
Level 8

Re: Streaming Player does not send Request to DRM Server

Any resolution to this issue? We are also seeing playback issues with manifests that have { } around the systemID.
0 Kudos