What does HackerNews think of ffmpeg.wasm?
FFmpeg for browser and node, powered by WebAssembly
I wonder about the use of remote file operation terminology (e.g., upload, download) versus local (e.g., open, save) when using offline/local and privacy as an attraction.
Found a previous post from someone using that lib https://news.ycombinator.com/item?id=26580333
In the future https://www.w3.org/TR/webcodecs/ may allow for a native API to do this.
1. MediaRecorder (requires browser support) https://developer.mozilla.org/en-US/docs/Web/API/MediaStream...
2. ffmpeg.wasm https://github.com/ffmpegwasm/ffmpeg.wasm/
Maybe can package that up and monetize but… maybe hard to corner a market
No affiliation -- found it while searching for browser-based ports of FFmpeg.
https://github.com/GoogleChromeLabs/webm-wasm
Safari doesn't play webm files two options for that
1). you can convert webm to MP4 with or without re-encoding(will be faster) using ffmpeg or ffmpeg-wasm (within browser) https://github.com/ffmpegwasm/ffmpeg.wasm
2). Another option is play webm directly using wasm https://github.com/brion/ogv.js
Question: Are you compiling FFmpeg to WASM, or FFMpeg's libav and interfacing with that directly?
Also for anyone curious, the author of ffmpeg.wasm[1] has an excellent guide on compiling FFmpeg to WASM:
https://itnext.io/build-ffmpeg-webassembly-version-ffmpeg-js...
Modfy is a purely browser-based privacy-first video tool capable of performing tasks like converting, compression, etc without uploading your files.
I thought it would be cool to process video in the browser using Web Assembly and FFmpeg
The project is also open source and based on https://github.com/ffmpegwasm/ffmpeg.wasm
Let me know what you think!