This is a list of questions that have been asked about rtc.io via twitter (and sometimes via an rtc-io repository issue).
We've attempted to provide answers here, and also working examples that can be run using the rtc-faq command-line helper tool.
More information on how to use the rtc-faq tool can be found in the README.
@silviapfeiffer Hi Silvia, playing w/ rtc.io, I was wondering how to switch from video+audio to audio-only w/out restarting the connection?
— ju (@delphiki) September 26, 2014Capture and negotiate on a video stream, then disable the video track in the captured stream.
Capture and negotiate on a video stream, then capture an audio only stream and replace the original stream with the audio only stream.
replace-captured-mediaBoth the solutions above require features of WebRTC or media streams that are currently only implemented in Chrome.
When using rtc-quickconnect in reactive mode, I am seeing a blank video element created before I have captured any media. How can I fix this?
What you are seeing here is a "default" stream that is added by Chrome when a peer connection is initiated with no "real" streams or data channels.
The best way you can prevent this displaying is through checking whether the stream you have received can actually play media. For ease of use,
this functionality has been built into an experimental rtc-ui package which can be used to
handle rendering video elements.
A demo using the rtc-ui package to handle switching between webcam capture is available below.
NOTE: to try this demo out, you will need to install the rtc.io screen capture extension and browse to the page on HTTPS (screen capture is only permitted on HTTPS).
dynamic-screenshare