video.js VS hls.js

For people who like to watch with subtitles, VLC currently doesn't support streaming to chromecast with SRT subtitles.. there are several issues for it and I believe support is slated for the next major version of Chromecast, but not sure when that will be.

The typical "workaround" is to reencode the video file to include the subtitles directly, but that sounded like too much work, so I hacked together a static page using https://videojs.com/ to embed a player and load the video and subtitles in a browser window.

Here it is in gist form if anyone has a similar issue: https://gist.github.com/HartS/9bb2721fa73b6798efcdbf5c463e87...

This was hacked together as quickly as possible for my own needs, so definitely not intended to be an example of clean code. You need to run the python server separately to serve the SRT because video-js can't load it from a file URL IIRC

Thank you! This is the kind of creative solution I was looking for. Your comment helped me find video.js which has first-party support for opening M3U8 streams.

videojs is superior to basically everything. It's also open source...

Another option is looking at https://videojs.com/ with the Vimeo video file links.

I am woring with HTML - I managed to download a (m3u8) video. by inspecting the webpage (videojs.com).

🔀 Repositório no GitHub

Now, to display the HLS stream to viewers, we’ll use HLS.js, which we installed earlier. For more UI customizations, you can check out Video.js, which uses HLS.js internally.

Maybe videojs?

You can find real-life examples of customized HTML5 video players on YouTube, the Cloudinary Video Player, JWPlayer, and Video JS. Each of these websites or frameworks utilizes the power of CSS to customize their videos or allow their users to do the same.

It looks like the IJF has switched to using the Video.js player on their portal. I'm not sure what to think of that. This could be the IJF taking more control over their IP which is ultimately a good thing. If you want to watch specific matches and see when certain actions happen then you must use their portal.

Good point; there's only a single server handling all the requests so things can be a bit slow depending on the time of day. And there are browser limits to the number of concurrent connections.

Apple browsers with native HLS support are better than those without as well. Other browsers need to load everything via https://github.com/video-dev/hls.js/ which slows things down.

Another user using Ubuntu + Firefox just reported this issue recently. You're likely running into this issue - the streaming library we use requires a codec that some browsers have bundled, but Firefox is not one of them. It expects the OS to provide it, and it sounds like yours is not.

I'm trying to build a simple web player for Jellyfin, for another project I'm working on that will embed a clipper. I am using HLS.js to load HLS streams, which seems to work really well for movies, but not at all for shows.

If you mean hls.js https://github.com/video-dev/hls.js/, I prefer Shaka because it can play both HLS and DASH, adding tons of stuff on top of it

I don't know the answer to the WebRTC part, but as long as you have a server with not-outrageously-priced outbound bandwidth, you can install an open source RTMP server like SRS[1], and stream to that RTMP server from OBS. It's really easy, configure the RTMP server & stream key, then "Start Streaming" which is right next to "Start Recording". You can then hand your friends a link, and they can play it in any media player with RTMP/HLS/FLV stream support, or you can add a simple web UI with e.g. hls.js[2] (very easy to write, there might even be prepackaged solutions) so that they truly don't need to download anything.

[1] https://github.com/ossrs/srs

[2] https://github.com/video-dev/hls.js/

I think HLS.js solved the same issue for H264.

hls.js

https://github.com/video-dev/hls.js/ <--download the release.zip, unpack it, extract dist/hls.js and dist/hls.js.map you can discard the rest. Near as I can tell these do not contain any external HTTP calls, IE: it's fully self-contained.