Open Bug 1492377 (cbcs) Opened 6 years ago Updated 2 years ago

[meta] Add cbcs encryption scheme support

Categories

(Core :: Audio/Video: Playback, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: jya, Unassigned)

References

(Depends on 3 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

Need to add cbcs encryption scheme support, now provided by Widevine CDM 10
Rank: 15
Priority: -- → P2
Alias: cbcs
Depends on: 1487416, 1486482
Summary: Add cbcs encryption scheme support → [meta] Add cbcs encryption scheme support
Assignee: nobody → bvandyk
Depends on: 1731727

Any updates on this? CBCS encryption enables playback across a wide range of devices with one type of media segment. For example I just sted this asset on firefox, and can see that clearly CBCS decryption isn't handled:

https://shaka-player-demo.appspot.com/demo/#audiolang=en-US;textlang=en-US;uilang=en-US;asset=https://content.uplynk.com/e5e23a51daca4f679ee29d173aa66ce2.mpd?m4fenctype=cbcs;panel=CUSTOM%20CONTENT;build=uncompiled

License URL is https://content.uplynk.com/wv, but shaka takes care of it, just try playing the above link in Chrome and then in firefox.

Additionally I can play it back in edge on windows, I can also play it back in safari if I create an HLS manifest using the same segments (which I just tested but won't demo for you now).

It plays back on roku and in exoplayer. Basically we are getting really close to being able to just use this one set of segments everywhere, but Firefox appears to be a holdout. You are the only prominent browser not supporting it as of now from what I can tell.

The sa

Thanks for the report. I've spun this off into it's own bug at bug 1759936 to investigate. If you could follow up on that bug with any further info on how long you expect the test asset to be live and how it was created, that'd be useful.

Unassigning bugs assigned to Bryce because he no longer works at Mozilla.

Assignee: brycebugemail → nobody

Firefox(win10) CBCS still not working, CENC works ok. See dashjs tests below.
Chrome(win10, widevine) = cbcs1:9+cbcs0:0+cenc ok
Edge(win10, widevine, playready) = cbcs1:9+cbcs0:0+cenc ok
Chrome(android, widevine) = cbcs1:9+cbcs0:0+cenc ok
Chrome(macOS, widevine) = cbcs1:9+cbcs0:0+cenc ok
Firefox(win10, widevine) = cenc ok
Firefox(macOS, widevine) = cenc ok

CBCS_1:9 pattern (10% encrypt, 90% nocrypt)
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacbcswv
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacbcs

CBCS_0:0 pattern
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacbcs2wv
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacbcs2

CENC normal scheme
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacencwv
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=llamacenc

Severity: normal → S3

Firefox(win10, widevine) started to work once "tenc" encryption box in an init.mp4 segment is using "default_constant_IV, default_constant_IV_size" fields instead of "default_per_sample_IV_size" field.
https://refapp.hbbtv.org/dash/test_dashjs_wv.html?video=springcbcs2wv

You need to log in before you can comment on or make changes to this bug.