Dan Rossi

This causes a stack issue, as the player tries to autoload instead of after clicking. Can't turn off autoloading ``` player.on("error", () => { player.pause(); player.trigger("ended"); player.reset(); player.src(player.currentSrc()); }); ```

An offline stream will go to error but no way to click to try and play again. Setting the src will try and start loading again.

An example fiddle I found. With a non existent manifest, you cant click to try and load again https://jsfiddle.net/m3sf8nav/

I've built an offline reconnect feature. Tested with HLS and Wowza. https://videojs.electroteque.org/offline

I have the same issue I am reading udp packets and sending to websocket. What else does it need ? my buffer is closing.

Does the data need to be parsed or reconstructed before sending to mux ? Something to be dependancyless of ffmpeg would be nice. The UDP packet size seems to be...

Is there any update to this. Is there a requirement to queue frames and send a certain number of frames or does it need segmenting on the server side first...

I've just found the possible issue passing through user clicks from the main player. For pro videos with the controls is disabled. It won't capture gestures then and reliant on...

An official pseudo player function. The player with controls disabled for pro videos isn't getting user clicks when clicking the overlay so pip won't work. https://dev.electroteque.org/vimeo/index5.html

Some tricks I tried failed. It's not getting user click to the iframe with the layer on top. With controls: 0 it should toggle the player. Then I can temporarily...