Handling multiple instances of hls.js

[survto]

Hi,
I am working on a web console that involves instantiating 3 HLS.js players .
HLS players randomly generate both MediaError (bufferStalledError) and NetworkError (manifestParsingError, audioTracklLoadError, levelLoadError). These errors cause continuous restarts of the players.
I noticed that as the number of players increases, the errors increase and the latency increases.
Are there any known issues about player behavior when we have multiple instances?
How resilient is the hls.js player?
Are there any workarounds or best practices to minimize the number of errors?
Thanks in advance

[robwalch]

You can instantiate as many instances of hls.js as you want, but you are responsible for performance. Parsing errors are a result of content issues, but stalling and network errors indicate an issue with resources on the client or server. To play media with an HLS.js instance you need an HTMLMediaElement. Not all platforms support playback with multiple (or many) elements. The number of hls.js instances should be limited based on platform resources. Three hls.js instances is a very reasonable number. You might want to consider enabling level capping (see capLevelToPlayerSize and capLevelOnFPSDrop in the API docs) so that each players selection is limited to its display area and lowers quality when frame drops are detected.