staff, Administrators
1,593
edits
GstWebRTC - GstWebRTCSrc: Difference between revisions
no edit summary
Jcaballero (talk | contribs) No edit summary |
Jcaballero (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
== Architecture == | == 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. 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. | 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. | |||
<br /><br /> | |||
Table 1 summarizes the complete set of possible configurations. At the time being, only one pad of each media type can be created. | Table 1 summarizes the complete set of possible configurations. At the time being, only one pad of each media type can be created. | ||
<html> | <html> | ||
| Line 13: | Line 17: | ||
<tr> | <tr> | ||
<td>Audio Only</td> | <td>Audio Only</td> | ||
<td align="center" | <td align="center"><img src="http://developer.ridgerun.com/wiki/images/8/89/Gstwebrtcsrc-audio.png" width=600></img><figcaption>Figure 1: Receive Audio</figcaption></td> | ||
<td>Example Pipeline</td> | <td>Example Pipeline</td> | ||
</tr> | </tr> | ||