Closed gkatsev closed 2 years ago
I've created a PR based off of this that integrates hls.js with contrib-quality-levels https://github.com/gkatsev/videojs-mux-kit/pull/1
I've updated the README to include how to import the new file and also add a note on how to get access to the live demo page.
maybe we update
player_software_version
to be:0.7.0-hls.js
or0.7.0-vhs
? That way from the Mux Data side of things we can see how the two different builds perform.
Something like that definitely is a good idea to do. Should it be the player_software_version
or maybe player_software_name
?
Is there a tech option in Mux data that could be set instead? Not really sure what's the best option.
@gkatsev mux metadata guide is here: https://docs.mux.com/guides/data/make-your-data-actionable-with-metadata
Yeah, I could see it going in player_software_name
, I don't feel strongly between that one or player_software_version
@dylanjha didn't see anything more appropriate. Decided to append it to the player-software-name as that seems a bit more appropriate to me compared to appending it to the version.
One small detail, otherwise QA is good and we should get this merged then follow up with a release!
This PR uses webpack env commands and alias options to output a separate
index.vhs.js
file that can be used with a defaultvideo.js
import and thus working with VHS. The default export will continue usinghls.js
. Thenpm run build
command will output both files.npm run dev
will run withhls.js
andnpm run dev:vhs
will run withvhs
.Fixes #62
~A next step, which probably should come in a separate PR is to integrate tech/hls.js with videojs-contrib-quality-levels.~ (This is taken care of in another PR) ~This is a WIP PR to switch videojs-mux-kit to use VHS. This is a minimal set of changes. I think it would be nice to be able to set up alternate builds that will use VHS or hls.js.~