I mentioned ffmpeg before. It's a little command line tool that's a real powerhouse when it comes to media production. If you're creating videos or need to transcode existing videos, or turning video in the a sequence of images, or an animated gif, ... I could go on for a while longer, but I guess you catch my drift. Yes, I am an ffmpeg fanboy. Or more generally, I'm a fan of any piece of software that does something really well reliably. But I digress...

Recently I learned that ffmpeg is now ,in fact, available in the browser (thank you @aidan.wyber !). Needless to say this was the perfect opportunity to give ffmpeg.wasm a try. It took a bit of fiddling about, but I got it working. So now I can press a button and after some time a 30 second mp4 rolls into my Downloads folder that I can just throw online and nobody complains. No more running scripts offline and copying files all over the place.

I need to note though that the rendering process is relatively slow. That 30s clip takes about 5 minutes to render. Though I don't think my manual transcoding process is any faster. And it's not like I have to site there and watch the logs. I can actually do something else (note to self).

In case you want to see this in action, you'll need to run the project locally. The ffmpeg recorder is only available in development mode, as the wasm file is around 30MB. Didn't want to be pushing that to everybody's phone... Code is on my GitHub. Have fun!

-> go to genuary.d17e.dev for endless variations

#genuary #genuary25 #genuary16 #JS #SVG #svelte #codeart #svgart #gradients #mixbox