TODO: Fetch high resolution protected content.
requestMediaKeySystemAccess ( 'org.w3.clearkey', [ )Ĭonsole. In that case, Chrome will discard any capabilities object it cannot support, so the accumulated configuration may contain one encryption scheme or both. In the example below, only one configuration with two different encryption schemes is queried. Label : 'configuration using the "cbcs" encryption scheme' , Label : 'configuration using the "cenc" encryption scheme' ,ĬontentType : 'video/mp4 codecs="avc1.640028"' ,ĬontentType : 'audio/mp4 codecs="mp4a.40.2"' , requestMediaKeySystemAccess ( 'org.w3.clearkey', [
GOOGLE CHROME UPDATE 2018 DOWNLOAD HOW TO
The example below shows how to query two configurations with different encryption schemes. Note that Clear Key always supports the 'cenc' scheme. If not specified, it indicates that any encryption scheme is acceptable. 'cbcs' AES-CBC mode partial video NAL pattern encryption.'cenc' AES-CTR mode full sample and video NAL subsample encryption.The new encryptionScheme key can be one of two values: To avoid having to determine which platform they're on to check for "known" encryption scheme support, a new encryptionScheme key is added in MediaKeySystemMediaCapability dictionary to allow websites to specify which encryption scheme could be used in Encrypted Media Extensions (EME). These two encryption schemes are incompatible, so web developers must be able to make intelligent choices about what content to serve. Some platforms or key systems only support CENC mode, while others only support CBCS mode. AV1 video decoder support had to be pushed back to Chrome 70 because of changes to the MP4 binding.Ĭhromestatus Tracker | Chromium Bug # EME: Querying encryption scheme support