staff, Administrators
1,593
edits
GstWebRTC - GstWebRTC Basics: Difference between revisions
no edit summary
Jcaballero (talk | contribs) No edit summary |
Jcaballero (talk | contribs) No edit summary |
||
| Line 33: | Line 33: | ||
=== Direction === | === Direction === | ||
RidgeRun's GstWebRTCSink and GstWebRTCSrc are used as standard GStreamer sink and source elements respectively. If a pipeline only uses the sink element, it becomes a send-only endpoint. | RidgeRun's GstWebRTCSink and GstWebRTCSrc are used as standard GStreamer sink and source elements respectively. If a pipeline only uses the sink element, it becomes a send-only endpoint. | ||
[[File:Gstwebrtc-sendonly.png|600px|thumb|center|Figure 1. Pipeline as a WebRTC send-only endpoint.]] | [[File:Gstwebrtc-sendonly.png|600px|thumb|center|Figure 1. Pipeline as a WebRTC send-only endpoint.]] | ||
Similarly, if a pipeline only uses the source it becomes a receive-only endpoint. | |||
[[File:Gstwebrtc-receiveonly.png|600px|thumb|center|Figure 2. Pipeline as a WebRTC receive-only endpoint.]] | [[File:Gstwebrtc-receiveonly.png|600px|thumb|center|Figure 2. Pipeline as a WebRTC receive-only endpoint.]] | ||
Finally, by using the both elements the pipeline behaves as a bidirectional endpoint. Figures 1, 2 and 3 show the scenarios described above, respectively. | |||
[[File:Gstwebrtc-sendreceive.png|400px|thumb|center|Figure 3. Pipeline as a WebRTC send-receive endpoint.]] | [[File:Gstwebrtc-sendreceive.png|400px|thumb|center|Figure 3. Pipeline as a WebRTC send-receive endpoint.]] | ||
=== Media Type === | === Media Type === | ||