Steps to reproduce
If you try to play audio content that has been encrypted but doesn’t have any
pssh boxes in the content, the audio usually hangs. The audio is encrypted normally, contains a
tenc box to get the key-id, and has applicable
senc boxes. The audio is added to the
<video> element using MSE. Using EME, the
pssh box is passed to
generateRequest and the session is created successfully. When the
video.play() is called, the video hangs, despite the keys being available.
The test below creates a
<video> element and loads up encrypted audio data. It initializes EME using app-provided init data. There are two init segments used in this test. The original contains a
pssh box in the media segments, the other is exactly the same except that the
pssh boxes are replaced with
Running the test with the original init segment plays fine. Running the test with the altered init segment usually fails to play. This problem is sometimes intermittent. Make sure to use http when accessing this test.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Steven K.”
Changed Assigned To to “Venkat K.”
Changed Assigned To from “Venkat K.” to “Nishant N.”
Changed Assigned To to “Ramy W.”
Changed Status to “Confirmed”
Changed Status from “Confirmed” to “Fixed”
Thank you for providing this information about the issue. We have confirmed the problem, and we are working on a solution for a future build of Edge. We are presently tracking this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.
The MS Edge Team
Can anyone from Microsoft provide an update on this? The last update said “working on a solution for a future build of Edge” and "duplicate of an existing internal bug report".
Has the bug been fixed? In what version of Edge will we see the fix? Thanks!
Can you please provide an update on this issue.
As this is blocking us to enable Key Rotation with MS Playready Encryption Scheme for LIVE.
Thanks and Regards,
I just confirmed that this is fixed in Edge/16.16299.