CBCS content does not work on WebOS6 since commit ec29f82592fdec9e189fc87a25704fabffb7d404 #7477
Labels
component: EME
The issue involves the Encrypted Media Extensions web API
platform: WebOS
Issues affecting WebOS
priority: P2
Smaller impact or easy workaround
type: bug
Something isn't working correctly
Milestone
Have you read the FAQ and checked for duplicate open issues?
yes
If the problem is related to FairPlay, have you read the tutorial?
unrelated
What version of Shaka Player are you using?
latest
Can you reproduce the issue with our latest release version?
yes
Can you reproduce the issue with the latest code from
main
?yes
Are you using the demo app or your own custom app?
own app
If custom app, can you reproduce the issue using our demo app?
its a smarttv, cannot use demo app there
What browser and OS are you using?
unrelated
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
WebOS6 which uses chrome 79
What are the manifest and license server URIs?
Manifest: https://edge1.motv.eu/s1/vods/30/neni-houba-jako-houba-3852/66c72001de232-2635-mp4-cbcs.mpd
License server: https://mw.motv.eu/widevine_proxy
What configuration are you using? What is the output of
player.getNonDefaultConfiguration()
?What did you do?
I attempted to play Widevine-CBCS encrypted content on webos
What did you expect to happen?
For the playback to work
What actually happened?
It didn't work, on some versions it fails with 4032 and later on with 6001 shaka player error code
I was able to find the commit that broke the playback by testing and compiling shaka player commit by commit - it was ec29f82
If I understand what the commit does, it is trying to detect cbcs encryption support and if not supported, it will remove the tracks. But webos6 does support CBCS and therefore it should play normally. Is there something we can change, configuration-wise in the player to make this work? Or is it an issue with webos and its declaration of supported drms? I tried setting up audioRobustness as well but that didn't help
Are you planning send a PR to fix it?
I tried to study the commit in question but I am not sure I fully understand it
The text was updated successfully, but these errors were encountered: