20,290
edits
GStreamer WebRTC Wrapper/Introduction/GstWebRTCWrapper Basics: Difference between revisions
GStreamer WebRTC Wrapper/Introduction/GstWebRTCWrapper Basics (view source)
Revision as of 19:51, 19 May 2021
, 19 May 2021no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 14: | Line 14: | ||
== Why GstWebRTCWrapperbin? == | == Why GstWebRTCWrapperbin? == | ||
Other WebRTC solutions will automatically detect the video and audio sources, as well as the decoders/encoders and other elements to be used to build the pipeline. This may be convenient for many applications, but result limiting for several other use cases. To mention some of them: | Other WebRTC solutions will automatically detect the video and audio sources, as well as the decoders/encoders and other elements to be used to build the pipeline. This may be convenient for many applications, but the result limiting for several other use cases. To mention some of them: | ||
* Extend existing pipeline to support WebRTC streaming. | * Extend existing pipeline to support WebRTC streaming. | ||
* Use non-standard pipeline configurations. | * Use non-standard pipeline configurations. | ||
| Line 22: | Line 22: | ||
* Quick gst-launch prototyping. | * Quick gst-launch prototyping. | ||
GstWebRTCWrapperbin was developed based on | GstWebRTCWrapperbin was developed based on these criteria. As such, the plug-in is ideal for: | ||
* Embedded platforms. | * Embedded platforms. | ||
* Existing media servers/applications. | * Existing media servers/applications. | ||