4 ms·
What on earth is a "pure webassembly/javascript port"? It's gotta be one or both of those to run in a browser regardless. Is it just ffmpeg compiled to wasm thr
by nynx 6y ago
What on earth is a "pure webassembly/javascript port"? It's gotta be one or both of those to run in a browser regardless. Is it just ffmpeg compiled to wasm through emscripten?
- xiphias2 6y agoIt's called a port because probably more work went into making it work than just recompiling.
- simlevesque 6y agothere is always two part to these ports: - a webassembly blob - a javascript wrapper to call the webassembly's functions from js in a practical way.
- thdc 6y agoThis is what it seems to be. The repo in this thread depends on another package which is the actual bulk of work: https://github.com/ffmpegwasm/ffmpeg.wasm-core https://github.com/ffmpegwasm/ffmpeg.wasm-core (fork of ffmpeg with emmake in a build script). There definitely does seem to be some other work in there in terms of getting it to actually work though. And tests.
- sp332 6y agoHere is a (soft paywalled) blog post about the "making of" this project. https://itnext.io/build-ffmpeg-webassembly-version-ffmpeg-js-part-2-compile-with-emscripten-4c581e8c9a16 https://itnext.io/build-ffmpeg-webassembly-version-ffmpeg-js...
- JeromeWu 6y agoYou can also check the same post in my blog: https://jeromewu.github.io/build-ffmpeg-webassembly-version-part-2-compile-with-emscripten/ https://jeromewu.github.io/build-ffmpeg-webassembly-version-...