Skip to content

WebGear_RTC FAQs⚓


What is WebGear_RTC API and what does it do?⚓

Answer: WebGear_RTC utilizes WebRTC technology under the hood, which makes it suitable for building powerful video-streaming solutions for all modern browsers as well as native clients available on all major platforms. For more info. see WebGear_RTC doc ➶


How to get started with WebGear_RTC API?⚓

Answer: See WebGear_RTC doc ➶. Still in doubt, then ask us on Gitter ➶ Community channel.


How WebGear_RTC is different to WebGear API, which should I choose?⚓

Answer: WebGear_RTC is similar to WeGear API in many aspects but utilizes WebRTC technology under the hood instead of Motion JPEG. You can choose any API according to your application, but the quality would be better on WebGear API, on-the-other-hand latency would be better on WebGear_RTC API. Also, WebRTC protocol accepts a wide range of devices, whereas WebGear is limited only to modern browsers.


"WebGear_RTC is throwing ModuleNotFoundError on importing", Why?⚓

Answer: This error means, VidGear is installed WITHOUT asyncio package support on your machine. For this support, see Requirements ➶.


Can WebGear_RTC always need Active Internet Connection?⚓

Answer: No, it just need internet only once during its Auto-Generation Process ➶ to download default data-files and it takes few seconds. You can also download files manually from Github Server, otherwise you can also add your own custom files. For more information see Data-Files Auto-Generation WorkFlow ➶


Is it possible to stream on a different device on the network with WebGear_RTC?⚓

If you set "" as host value instead of "localhost" on Host Machine, then you must still use http://localhost:8000/ to access stream on your host machine browser.

For accessing WebGear_RTC on different Client Devices on the network, use "" as host value instead of "localhost" on Host Machine. Then type the IP-address of source machine followed by the defined port value in your desired Client Device's browser (for e.g. to access the stream.


Can I manually place default files for WebGear_RTC?⚓

Answer: Yes, you can either download default files from Github Server, and manually place at default location, OR, you can yourself create the require three critical files (i.e index.html, 404.html & 500.html) inside templates folder at the default location, thereby you don't need any internet connection at all. For more information see Data-Files Auto-Generation WorkFlow ➶


How to stream Webgear_RTC Server output to multiple clients?⚓

Answer: See this usage example ➶.


How to send OpenCV frames directly to Webgear_RTC Server?⚓

Answer: See this usage example ➶.


How can I add my custom WebPage to WebGear_RTC?⚓

Answer: See this usage example ➶.


How can to add CORS headers to WebGear_RTC?⚓

Answer: See this usage example ➶.


Can I change the default location?⚓

Answer: Yes, you can use WebGear_RTC's custom_data_location attribute of option parameter in WebGear_RTC API, to change default location to somewhere else.


Can I delete/rename the WebGear_RTC default data?⚓

Answer: Yes, but you've to follow these rules ➶


Last update: October 7, 2021