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 am able to reproduce. What I am seeing is that level 0 was already loaded, so the player successfully switches to level 0, as level 1 fails. Why fragment loading does not resume is the issue.
v1.3.5 jumps straight down to 0 without fragment requests being interrupted, so it avoids this case which is probably still there, but less likely to occur. Let me know if a v1.4.5 patch would help as v1.5.0 won't land until later this summer.
Yes, a v1.4.5 patch would be a great help, as I was seeing this bug happens more than often.
I have tried your changes with #5537 and it has thrown a fatal: true fragLoadError for video and fatal: true levelLoadError for live successfully.
What version of Hls.js are you using?
1.4.4
What browser (including version) are you using?
Chrome 114.0.5735.90
What OS (including version) are you using?
Windows 10
Test stream
https://vod-zlr2.tv360.vn/video1/2022/11/10/09/7062f3b1/7062f3b1-832c-4b04-b3d3-e5b8ef1ffb3a_m.m3u8?timestamp=1686284460&token=b1f4c65bfcbeadc4d0e441fe000a08f0
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
https://hlsjs.video-dev.org/demo/?src=https%3A%2F%2Fvod-zlr2.tv360.vn%2Fvideo1%2F2022%2F11%2F10%2F09%2F7062f3b1%2F7062f3b1-832c-4b04-b3d3-e5b8ef1ffb3a_m.m3u8%3Ftimestamp%3D1686284460%26token%3Db1f4c65bfcbeadc4d0e441fe000a08f0&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOnRydWUsInN0b3BPblN0YWxsIjpmYWxzZSwiZHVtcGZNUDQiOmZhbHNlLCJsZXZlbENhcHBpbmciOi0xLCJsaW1pdE1ldHJpY3MiOi0xfQ==
(Please info if the test link is expired, we will provide a new one)
Expected behaviour
After number of level loader retries, should ended with fatal error.
hlsjs.video-dev.org-1685673654745.log
What actually happened?
End with no fatal error.
Console output
Chrome media internals output
No response
The text was updated successfully, but these errors were encountered: