You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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.
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!
The text was updated successfully, but these errors were encountered: