-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Some resolutions don't appear on dash #3361
Comments
It looks like the problem is that we are choosing to go with your Once we pick a codec and container, we filter out all tracks that have a different codec and container. MediaSource can't do seamless codec-switching or container-switching at the moment. One day it might become part of the standard, in which case this sort of thing will become less of a problem. So this is a bit of an odd situation, anyway. I think we were kind of assuming that manifests would offer the same set of resolutions for each codec, when we made the code. One of the planned parts of our MediaCapabilities API work (#1391) will be a configuration value that will let you manually choose which codec you would prefer the player to use. Once that is added, you could tell the player to prefer For now, I'll mark this as "working as intended". If you think that setting codec preferences wouldn't be a good solution for your asset library, and you also can't fix this on your end, then we could make an enhancement request for this. It's not in the design doc as it stands now, but we might be able to add something like an optional user-provided codec-picking callback to the codec preference algorithm, to let users choose codecs based on miscellaneous criteria. |
Interesting! My options could be as follows:
Is there anything else that could be possible solutions for this? |
If you make more resolutions for your You could also just not list the |
I don't have more Using just In any case, I'll wait for spec to change or an option to prefer |
Alright. I'll close this issue then. Feel free to track issue #1391 for progress on that API. |
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
Tried demo and the nightly demo
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
master
?I tested the nightly, not sure if they're the same tho..,
Are you using the demo app or your own custom app?
Both
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Tried Google Chrome on Windows 10
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?
https://dweb.link/ipfs/QmYWt44ZD6bVhHHo8BtPUBP9yT9cCZYYgnNps3vxouxpWQ?filename=dash.xml
What configuration are you using? What is the output of
player.getConfiguration()
?It's the demo player.
What did you do?
Load the manifest as a Custom URI
What did you expect to happen?
See the resolutions which are > 960p
What actually happened?
I can only see the resolutions up to 960p, not higher this seems to be an edge case scenario for me.
The text was updated successfully, but these errors were encountered: