Frequently Asked Questions
Follow Us On
 | The RidgeRun GStreamer Browser Sink documentation from RidgeRun is presently being developed. |
- What technology does GstRrBrowserSink use underneath?
- GstRrBrowserSink is a striped down version of WebRTC. It's still compliant and valid WebRTC, but with the bare minimum features it needs to operate.
- What's wrong with existing WebRTC solutions?
- There's nothing wrong with them, they're just considerably more complex to setup. And complexity usually comes with fragility. GstRrBrowserSink was designed to be simple, work out of the box, and require no external setup.
- Do I need an internet connection to use GstRrBrowserSink?
- No. You can stream fully on localhost.
- Are there any plans to support audio and data channel?
- Audio, maybe. Data channel probably not. At the time being we are only considering features that will not compromise the usability of the project.
- Are there any plans to stream through the internet?
- No. Our goal is not to simplify WebRTC, is to provide means to deliver live video to a local GUI on a browser. If you need NAT traversal, signaling, etc... you're probably better off with a more complete WebRTC stack.
- What codec formats are supported?
- Currently only H264 is supported. To favor latency, only the Baseline profile is supported. Codec compatibility with the browser is a major pain point and we want to avoid users dealing with it. By keeping the support to one codec we can test multiple browsers, devices and operating systems. Having said that, if your want a new codec you can sponsor this effort.