ffmpegwasm / ffmpegwasm/ffmpeg.wasm
Is it at all possible to simplify usage of the library?
- Dominant language
- C
- Stars
- 17.8k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Node isn't supported, so why is npm still the installation method? SharedArrayBuffer requires closed CORS policy, so why is the starter example referencing unpkg? Why is unpkg baked into the code at all?
Also, is the global class supposed to be FFmpeg or FFmpegWASM?
**Describe the solution you'd like**
Why not just make it a single front facing import file (or two to separate esd from umd) with a directory tree that's consistent?
A lot of us don't have the ability to install anything on our web service providers (or even terminals at all). We have to self host the library anyway. Let us just unzip a release file into the directory of our choice
**Additional context**
That's all. Please excuse any frustration latent in the text. Version 10 worked fine until I hit iOS support...
Contributor guide
Assessment
This issue has not been assessed yet.