ffmpeg-python VS ffmpeg.wasm

Even given an option it can be difficult to find the corresponding documentation, if only because of the many different submodules and encoders and decoders and filters that have o-so-slightly different options. That said, I've just switched from pydub to ffmpeg-python (due to memory issues of the former[1]) and judging from the Jupiter notebook[2] it seems a much more intuitive method of constructing ffmpeg pipelines.

[1] https://github.com/jiaaro/pydub/issues/135

[2] https://github.com/kkroening/ffmpeg-python/tree/master/examp...

You might want to look into ffmpeg-python as well

This bug on github sounds like the same issue you have

take a look at https://github.com/kkroening/ffmpeg-python

The ffmpeg-python python package still makes use of the “future” python package (search for “past” in the code base). These should be removed and updated as necessary.

I've had a look through these examples, but I can't get the numpy conversion to work (I get broken pipe errors, but if any of you can get it working this solution would be ideal)

Your going to be wanting to enumerate all the files in a folder, shuffle them, and then use a library for splicing them together. A quick google search brought me to moviePy, which seems pretty solid. ffmpeg is the industry standard for programmatically working with video, but it's...complicated to say the least. Looks like there are some good python bindings for it, but it may be overkill for this project. I'm sure there are others out there too.

stitching [0], [1], and [2]

[0]https://github.com/kkroening/ffmpeg-python#quickstart

[1]https://kkroening.github.io/ffmpeg-python/#ffmpeg.zoompan

[2]https://ffmpeg.org/ffmpeg-filters.html#Examples-133

I've been using ffmpeg-python recently, and it will do a lot of the crazy complex transforms for you, and you can write sane python code vs. trying to deal with the crazy default ffmpeg syntax.

https://github.com/kkroening/ffmpeg-python

ffmpeg is the traditional Swiss Army knife for video stuff. there's a Python library out there. might not be appropriate in an embedded environment though, it's a bit of a beast.

There's already ffmpeg wasm. I've used it in projects. Works great.

https://github.com/ffmpegwasm/ffmpeg.wasm

There's a low-hanging fruit that I think would make ffmpeg more helpful for regular people.

There's a million terrible websites that offer file conversion services. They're ad-ridden, with god-knows-what privacy/security postures. There's little reason for users to need to upload their files to a third-party when they can do it locally. But getting them to download fiddly technical software is tough - and they're right to mistrust it.

So, there's a WASM version of ffmpeg, already working and hosted at Netlify [1]. It downloads the WASM bundle to your browser and you can run conversions/transformations as you wish, in your browser. Sandboxed and pretty performant too!

If this tool a) was updated regularly b) had a nicer, non-CLI UI for everyday users and c) was available at an easily-Googlable domain name - it would solve all the problems I mentioned above.

[1]: https://ffmpegwasm.netlify.app/

As their github page says, based on https://ffmpegwasm.netlify.app ...

I'm guessing no one did GPU-optimizations? I saw a web app (not an ffmpeg transpilation) that went clever and used WebGL so it can access the GPU and use its parallel processing capabilities...

ffmpeg.wasm: The engine making all these happen. However, I’m a bit concerned about its current situation. The repo has not been updated for more than six months now, and that’s not a healthy sign for an open-source project. Clearly I was reading the commits wrong. The author mentioned “speed up x264 with SIMD intrinsics” in their roadmap (https://github.com/ffmpegwasm/ffmpeg.wasm/discussions/415), which, if landed, could make such on-device video editors much more competitive.

I use https://github.com/ffmpegwasm/ffmpeg.wasm and I want my FFMPEG commands to be hidden from others.

Possibly using this? https://github.com/ffmpegwasm/ffmpeg.wasm

You could try using something like ffmpeg wasm which is a way of using ffmpeg client side in browser. Unfortunately WebAssembly only supports files less than 2 gigabytes, which is a problem for videos. And I don't know if ffmpeg wasm contains ffprobe, so you might have to find another project or try to compile ffprobe to wasm yourself. This stuff is out of my wheelhouse so I can't offer much help.