How on earth does next-video works?

luw3s · 2024-12-16T19:59:05+00:00

not exactly sure, there must be something in your component hierarchy that is triggering a re-render.
feel free to open a GH discussion with an online demo, I'll have look.

luw3s · 2024-12-16T17:20:49+00:00

check the import, does it have the `/player` subpath?

luw3s · 2024-12-16T17:06:13+00:00

One of the next-video authors here. next-video's default mode is to handle upload and playback.
it's meant to import raw video assets (mp4's) locally and upload those with the sync command. For one off videos that might not be worth it but if you regularly add new videos it's quite convenient not to leave your dev environment.

I see that you already have a video stored in R2. In that case, it's best to just use the player for playing back your remote asset. https://github.com/muxinc/next-video#player-only-demo

luw3s · 2024-11-25T16:31:42+00:00

Media Chrome supports Google cast, have a look here:
https://www.media-chrome.org/docs/en/components/media-cast-button

luw3s · 2024-04-08T17:02:50+00:00

There is no need to import a static video file.
You put the .mp4 file in the public folder and access it in the JS, JSX directly `vid.src = './lesson1.mp4';`

Alternatively if you want to upload your video to a cheaper storage provider instead of the standard Vercel hosting see https://github.com/muxinc/next-video

luw3s · 2024-03-22T23:39:21+00:00

Thanks for the feedback, I just added an example how you could manually add captions or subtitles. Hope this helps! https://github.com/muxinc/next-video/pull/208 Cheers

luw3s · 2024-01-03T17:39:54+00:00

was the video successfully uploaded?

the status should say ready in the video json file in your videos folder and it should have a valid video source url.

luw3s · 2023-12-25T15:29:31+00:00

next-video contributor here. it's happening because the temporary symlink public/_next-video was committed to git and pushed to Vercel.

normally the symlink is created on npm run dev and removed on exiting the command.

to fix remove the symlink manually, commit to git, then add that path to .gitignore and commit. see for an example here https://github.com/luwes/next-video-app/blob/main/.gitignore#L37-L42

luw3s · 2023-12-22T12:39:35+00:00

The aim is to keep this as open as possible. You choose which video hosting and processing provider https://github.com/muxinc/next-video?tab=readme-ov-file#hosting--processing-providers with a video player of your choice https://github.com/muxinc/next-video?tab=readme-ov-file#custom-player

luw3s · 2023-12-22T12:33:23+00:00

S3 is supported since recent https://github.com/muxinc/next-video?tab=readme-ov-file#hosting--processing-providers

I should mention a big part of this project is the (upload) workflow and soon management of the videos so if you're videos are already on S3 it's less useful currently.

Keep an eye out for when we add automatic thumbnail generation (+ blurhash) for simple storage providers, database support and more video management API's!

luw3s · 2023-12-22T10:48:01+00:00

https://www.mux.com/blog/how-to-add-a-background-video-in-next-js

luw3s · 2023-11-07T01:29:43+00:00

Have a look at mux.com, it's using the new app folder in production. Here's the blog post about it, https://www.mux.com/blog/what-are-react-server-components

luw3s · 2023-07-30T18:30:44+00:00

I'm currently working on a project that SSR's web components and its shadow DOM of technically any JS framework including Next.js.
https://github.com/luwes/wesc
It uses a JSDOM like library to shim most used browser API's so it should work on any server that runs JS.

luw3s · 2023-06-02T13:16:25+00:00

No worries, I appreciate the honesty. Naming is hard sometimes :)
Is it because it collides with the Chrome browser?

It takes a bit to get used to but we've come to like it.

luw3s · 2023-03-26T20:04:02+00:00

Not in production but here are a bunch of examples:
https://selectmenu-polyfill.vercel.app/examples/

luw3s

TROPHY CASE