tejaswigowda

Absolutely. Audio extraction, format conversion, loudness normalization are all there. If you have a specific TTS pipeline in mind the raw FFmpeg mode should handle most of it.

WASM SIMD is 128-bit wide as dtf noted, so AVX-512 won't apply here. Longer term, WebGPU could be a more interesting path for compute acceleration in the browser than SIMD widening.

Active development -- PR just came in from luispa. Happy to review contributions.

Thank you! Reviewed and merged!

~4x slower than native for encoding, which is acceptable for clips under 5 mins. No hardware encoding -- WASM is CPU-bound, for now. WebCodecs could bridge that gap in future.

It already does -- trim, crop, concatenate, picture-in-picture, side-by-side, subtitle embedding. What would you add? Let's make it happen.

Fair. The emojis are a style choice -- I find them useful as visual anchors when scanning a long feature list. The code is in docs/ either way.

The browser-as-runtime has one property nothing else has: zero install on every OS. For sensitive files for medical, legal, personal. It's also the only architecture where you can verifiably prove data never left the device.

My personal pain point. I teach entertainment engineering at univ. We need this. All the time. Getting IT to install this in a classroom is a pain. It has already reduced my pain regarding this (anecdotal, yes. But I see the results and am planning to do a usability study). Thought it might be useful to someone else.

This is a great addition! You can use the raw ffmpeg mode to do this currently if you know the flag syntax

Whisper.cpp for local speech transcription and WebLLM for in-browser LLM inference follow the same pattern. We're calling this the Web-CLI architecture. A paper is in progress.