ffmpeg.wasm

I have been running this for at least a year, it works great. I have it resizing video, and save to raw pixel data that I use to extract pixel color info for use in my web application. Anything ffmpeg does (except streaming because it doesn't have network access) can be done in the browser. https://github.com/ffmpegwasm/ffmpeg.wasm

Thank you FFmpeg developers and contributors! If there's anything that needs audio/video automation, I've always turned to FFmpeg, it's such a crucial and indispensible tool and so many online video tools use it and are generally a UI wrapper around this wonderful tool. TIL - there's FFmpeg.Wasm also [0]. In Jan 2024, I had used it to extract frames of 1993 anime movie in 15 minutes video segments, upscaled it using Real-ESRGAN-ncnn-vulkan [1] then recombining the output frames for final 4K upscaled anime [2]. FWIW, if I had built a UI on this workflow it could've become a tool similar to Topaz AI which is quite popular these days. [0]: https://github.com/ffmpegwasm/ffmpeg.wasm [1]: https://github.com/xinntao/Real-ESRGAN-ncnn-vulkan [2]: https://files.horizon.pics/3f6a47d0-429f-4024-a5e0-e85ceb0f6...

Great work on this - I made a terminal command similar to this (llmpeg), and was actively trying to get exactly this working - a webasm compiled version of ffmpeg that could encode in the browser. I for the life of me couldn't get the provided examples on https://github.com/ffmpegwasm/ffmpeg.wasm to run. Just for my own development curiosity, was there anything specific you had to do to get ffmpegwasm to work?

The JS ports of FFmpeg (or WASM port if you want the in-browser approach) are very old and would be more than present in modern LLM training datasets, albeit likely not enough of a proportion for LLMs to understand it well. https://github.com/Kagami/ffmpeg.js/ https://github.com/ffmpegwasm/ffmpeg.wasm

Like this? https://github.com/ffmpegwasm/ffmpeg.wasm

I get to be one of the lucky few to learn today that ffmpeg was ported (well, transpiled) to WASM. This is more specifically built on that port: https://github.com/ffmpegwasm/ffmpeg.wasm That project has an interactive playground that essentially describes and demonstrates how it works: https://ffmpegwasm.netlify.app/playground This also means that despite being a locally hosted ffmpeg frontend, it's still slower than native ffmpeg and bound to WASM limits like file size (still a generous 2GB for images and audio, but not as viable for big video conversions). Still weird that this project doesn't seem to acknowledge that anywhere.