GstKinesisWebRTC Configurations
| GstKinesisWebRTC Amazon Kinesis WebRTC GStreamer Plugin |
|---|
|
| Context Overview |
| GstKinesisWebrtc Description |
| Evaluating GstKinesisWebRTC |
| Getting the code |
| Building GstKinesisWebRTC |
| Getting Started |
| Contact Us |
The kinesiswebrtcbin can be used as a sender-receiver endpoint. It can be configured to have the role of Master or Viewer. The element Master role means it can send audio and video and receive multiple streams of audio and video pairs. As a Master, the element can only have 2 sink pads, one for audio and one for video streams. Similarly, the Viewer can only have 2 sink pads, with the difference that it can only receive a single audio and video pair that will come from the Master. For both cases, the pipeline configuration will determine if it sends only audio, only video, or audio and video.
On the other hand, the element can create multiple source pads, which will be determined by the connected viewers or master, depending on the configured role. The element can receive video and audio streaming from each connected viewer when on Master role, and only the video and audio streaming from the connected master when on Viewer role. The corresponding pads will be created when the stream arrives through the peer-to-peer connection. So as you can imagine the source pads of kinesiswebrtcbin are sometimes and will be created dynamically.
The element can send and receive audio and video simultaneously, or just audio or just video. The pipeline configuration determines what will be sent over WebRTC and pushed down the pipeline.
