3 ms·
yeah i'm gonna need a TLDR of the major moving parts. how do you even do video editing in the browser? is there a "ffmpeg in the browser"? is that the basic bui
by swyx 2y ago
yeah i'm gonna need a TLDR of the major moving parts. how do you even do video editing in the browser? is there a "ffmpeg in the browser"? is that the basic building block?
- rizky05 2y agoActually it is: https://github.com/ffmpegwasm/ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm, but for this particular project it seems using mp4box from gpac
- pilaf 2y ago> is there a "ffmpeg in the browser"? I don't know if this project uses it, but there's ffmpeg.wasm [1]. 1: https://github.com/ffmpegwasm/ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm
- padenot 2y agoWe've been working on the Web Codecs API for a few years now. It only handles encoding and decoding media codecs, ffmpeg does much more (container handling, filters and everything needed really). Web Codecs can take a compressed media packet and get you the decoded image or audio buffer it corresponds to. Conversely it can take audio or images with timestamps and get you a series of encoded media packets you can then containerize (we say mux) and get you e.g. an mp4 file. https://w3c.github.io/webcodecs/ https://w3c.github.io/webcodecs/
- xfalcox 2y agoCan I just say that I was disappointed by the Web Codecs API leaving muxing the end result as a "draw the rest of the fucking owl" thing.