Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

videjs-hlsjs vs videojs-contrib-hls/videojs-http-streaming #93

Open
arski opened this issue Apr 22, 2019 · 3 comments
Open

videjs-hlsjs vs videojs-contrib-hls/videojs-http-streaming #93

arski opened this issue Apr 22, 2019 · 3 comments

Comments

@arski
Copy link

arski commented Apr 22, 2019

Hi there, curious if you can describe when and why someone would prefer to use this library (I guess in particular hls.js vs the videojs 'native' ones) - would be nice to see that in the readme maybe?

Thanks!

@teoeter
Copy link

teoeter commented Jul 17, 2019

fragmented mp4

@tri170391
Copy link
Contributor

tri170391 commented Jul 17, 2019

In general it's just 2 different "media engines" to play HLS with video.js as a UI. Depends on the particular stream it might work better if backed by hls.js (and also there's a lot of tuning you can do compared to vanilla vhs)

The trade-off is we are not really officially supported by video.js devs so interactions with videojs plugins is a little bit iffy but we covered some of the basic one alright.

@yurguis
Copy link

yurguis commented Jul 25, 2019

I had to look for an alternative to videojs' http-streaming hls handler and found out this plugin. It works very well with the version of videojs I use which is 7.4.1.
Only problem I found was the use of quality levels. What I finally did was to fork the project and expose hls so I can use it like with native hls.js, everything is working good so far.
Maybe some of the contributors could consider something like this.
Hls.js can handle custom attributes in playlists while with this plugin I could not access those atrributes to use them as labels for quality levels that's why I just added this line
tech.hls = _hls;
and I could work directly with hls.currentLevel as in documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants