Cenc are only supported in API level >=21 for Widevine key system ?

[Tao Liu]

Hi

    I found this in chromium source code, so I wan to known if  cenc are  only supported in API level >=21 for Widevine key system?

Thanks, 

Tao, Liu

[David Dorwin]

This comment is referring to the exact string "cenc", which is the EME Initialization Data Type string for CENC 'pssh' boxes. Prior to API level 21, only "video/mp4" could be used to specify this interpretation of the Initialization Data. Also, there is/was no specification of the strings that MediaDrm plugins support, but "video/mp4" seems to be supported by all.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Tao Liu]

I got below info when watching netflix, after call  MediaDrm.getKeyRequest. 

I/WVCdm   (  126): CdmEngine::GenerateKeyRequest

E/WVCdm   (  126): CdmLicense::PrepareKeyRequest: retrieved certificate not of type service, 0

E/WVCdm   (  126): CdmEngine::GenerateKeyRequest: key request generation failed, sts = 3

Any ideas?

[David Dorwin]

It appears license request generation failed because the certificate for encrypting client information was invalid.

Were you actually watching Netflix or attempting to watch a video on Netflix? Were you using the desktop site?

[Tao Liu]

Yes, I want to watch netflix drm video with chromium on Android. But If I use Android user agent, netflix will let me install android app, so I use Linux PC user agent to visit Netflix, and then encounter below problems :

1 content_shell does not support EME, so add EME support 

2 Android "Distinctive Identifier" is ALWAYS_ENABLED, but with Linux PC ua, Netflix require "Distinctive Identifier" to be "not-allowed". Then I hack chromium to bypass.

3 Netflix will set server certificate first, then android widevine failed to  generate key request. And I didn't find widevine server certificate specification.

So,  how to continue my work? 

[David Dorwin]

You could try not setting the PRIVACY_MODE property to bypass some of the certificate logic. However, it it's possible the desktop site makes assumptions about the client implementation and cannot be made to work on Android.