Missing video tracks in Edge and Playready #634
Assignees
Labels
component: EME
The issue involves the Encrypted Media Extensions web API
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
type: external
An issue with an external dependency; not our issue; sometimes kept open for tracking
Milestone
Comments
|
There was a bug on Edge that we had a workaround for. This workaround is now causing problems now that the original bug is fixed. However, Edge's fix of the original problem introduces a different problem that we need to workaround. We have filed a bug against Edge for this new case. Basically when we query EME for what the browser supports, Edge doesn't report everything that it supports so we think that some of the tracks are not supported when they in fact are. So we need to update our workaround for this. |
joeyparrish
added
type: bug
|
Marked as "external bug" to reflect that Edge is at fault, but added to the v2.1 milestone for Shaka Player to work around Edge's bug. |
birme
pushed a commit
to Eyevinn/shaka-player
that referenced
this issue
Dec 28, 2016
Edge recently pushed an update which fixed a bug that we were working around. This was that it didn't support multiple MIME types when querying EME. Now it will allow multiples to be passed in. However, Edge's update also introduced a new bug that when getting the configuration from the access object, it doesn't report the correct MIME types. It should include every MIME type that is supported, but it only includes the first one. Closes shaka-project#634 Change-Id: I7156887a112dc844b3cbc9bb2dd9676afee6cf56
Closed
shaka-bot
pushed a commit
that referenced
this issue
Dec 28, 2016
Caused by the fix from issue #634 Change-Id: I5a622af126245ca7849cc3894edb2d465cc21a37
joeyparrish
pushed a commit
that referenced
this issue
Jan 7, 2017
Edge recently pushed an update which fixed a bug that we were working around. This was that it didn't support multiple MIME types when querying EME. Now it will allow multiples to be passed in. However, Edge's update also introduced a new bug that when getting the configuration from the access object, it doesn't report the correct MIME types. It should include every MIME type that is supported, but it only includes the first one. Closes #634 Change-Id: I7156887a112dc844b3cbc9bb2dd9676afee6cf56
joeyparrish
added a commit
that referenced
this issue
Jan 7, 2017
Caused by the fix from issue #634 Change-Id: I5a622af126245ca7849cc3894edb2d465cc21a37
|
The fix for this has just been released in v2.0.3. |
TheModMaker
added
the
component: EME
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Shaka Player are you using?
2.0.2
Yes
master?Yes, I tried at http://nightly.shaka-player-demo.appspot.com/demo/
Are you using the demo app or your own custom app?
Demo app
What did you do?
Try to play video on the demo site in the browser Microsoft Edge on Windows 10.
What content did you load?
If standard demo asset, which one?
Unified Streaming > Tears of Steel (PlayReady)
If custom asset, what manifest and license server URIs?
How did you interact with the content, if at all?
Just started and checked drop down menu on which video tracks are available.
What did you expect to happen?
The non-DRM version of Tears of Steel has five bitrates. I expect the DRM version to also have that.
What actually happened?
Only the two lowest video bitrates are available in Edge. In IE11 all bitrates are available. Tried on Edge version 38.14393.0.0.
The text was updated successfully, but these errors were encountered: