custom loader aborted continuously #330
Labels
Comments
|
thanks, I found an issue in abr-controller |
mangui
added a commit
that referenced
this issue
Mar 25, 2016
…of emergency switch down on the quality level of last successfully loaded fragment eg: Loaded 1 of [1 ,36],level 0 switching to level 3 Loading 2 of [1 ,36],level 3 ... loading too slow, abort fragment loading and switch to level 0 => switching to level 3 (which is bad ... it should effectively switches to level 0 here) change the logic in get nextAutoLevel() : don't compare this._nextAutoLevel to lastfetchlevel. instead, reset this._nextAutoLevel on FRAG_LOADED related to #330
|
Hi @ilgooz plz recheck against hls.js v0.5.16 and let me know if it is fixed |
|
@mangui 3x of this: here are my logs from chrome: |
|
ok then I guess we can close this one. |
|
alright, you can ping me again after fixes. I'd happily test. |
mangui
referenced
this issue
Mar 25, 2016
in case playback is still stalling although a seek over buffer hole just occured, hls.js will seek to next buffer start + (nb of consecutive stalls * seekHoleNudgeDuration to try to restore playback related to https://github.com/dailymotion/hls.js/issues/319 related to https://github.com/dailymotion/hls.js/issues/330
mangui
added a commit
that referenced
this issue
Mar 25, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hey, this relevant with #319. I'm able to reproduce the same issue but with a custom loader of ours. I see that hls.js continuously calls abort method on Loader and sets level to 0. I'm running on the same env with previous issue.
logs from chrome:
The text was updated successfully, but these errors were encountered: