Skip to content
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

PS5 limitation causing playable variants to be dropped #4782

Closed
littlespex opened this issue Dec 2, 2022 · 3 comments
Closed

PS5 limitation causing playable variants to be dropped #4782

littlespex opened this issue Dec 2, 2022 · 3 comments
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Milestone

Comments

@littlespex
Copy link
Contributor

littlespex commented Dec 2, 2022

Have you read the FAQ and checked for duplicate open issues?
Yes

What version of Shaka Player are you using?
4.2.x

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?
Custom app

If custom app, can you reproduce the issue using our demo app?
No, the issue is device specific

What browser and OS are you using?

  • Device: PS5
  • OS: Prospero
  • UA: Mozilla/5.0 (PlayStation; PlayStation 5/4.00) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Safari/605.1.15

What are the manifest and license server URIs?

Available upon request

What configuration are you using? What is the output of player.getConfiguration()?

Default

What did you do?

Load a DRM protected stream that produces 20+ variants in the period flattening process.

What did you expect to happen?
All playable variants are available via player.getVariantTracks().

What actually happened?

Playable variants are dropped.

@littlespex littlespex added the type: bug Something isn't working correctly label Dec 2, 2022
@github-actions github-actions bot added this to the v4.4 milestone Dec 2, 2022
@littlespex
Copy link
Contributor Author

littlespex commented Dec 2, 2022

One potential fix that we have tried is to cache the results of requestMediaKeySystemAccess in the decodingInfo polyfill because there are many codec/drm combinations that repeat.

Can anyone think of any potential drawbacks to this approach?

@joeyparrish
Copy link
Member

😭

@littlespex
Copy link
Contributor Author

This issue is addressed by a previous fix: #4708

@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jan 31, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 31, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated type: bug Something isn't working correctly
Projects
None yet
Development

No branches or pull requests

2 participants