4 ms·
How much work would be required to adapt this to use WebRTC with native H.264 instead of websockets with a javascript-based MPEG1 decoder implementation?
by 0x0 11y ago
How much work would be required to adapt this to use WebRTC with native H.264 instead of websockets with a javascript-based MPEG1 decoder implementation?
- icebraining 11y agoWhy WebRTC? I think that's more designed for Browser-to-Browser connections. You'd just need to stream an H.264 file using a <video> tag (and use a websocket for the input).
- tehbeard 11y agoStreaming an unbounded file to a <video> tag can have fairly significant delay compared to webRTC. It's really more designed for one to many situations (such as livestreams or VOD) than one to one low latency.
- cypher543 11y agoProbably not much. The WebRTC reference implementation[1] by Google and Mozilla is fairly easy to build and embed, assuming your Internet connection can handle a complete checkout of the Chromium repository. Unfortunately it only supports the VP8 codec for video. There is also OpenWebRTC[2] by Ericsson, but it doesn't work on Windows. [1]: http://www.webrtc.org/native-code/development http://www.webrtc.org/native-code/development [2]: http://www.openwebrtc.io/ http://www.openwebrtc.io/
- dharma1 11y agoThere's VP9 too - https://plus.google.com/+JustinUberti/posts/3FLVapCvDaG https://plus.google.com/+JustinUberti/posts/3FLVapCvDaG