GstWebRTC - GstWebRTCBin: Difference between revisions
Jcaballero (talk | contribs) No edit summary |
Jcaballero (talk | contribs) No edit summary |
||
Line 9: | Line 9: | ||
=== 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. | |||
<html> | <html> | ||
<center> | <center> |
Revision as of 20:11, 10 July 2017
← |
⌂ Home |
→ |
This pages gives an overview of the GstWebRTCBin element.
Architecture
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.
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.
Send/Receive Audio Only | |
Send/Receive Video Only | |
Send/Receive Audio+Video |
← |
⌂ Home |
→ |