GstKinesisWebRTC/Description/Configurations

From RidgeRun Developer Wiki
Revision as of 17:24, 9 October 2022 by Mmontero (talk | contribs) (Created page with "The kinesiswebrtcbin can be used as a sender-receiver endpoint. The element master role means It can send audio and video and receive multiple streams of audio and video pairs...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The kinesiswebrtcbin can be used as a sender-receiver endpoint. The element master role means It can send audio and video and receive multiple streams of audio and video pairs. As master the element can only have 2 source pads one for audio and one for video streams. However 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 sink pads, which will be determined by the connected viewers. The element can receive video and audio streaming from each connected viewer and the corresponding pads will be created when the stream arrives through the peer-to-peer connection. So as you can imagine the sink 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 sended over WebRTC and pushed down the pipeline.