-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot force Chromium Edge to use Widevine with dash.js v3 #3148
Comments
@dsilhavy here you go :) |
Hi @tomraut , As an example: Since the server url for Widevine is not included in the init data it is necessary to set this information when calling the player. For Playready the server url is part of the init data which is why we do not need to hand over server information to the player. dash.js will use the first DRM system for which the requestMediaKeySystemAccess promise is succesfully resolved. This seems to be Playready in this case. In order to change DRM priorities you can use the priority attribute as you did in your example. |
Fair enough, let's keep current behaviour as it is. I'll fix our integration by adding priority attribute. |
Steps to reproduce
Observed behaviour
dash.js logs that it selects PlayReady as key system and won't start playback
There is a workaround for this issue and it is including "priority" attribute to protectionData like this:
Note that with dash.js 2.9.3 same worked without having to include "priority" but apparently some changes made in #2953 broke this. I think this should work also without having to include "priority" in cases where there is only one key system provided in protectionData.
The text was updated successfully, but these errors were encountered: