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
Browser: Chrome 64.0.3282.167 OS: Windows 10 x64 Clappr Version: 0.2.86
Steps to reproduce:
Use a LIVE playlist
set liveSyncDuration and liveMaxLatencyDuration values
Example:
hlsjsConfig: {
liveSyncDuration: 8,
liveMaxLatencyDuration: 18
},
Play the stream (it works fine and as expected with above values)
Stop the stream with UI button (at any point)
Play the stream again (with UI button)
Player breaks with error in console
This issue also happens with the player at http://cdn.clappr.io/ if the above criteria is met.
console error is:
hls.js:15328 Uncaught Error: Illegal hls.js config: don't mix up liveSyncDurationCount/liveMaxLatencyDurationCount and liveSyncDuration/liveMaxLatencyDuration
at new t (hls.js:15328)
at e._setup (hls.js:152)
at e.play (hls.js:354)
at e.play (container.js:301)
at e.clicked (poster.js:84)
at HTMLDivElement.r.proxy (zepto.js:1616)
I'm assuming Clappr is resetting values for liveSyncDurationCount+liveMaxLatencyDurationCount (notice the COUNT) upon attempting to restart stream, even though they should not be provided when using the NON-count values.
The text was updated successfully, but these errors were encountered:
Browser: Chrome 64.0.3282.167
OS: Windows 10 x64
Clappr Version: 0.2.86
Steps to reproduce:
Example:
hlsjsConfig: {
liveSyncDuration: 8,
liveMaxLatencyDuration: 18
},
This issue also happens with the player at http://cdn.clappr.io/ if the above criteria is met.
console error is:
hls.js:15328 Uncaught Error: Illegal hls.js config: don't mix up liveSyncDurationCount/liveMaxLatencyDurationCount and liveSyncDuration/liveMaxLatencyDuration
at new t (hls.js:15328)
at e._setup (hls.js:152)
at e.play (hls.js:354)
at e.play (container.js:301)
at e.clicked (poster.js:84)
at HTMLDivElement.r.proxy (zepto.js:1616)
I'm assuming Clappr is resetting values for liveSyncDurationCount+liveMaxLatencyDurationCount (notice the COUNT) upon attempting to restart stream, even though they should not be provided when using the NON-count values.
The text was updated successfully, but these errors were encountered: