3 ms·
> i'm not talking about GUI but rather the camera/picture processing. That's usually done by the browser when using WebRTC (except for postprocessing, e.g. bac
by lxgr 3y ago
> i'm not talking about GUI but rather the camera/picture processing.
That's usually done by the browser when using WebRTC (except for postprocessing, e.g. background blur), not the application (using WASM or JavaScript).
Some browsers do this in hardware, others don't – just like some native videoconferencing applications are horrible CPU hogs, and others are quite efficient.