This is amazing. We also kind of created a Player context provider and was using it to maintain/mutate player state globally. If its possible to also share any examples related to player events and new way to register plugins in V10, that would also help better understand the overall picture.
Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
41–50 of 170 posts
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#42Earlier quoted context omitted.
Hey VJS core contributor here. We definitely feel that concern and we also don't yet have a silver bullet formalized. I suspect we'll need some kind of alternate implementations or feature augmentation at some point. We're currently doing things in a bit more ad hoc way, such as the interrelationship between PiP and Fullscreen (see, e.g.: https://github.com/videojs/v10/blob/main/packages/core/src/d... ).
One other thing to note: because the features are "composed", we at least have a lot of flexibility here that makes me feel pretty good about the fundamentals and not "coding ourselves into a corner" here.
Yeah the composability buys you a lot of room. One central store with events, inject it into each feature, and they stay decoupled without painting yourself in.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#43Serious question. We currently have this tool in our framework, that we use to play videos from youtube, vimeo, and a whole lot of other sites: https://github.com/Qbix/Platform/blob/main/platform/plugins/... We currently already use video.js, and our framework us used all over the place, so we’d be the perfect use case for you guys. How would we use video.js 10 instead, and for what? We would like to load a small vid…
That's great! It looks like you have a pretty extensive integration with the prior version of Video.js, so migrating will take some work, but I think worth it when you can make the time. That said, for Beta it works with browser-supported formats and HLS, with support for services like Youtube and Vimeo close behind as we migrate what we haver in the Media Chrome ecosystem[1]. So if that's what you need maybe hold your breath for a few weeks.
What are you supporting today that requires Wowza or Red5? The short answer is Video.js is only the front-end so it won't help the server side of live streaming much. I'm of course happy to recommend services that make that part easier though.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#44Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#45Probably not base case but a quick test to replace my audio player (currently using Plyr) turned up the following gaps for me, at least with the out-of-the-box code.
1. No playback rates under 1
2. No volume rocker on mobile
3. Would appreciate having seek buttons on mobile too
4. No (easily apparent) way to add an accent color, stuck with boring monochrome
5. Docs lacked clear example/demo/playground so I wasn't sure what it would look like until implemented
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#46I've never used video.js, and the site/advertising seems to be fairly oriented towards people who have used it or are familiar with it.
I had one question I couldn't answer reading the site: what makes this different from the native html video element?
AFAICT just the transport controls?
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#47Probably not base case but a quick test to replace my audio player (currently using Plyr) turned up the following gaps for me, at least with the out-of-the-box code. 1. No playback rates under 1 2. No volume rocker on mobile 3. Would appreciate having seek buttons on mobile too 4. No (easily apparent) way to add an accent color, stuck with boring monochrome 5. Docs lacked clear example/demo/playground so I wasn't sur…
All solid feedback, thanks! I'm making sure these get captured as issues. Otherwise we're closely tracking feature parity with Plyr (and other players) and our goal is to have full parity by GA, aiming for the middle of the year.
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#48Serious question. We currently have this tool in our framework, that we use to play videos from youtube, vimeo, and a whole lot of other sites: https://github.com/Qbix/Platform/blob/main/platform/plugins/... We currently already use video.js, and our framework us used all over the place, so we’d be the perfect use case for you guys. How would we use video.js 10 instead, and for what? We would like to load a small vid…
That's great! It looks like you have a pretty extensive integration with the prior version of Video.js, so migrating will take some work, but I think worth it when you can make the time. That said, for Beta it works with browser-supported formats and HLS, with support for services like Youtube and Vimeo close behind as we migrate what we haver in the Media Chrome ecosystem[1]. So if that's what you need maybe hold yo…
Thank you for your feedback. Yep I definitely understand that Video.js is just the front end. I want to avoid using Wowza / Red5 and just want to serve chunks of video files, essentially, buffering them and pasting them to the "end of the stream" laying down tracks ahead of the video.js train riding over those tracks.
So I'm just wondering whether we can do streaming that way, and video.js can "just work" to play the video as we fetch chunks ahead of it ("buffering" without streaming servers, just basic HTTP range requests or similar).
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#49Seeking on the main https://videojs.org/ page doesn't work for me on chromium.
Throws Uncaught (in promise) TypeError: AbortSignal.any is not a function on volume-slider-data-attrs.BOpj3NK1.js
Re: Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller
#50Seeking on the main https://videojs.org/ page doesn't work for me on chromium. Throws Uncaught (in promise) TypeError: AbortSignal.any is not a function on volume-slider-data-attrs.BOpj3NK1.js
Hey there, on the Video.js team. What browser and version did you run into this on?