W3C home > Mailing lists > Public > public-html-media@w3.org > June 2020

[encrypted-media] Clarify what could cause session.keyStatuses to always be empty (#468)

From: bdr via GitHub <sysbot+gh@w3.org>
Date: Fri, 26 Jun 2020 03:35:19 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-645982835-1593142518-sysbot+gh@w3.org>
XBDRX has just created a new issue for https://github.com/w3c/encrypted-media:

== Clarify what could cause session.keyStatuses to always be empty ==
I'm implementing EME playback on a range of Smart TVs which support the spec "Encrypted Media Extensions W3C Working Draft 31 March 2015". The TVs have native DASH support so I am not using MSE.

I'm using commonly available test streams which I don't believe are using DASH features unsupported by the TVs:


**Not Working**

- Playready MediaKeySystemAccess is supported and media keys are created
- 'encrypted' events are received ok
- the license request appears to be successful
- the license response is sent to keySession.update 
- 'handlekeyStatusesChange' event is received but keyStatuses is *always* empty
- playback doesn't start, no errors are generated and no further video events are received

I've read through https://www.w3.org/TR/2015/WD-encrypted-media-20150331/ several times and it's not clear to me what can cause this to happen or what actions I should take.  Can someone please clarify?

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/468 using your GitHub account
Received on Friday, 26 June 2020 03:35:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 26 June 2020 03:35:22 UTC