-
Notifications
You must be signed in to change notification settings - Fork 795
4K UHD 60p playback issue in Chrome and Firefox #1309
Comments
This is related to https://github.com/videojs/videojs-contrib-hls/issues/1435, closing this in favor of the other issue |
Reopening as it's unrelated to #1435 (segment size isn't what's causing the describing problem per se). @Kjeld your playlist confuses me. You have an In any case, what's happening here is that the initial bandwidth is low enough and the video playlist's If you feed in a pre-programmed videojs('videojs-contrib-hls-player', {html5: {hls: {bandwidth: 30000000}}}) it will select the audio+video playlist and everything will work out. Perhaps we should add something to the initial playlist selection that disregards any audio-only variants if there are any audio+video variants. That being said, unless you need it, you should consider dropping the only audio-only variant playlist. Note that Apple no longer recommends using an audio-only playlist in its HLS authoring guidelines; it now recommends a playlist with low-bitrate audio and video. Alternatively, simply encode more variants that have lower-bandwidth streams. |
Moving this to VHS and we can fix this initial playlist selection logic there /move to http-streaming |
This issue was moved by forbesjo to videojs/http-streaming#175. |
Description
The issue is that our 4K UHD stream doesn't play video. It only reads (and plays back) the audio .ts chucks. We think it is related to a undefined width and height issue.
Sources
https://content.streamone.io/embed/item=TpZBf-QKi4e2/bbbuhd60p.html
https://media.streamone.io/hls/account=MpBJPKUJ4Y6i/item=TpZBf-QKi4e2/TpZBf-QKi4e2.m3u8
Steps to reproduce
Results
Expected
Playback of 60fps UHD video.
videojs-contrib-hls version
It can be reproduced on you latest release
https://videojs.github.io/videojs-contrib-hls/
Browsers
Chrome
Firefox
Platforms
High Sierra
Debian 8
PS: The item is currently transcoding on a test account for you to publicly access, it will be there in 60 minutes from now. 12:23 UTC+1 == NOW()
The text was updated successfully, but these errors were encountered: