-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Tizen unable to play clear when configured for DRM due to #2620 workaround #3589
Comments
It'd seems workarounds are not expecting box other then avc1 All video content in mpd is avc3 |
@msavvik, can you send a PR to handle avc3 and its encrypted equivalent? |
Well spotted @msavvik - thanks! |
Will be able to submit PRs once I've cleared it with my organization. In
progress.
czw., 9 wrz 2021 o 17:38 Joey Parrish ***@***.***> napisał(a):
… @msavvik <https://github.com/msavvik>, can you send a PR to handle avc3
and its encrypted equivalent?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3589 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK5K2UK4XRNA5BERKLSBIJDUBDIG7ANCNFSM5CQB6BMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
@msavvik, we closed this issue with a PR from @david-hm-morgan. Please see #3625. But if you want to get permissions from your organization for other contributions in the future, we are always happy to have more people involved. Thanks! |
content_workarounds.js was introduced for Tizen and Xbox platforms. We found that that meant a regression where certain streams were unable to be played. This PR adds ac-3 into the content workarounds in the same was as ec-3 to ensure these streams can be played once more. Issue #3589
content_workarounds.js was introduced for Tizen and Xbox platforms. We found that that meant a regression where certain streams were unable to be played. This PR adds ac-3 into the content workarounds in the same was as ec-3 to ensure these streams can be played once more. Issue #3589
content_workarounds.js was introduced for Tizen and Xbox platforms. We found that that meant a regression where certain streams were unable to be played. This PR adds ac-3 into the content workarounds in the same was as ec-3 to ensure these streams can be played once more. Issue #3589
content_workarounds.js was introduced for Tizen and Xbox platforms. We found that that meant a regression where certain streams were unable to be played. This PR adds ac-3 into the content workarounds in the same was as ec-3 to ensure these streams can be played once more. Issue #3589
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v3.2.0
(v3.0.11 & v3.1.1 also)
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
master
?Yes
Are you using the demo app or your own custom app?
Own custom demo app at https://otvplayer.nagra.com/demo/content/shakaPlayer/issue2620TizenSideEffect/
If custom app, can you reproduce the issue using our demo app?
No because need to customise DRM config
What browser and OS are you using?
Tizen Smart TV
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Tizen 3/5/5.5/6
What are the manifest and license server URIs?
https://otvplayer.nagra.com/demo/content/bbc/bbc_segmented_snaking_subtitle/dash/ondemand/elephants_dream/1/client_manifest-snake.mpd
What configuration are you using? What is the output of
player.getConfiguration()
?Click to expand
What did you do?
Player configured for DRM
Play a clear stream
What did you expect to happen?
Play clear stream without issue.
What actually happened?
3019 error reported
Traced this to d0da2d4
where Tizen and Xbox had special case handling added.
The text was updated successfully, but these errors were encountered: