https://sporttotal-tv.github.io/debug-player/index.html
We discovered the following behaviour by experimenting with livetimeout:
| value | behaviour |
|---|---|
livetimeout: 90 |
Our default. Causes error 230001 to happen in 90% right after the ad. Other values as 30 or 15 produce the same result |
livetimeout: 0 |
Plays the stream for ~10s, then a loading spinner appears. Can be dismissed by clicking on LIVE next to the volume controls, but appears almost immediately |
no livetimeout in setup |
Plays the stream for about ~10s, then shows a loading spinner for ~1 .. 2 seconds, and then displays Error 230001 |
From the documentation:
Set to 0 to configure a stream to never time out. The player will continue requesting manifests until it times out. If a live manifest does not update after being requested for longer than liveTimeout, the stream will end with an error event. If you want a stream to end immediately, include an end tag in the manifest. This configuration option only handles stalled manifests, not issues with segment loading. A chunk that results in a 404, for example, will still error out.
npm i
http-server <projectfolder>
(or you can use any other local server)
By default the project will try to load the 1st active soccer game from sporttotal.tv's events schedule. If there is no game in progress, the players will error out. You can paste your own test stream m3u8 url into the input field and click Load custom - this will swap the source in jwplayer.
There's also a video.js player in here to proof that the issue is actually only in jwplayer. The sporttotal.tv website however relies on jwplayer atm. The video.js player will also not swap sources via Load custom at the moment...