Lessons in WebAssembly: Client Side Video Editing
summary
A team integrates FFmpeg compiled with Emscripten into a React Chrome OS app to enable offline client‑side editing, and trimming via FFmpeg works but is very slow — roughly three orders of magnitude compared to native; builds hit linker and asm.js issues, the Wasm binary is huge, and Chrome OS CPU limits make re‑encoding impractical. A pepper native client build runs much faster, and Rust shows better portability for Wasm moving forward.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:18Why We Built a Screen Recording and Video Editing App for Chrome Os
- 3:26Trimming or Shortening the Video
- 6:52Pepper Plug-In Api
- 8:50Performance
- 10:32Choose a Video Editing Library
- 10:58Ffmpeg
- 13:51Hello World to a Wasm File
- 16:09M Configure
- 18:13Demo
- 18:47Trim Functionality
- 24:03Web Assembly
related talks
27mVideo Editing in the Browser
37mBeyond the browser: Moving forward with a more Declarative Future with WebAssembly
27mNative Web Apps: React and WebAssembly to Rewrite Native Apps
41mLet's build with WebAssembly!
31mSplit Rendering TV Applications Using WASM
27mFast future with WebAssembly
28mWebAssembly: Of Portability, and Performance
29mWebAssembly - the Final Frontier