Dash.js: [EME] Robustness levels

Created on 18 May 2017  路  5Comments  路  Source: Dash-Industry-Forum/dash.js

This is a change request for adding possibility to set robustness level required by the license server (according to platform and encryption of the content), in order to avoid following warning message on chrome:

It is recommended that a robustness level be specified. Not specifying the robustness level could result in unexpected behavior, potentially including failure to play.

Details for setting robustness level are provided here: https://storage.googleapis.com/wvdocs/Chrome_EME_Changes_and_Best_Practices.pdf

Player should provide a means for setting audio and video robustness levels:

mediaPlayer.setProtectionData({
    "com.widevine.alpha": {
        "serverURL": "<licenser_server_url>",
        "audioRobustness": "<robustness_level_for_audio>",
        "videoRobustness": "<robustness_level_for_video>",
        ...
    }
});
EMDRM Feature Enhancement stale

Most helpful comment

Yes it works, but I think it would more convenient to provide these robustness levels according to the key system, along with all others key system's specific data.

All 5 comments

You can do it right now
var player = dashjs.MediaPlayer().create();
player.getProtectionController().setRobustnessLevel('SW_SECURE_CRYPTO');

it's works for me on Chrome 58 without warning.

Yes it works, but I think it would more convenient to provide these robustness levels according to the key system, along with all others key system's specific data.

@bbert @epiclabsDASH
any thing on how to provide the
audioRobustness: "SW_SECURE_CRYPTO", videoRobustness: "SW_SECURE_DECODE"

from the perspective of the client app which will consume dash.js. I mean what would be the best possible way to provide these robustness levels according to the key system, along with all others key system's specific data.

If i understanding it correctly from what has been mentioned in the thread, it will just give a warning in Chrome version >= 58. So i take it that the options audioRobustness & videoRobustness are not mandatory rather optional. And it is in roadmap to make this a feature.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed because no further activity occurred. If you think this issue is still relevant please reopen it. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings