-
-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does it compare with ffmpeg.js? #75
Comments
Yes please address this in the README. |
Both ffmpeg.wasm and ffmpeg.js are built using emscripten, but ffmpeg.js does not output WASM.
$ npm install ffmpeg.js@4.2.9003
$ tree node_modules/ffmpeg.js
├── COPYING.GPLv2
├── COPYING.LGPLv2.1
├── LICENSE.MP4
├── LICENSE.WEBM
├── README.md
├── ffmpeg-mp4.js
├── ffmpeg-webm.js
├── ffmpeg-worker-mp4.js
├── ffmpeg-worker-webm.js
└── package.json In contrast, ffmpeg.wasm uses WASM threads and is fast, but this requires SharedArrayBuffer, which is difficult to implement due to Spectre, so it will only work on Chrome 74 or later. |
Thanks a lot for the explanations. |
I took a stab at porting som of the SIMD code for x264 to intrinsics (https://github.com/AlexVestin/x264-simd). There's definitely some room for speedups, though I couldn't get it match the native (relative) performance. Also since it's not released yet (although it seems to be coming soonisch) it might be worth to wait for something like WebCodecs |
@AlexVestin Looking forward to x264-simd! I believe it will be a huge speed up to ffmpeg.wasm! |
Hey! It would be nice if there was some explanations about the differences with ffmpeg.js
There is a big warning at the beginning of the README, but nothing more than that.
The text was updated successfully, but these errors were encountered: