You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a playlist that contains two codecs - VP9 and x264: https://vz-22d62536-ed8.flufflecdn.net/1ca2960b-77b9-40af-9d34-24178057bbd3/playlist.m3u8
I would like for VP9 to take precedence over x264 when it is supported by the browser. I managed to make it work when selecting the resolution manually by taking the proper level when resolution is selected in the player.
The problem that I'm having is when Auto quality is enabled, the player selects the lower bitrate video (which won't always be x264 in my case). Is there a way to change this behaviour?
Thank you!
What have you tried so far?
No response
The text was updated successfully, but these errors were encountered:
> start candidates with "vp09,mp4a" ignored because min framerate of 30.303 > maximum of 30
There is no option to increase the maximum frame rate limit. It is chosen for greatest compatibility.
robwalch
removed
the
Needs Triage
If there is a suspected stream issue, apply this label to triage if it is something we should fix.
label
Sep 10, 2024
Hmm, that's generated by shaka packager, which maybe recognizes FPS wrongly. Assuming I have fixed the FPS values (so both codecs have 30fps) - how could I proceed?
What do you want to do with Hls.js?
Hello!
I have a playlist that contains two codecs - VP9 and x264:
https://vz-22d62536-ed8.flufflecdn.net/1ca2960b-77b9-40af-9d34-24178057bbd3/playlist.m3u8
I would like for VP9 to take precedence over x264 when it is supported by the browser. I managed to make it work when selecting the resolution manually by taking the proper level when resolution is selected in the player.
The problem that I'm having is when Auto quality is enabled, the player selects the lower bitrate video (which won't always be x264 in my case). Is there a way to change this behaviour?
Thank you!
What have you tried so far?
No response
The text was updated successfully, but these errors were encountered: