When will it become practical to run Linux inside the browser using WASM?
FFmpeg-online: ffpmeg running on the browser
11–20 of 31 posts
Re: FFmpeg-online: ffpmeg running on the browser
#12When will it become practical to run Linux inside the browser using WASM?
[deleted]
Re: FFmpeg-online: ffpmeg running on the browser
#13When will it become practical to run Linux inside the browser using WASM?
Probably before WASM bytecode can manipulate the DOM without JavaScript.
The browser seems on track to do everything except giving first-class support for other languages.
I've been studying the WebGPU API, which seems good, and visions of even our game engines being written in JavaScript are continually before my eyes.
Re: FFmpeg-online: ffpmeg running on the browser
#14When will it become practical to run Linux inside the browser using WASM?
It’s been possible for years. I’m not sure what a good definition of “practical” would be though.
Re: FFmpeg-online: ffpmeg running on the browser
#15Anyone know what the browser support is likely to be for this?
I’m working on something right now where I’m having to use a web service to merge an mp3 and mp4. Doesn’t even need to re-encode. So this might be perfect if a decent amount of browsers can run it.
Re: FFmpeg-online: ffpmeg running on the browser
#16As their github page says, based on 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...
The 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.
Re: FFmpeg-online: ffpmeg running on the browser
#17Similar, but nicer UI: https://ffmpeg.app
Re: FFmpeg-online: ffpmeg running on the browser
#18Or better use the WebCodecs API to be able to use your hardware encoding and decoding facilities.
Generally speaking, CPU decoding isn't that slow in the first place (compared to any kind of encoding), and hardware encoding is low-quality and lacking in options.
Hardware encoding is great for quickly getting a camera feed to disk at a non-professional quality level, but it's hard to imagine ever using it to do a re-encode of anything -- where you usually want to prioritize quality and a smaller size over encoding speed.
Re: FFmpeg-online: ffpmeg running on the browser
#19As their github page says, based on 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...
The 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.
They could use the WebCodec APIs to decode frames using the hardware, similar to how ffmpeg already supports VA-API for hardware decoding.
Re: FFmpeg-online: ffpmeg running on the browser
#20Related:
ffmpeg.wasm – a pure WebAssembly / JavaScript port of FFmpeg - https://news.ycombinator.com/item?id=33794122 - Nov 2022 (23 comments)
FFmpeg for browser and Node, powered by WebAssembly - https://news.ycombinator.com/item?id=28251801 - Aug 2021 (87 comments)
A pure WebAssembly / JavaScript port of FFmpeg - https://news.ycombinator.com/item?id=24987861 - Nov 2020 (125 comments)