-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Rendition selection with multi-codec manifest could ignore the preferred codec #6421
Comments
Hi @woshimaliang,
v1.5 adds logic for picking advanced codecs on start. I recommend updating HLS.js to the latest (v1.5.8) and not setting
Level indexes do not map to the order that variants appear in the manifest. When you set the Level index manually or force playback to begin on a specific Level with |
What version of Hls.js are you using?
1.3.5
What browser (including version) are you using?
Version 124.0.6367.119 (Official Build) (arm64)
What OS (including version) are you using?
MacOS 14.4.1 (23E224)
Test stream
No response
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
With a multi-codec manifest, which includes both h.265 and h.264 codec, when we set default start level (-1), everything is fine. Hls is able to pick an appropriate rendition to start with H.265 (when browser supports that).
However if we specify a startLevel other than start level (-1), our engineer found:
Expected behaviour
set a start level != -1 should not change the behavior. When H.265 (for example) is supported and picked, then sort renditions of that codec, instead of all renditions (of all codecs) in that multi-codec manifest. But we might misunderstand how startLevel:-1 works that it could pick H.264 or H.265 depending on bandwidth.
API doc:
What actually happened?
unpredictable, based on bandwidth
Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: