GstWebRTC - GstWebRTCSrc: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
No edit summary
Line 23: Line 23:
   <td>Video Only</td>
   <td>Video Only</td>
   <td align="center"><img src="http://developer.ridgerun.com/wiki/images/6/69/Gstwebrtcsrc-video.png" width=600></img><figcaption>Figure 2: Receive Video</figcaption></td>
   <td align="center"><img src="http://developer.ridgerun.com/wiki/images/6/69/Gstwebrtcsrc-video.png" width=600></img><figcaption>Figure 2: Receive Video</figcaption></td>
   <td>Example Pipeline</td>
   <td><a href=http://developer.ridgerun.com/wiki/index.php?title=GstWebRTC_-_H264_Examples#Receive_Pipeline>Example Pipeline</a></td>
</tr>
</tr>
<tr>
<tr>

Revision as of 17:46, 12 July 2017


WebRTC Fundamentals


Home

Evaluating GstWebRTC



This pages gives an overview of the GstWebRTCSrc element.

Architecture

RidgeRun's GstWebRTCSrc is used as a standard GStreamer source element. If a pipeline uses the GstWebRTCSource element, it becomes a receive-only endpoint. GstWebRTCSrc element may receive audio, video or both simultaneously.

Configurations

The supported capabilities are determined at runtime based on the pads that were requested for the elements. Simply said, if a GstWebRTCSrc was created with video and audio pads, it will be capable of receiving both medias. Table 1 summarizes the complete set of possible configurations. At the time being, only one pad of each media type can be created.

Audio Only
Figure 1: Receive Audio
Example Pipeline
Video Only
Figure 2: Receive Video
Example Pipeline
Audio + Video
Figure 3: Receive Audio and Video
Example Pipeline
Table 1. GstWebRTCSrc Supported Capabilities




WebRTC Fundamentals


Home

Evaluating GstWebRTC