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
hls.js tries to buffer up to a maximum number of bytes (60 MB by default) rather than to buffer up to a maximum nb of seconds.
this is to mimic the browser behaviour (the buffer eviction algorithm is starting after the browser detects that video buffer size reaches a limit in bytes)
config.maxBufferLength is the minimum guaranteed buffer length that hls.js will try to achieve, even if that value exceeds the amount of bytes 60 MB of memory.
maxMaxBufferLength acts as a capping value, as if bitrate is really low, you could need more than one hour of buffer to fill 60 MB....
=> the max buf length hls.js will try to achieve will always be between [config.maxBufferLength,config,maxMaxBufferLength]
I agree that renaming those variables would help ...
maybe config.maxBufferLengthMin and config.maxBufferLengthMax ...
any suggestion welcomed ...
I don't mean maxBufferLength, but maxMaxBufferLength
The text was updated successfully, but these errors were encountered: