2 ms·
As their github page says, based on https://ffmpegwasm.netlify.app https://ffmpegwasm.netlify.app ... I'm guessing no one did GPU-optimizations? I saw a web ap
by netsharc 3y ago
As their github page says, based on https://ffmpegwasm.netlify.app https://ffmpegwasm.netlify.app ...
I'm guessing no one did GPU-optimizations? I saw a web app (not an ffmpeg transpilation) that went clever and used WebGL so it can access the GPU and use its parallel processing capabilities...
- xyst 3y agoIt’s nice if you have a modern computer, but I wonder what happens when the client has a very old computer or a “Chromebook”. Will the experience for those low end computers be degraded? It’s been awhile since I actually used ffmeg directly but I do recall trying to transcode some video to a different format and it took some time on a 2015 MacBook (not a MBP, like a thinner version of the MBA, lol)
- devwastaken 3y agoThe algs for media codecs are typically in handwritten assembly in combination with C. Actual GPU hardware acceleration implements specific media algorithms in hardware and is not accessible from the browser. I'm not aware of any kind of gpu codec algs that work in browser.
- johntb86 3y agoThey could use the WebCodec APIs to decode frames using the hardware, similar to how ffmpeg already supports VA-API for hardware decoding.