7 ms·
Mumble web clients exist. They are limited to what the browser allows with respect to TCP and UDP access. So they need some sort of websocket proxy to work. An
by upofadown 7y ago
Mumble web clients exist. They are limited to what the browser allows with respect to TCP and UDP access. So they need some sort of websocket proxy to work.
Another example of why web apps are inherently limited I suppose...
- giancarlostoro 7y agoI was implying the voice implementation on the backend should natively support audio streaming to the web. Its nothing new and Discord does it. Hacking it to work is not going to be perfect.
- lmz 7y agoIt seems Mumble uses speex as the codec. Not sure how well that's supported by the browsers.
- mgamache 7y agoFlash supported Speex I wonder if that’s part of why it’s used
- upofadown 7y agoNormally Opus these days. Which is what the web client uses. * https://github.com/Johni0702/mumble-web https://github.com/Johni0702/mumble-web
- lmz 7y agoTechnically browsers have WebRTC and can do Opus without the emscripten compiled libopus, but I guess the Mumble server won't support WebRTC's RTP stream.