staff, Administrators
1,593
edits
GstWebRTC - GstWebRTCBin: Difference between revisions
no edit summary
Jcaballero (talk | contribs) No edit summary |
Jcaballero (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
Ridgerun's GstWebRTCBin can be used as a sender-receiver endpoint, as shown in Figure 1. If a pipeline uses GstWebRTCBin element, it becomes a send-receive endpoint. GstWebRTCBin may receive and send audio, video or both simultaneously. | Ridgerun's GstWebRTCBin can be used as a sender-receiver endpoint, as shown in Figure 1. If a pipeline uses GstWebRTCBin element, it becomes a send-receive endpoint. GstWebRTCBin may receive and send audio, video or both simultaneously. | ||
<br /> | <br /> | ||
=== Configurations === | === Configurations === | ||
The supported capabilities are determined at runtime based on the pads that were requested for the elements. Simply said, if a GstWebRTCBin was created with video and audio pads, it will be capable of sending and 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. | The supported capabilities are determined at runtime based on the pads that were requested for the elements. Simply said, if a GstWebRTCBin was created with video and audio pads, it will be capable of sending and 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. | ||
<html> | <html> | ||
<center> | <center> | ||