Difference between revisions of "GstWebRTC - GstWebRTCBin Features"

From RidgeRun Developer Connection
Jump to: navigation, search
m
 
(29 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{GstWebRTC Page|
+
{{GstWebRTC/Head|previous=GstWebRTCBin Properties|next=Data Channel|metakeywords=Gstreamer WebRTC Basics,Plugin Overview,WebRTC Basics,Gstreamer WebRTC Plugin Overview,GstRrWebRTCBin element,GstRrWebRTCBin,signaling}}
[[GstWebRTC - GstWebRTCBin Properties | GstRrWebRTCBin Properties]]|
 
[[GstWebRTC - Evaluating GstWebRTC|Evaluating GstRrWebRTC]]|
 
  
 +
== Features ==
 +
;Data Channel
 +
:Datachannel is a network channel which can be used for bidirectional peer-to-peer transfers of arbitrary data. For more information visit our [[GstWebRTC_-_Data_Channel|GstRrWebRTC Data Channel page]].
 +
;ICE Trickle
 +
:Ice-Trickle speeds up the initial connection process by exchanging individual ICE candidates.
 +
;Media Send+Receive
 +
:GstRrWebRTC is able to send and/or receive media or data of a pair at the same time.
 +
;RTCP Muxing
 +
:GstRrWebRtc is able to enable that RTP and RTCP share the same socket and connection
 +
;Codec Agnostic
 +
:GstRrWebRtc is not forced to use only some kinds of encoders or decoders, it could use any kind of codec while the messages can be understood
 +
;Extensible Signaler Support
 +
:GstRrWebRTC has 4 different signalers and also allows you to create a different one and use it with GstRrWebRTC. For more information visit our [[GstWebRTC_- Signaler |GstRrWebRTC Signaler page]].
 +
;Simultaneous Media and Data Support
 +
:With GstWebRc you can send and/or recieve Audio, Video, Data, or any combination of them.
 +
;Candidates Filtering
 +
:This support allows you to remove not needed ICE candidates to speed connection process.
  
{| class="wikitable" style="margin-right: auto; margin-left: auto; border: none;"
+
{{GstWebRTC/Foot|previous=GstWebRTCBin Properties|next=Data Channel}}
|-
 
! style="background: black; color: white;" | Features!! style="background: black; color: white;" | i.MX6 Quad / i.MX6 Dual !! style="background: black; color: white;" | i.MX7 Dual !! style="background: black; color: white;" | i.MX8M Dual / i.MX8M QuadLite / i.MX8M Quad
 
|-
 
! scope="row" | CPU
 
| style="text-align: left" | <li>(i.MX 6Quad) 4 x Cortex-A9</li><li>(i.MX 6Dual) 2 x Cortex-A9<li> || style="text-align: left" | <li>Arm Cortex-A53 MPCore platform</li><li>Arm Cortex-M4 core platform</li> || style="text-align: left" | <li>2 x Cortex-A7</li><li>Cortex-M4</li>
 
|-
 
! scope="row" | Maximum CPU Frequency
 
| style="text-align: left" | <li>1.2 GHz</li> || style="text-align: left" | <li>(A7) 1.2 GHz</li><li>(M4) 200 MHz</li> || style="text-align: left" | <li>1.5 GHz</li>
 
|-
 
! scope="row" | I-Cache/D-Cache
 
| style="text-align: left" | 32 KB/32 KB L1, 1 MB L2 || style="text-align: left" | <li>(A7) 32 KB/32 KB L1, 512 KB L2</li><li>(M4) 16 KB/16 KB L1</li> || style="text-align: left" | <ul><li>'''Arm Cortex-A53:'''<br>'''>''' <U>Quad symmetric Cortex-A53 processors:</U><br>- 32 KB L1 Instruction Cache<br>- 32 KB L1 Data Cache<br>- Support L1 cache RAMs protection with parity/ECC<br>'''>''' <U>Support of 64-bit Armv8-A architecture:</U><br>- 1 MB unified L2 cache<br>- Support L2 cache RAMs protection with ECC<br>- Frequency of 1.5 GHz</ul></li><br><ul><li>'''Arm Cortex-M4:'''<br>- 16 KB L1 Instruction Cache<br>- 16 KB L1 Data Cache<br>- 256 KB tightly coupled memory (TCM)</ul></li><br>
 
|-
 
! scope="row" | External Memory Interface
 
| style="text-align: left" | 2 x 32 LP-DDR2, 1-ch. x 64 DDR3/DDR3L || style="text-align: left" | 32/16-bit LP-DDR2, DDR3, DDR3L, and LPDDR3 up to 533 MHz, rawNAND, QuadSPI NOR || style="text-align: left" | <li>32/16-bit DRAM interface: LPDDR4-3200, DDR4-2400, DDR3L-1600</li><li>8-bit NAND-Flash</li><li>eMMC 5.0 Flash</li><li>SPI NOR Flash</li><li>QuadSPI Flash with support for XIP</li>
 
|-
 
! scope="row" | Display Interface
 
| style="text-align: left" | HDMI + PHY 2 x parallel, 2 x LVDS, MIPI DSI || style="text-align: left" | 24-bit parallel RGB, MIPI DSI, EPDC || style="text-align: left" | <ul><li>'''HDMI Display Interface:'''<br>- HDMI 2.0a (1 display): up to 4096x2160 @ 60 Hz, support HDCP 2.2 and HDCP 1.4<br>- 20+ Audio interfaces 32-bit @ 384 kHz fs with Time Division Multiplexing (TDM) support<br>- S/PDIF input and output<br>- Audio Return Channel (ARC) on HDMI<br>- Upscale HD graphics to 4K for display<br>- Downscale 4K video to HD for display<br>- Display Port<br>- Embedded Display Port</ul></li><ul><li>'''MIPI-DSI Display Interface:'''<br>- MIPI-DSI 4 channels supporting one display, up to 1920x1080 @ 60 Hz<br>- LCDIF display controller<br>- Output can be LCDIF output or DC display controller output</ul></li>
 
|-
 
! scope="row" | Hardware Video Acceleration
 
| style="text-align: left" | HD (1080 + 720)p30 video decode<br>HD 1080p30 video encode || style="text-align: left" | Software Only || style="text-align: left" | <ul><li>Video Processing Unit:<br>- 4Kp60 HEVC/H.265 main, and main 10 decoder<br>- 4Kp60 VP9 decoder<br>- 4Kp30 AVC/H.264 decoder<br>- 1080p60 MPEG-2, MPEG-4p2, VC-1, VP8, RV9, AVS, MJPEG, H.263 decoder</ul></li><li>Software Only encoding support</li>
 
|-
 
! scope="row" | Hardware 2D/3D Graphics Acceleration
 
| style="text-align: left" | <li>OpenGL ES 1.1/2.0/3.0</li><li>OpenCL 1.1 EP</li><li>OpenVG 1.1, 2DBLT, 4 shaders</li> || style="text-align: left" | No, but has a PxP (PiXel processing pipeline for imagine resize, rotation, overlay and color space conversion) || style="text-align: left" | <li>OpenGL/ES 3.1</li><li>Open CL 1.2</li><li>Vulkan, 4 shaders
 
|-
 
|}
 
 
 
 
 
|keywords=Gstreamer WebRTC Basics,Plugin Overview,WebRTC Basics,Gstreamer WebRTC Plugin Overview,GstRrWebRTCBin element,GstRrWebRTCBin}}
 

Latest revision as of 10:15, 9 March 2023



Previous: GstWebRTCBin Properties Index Next: Data Channel




Features

Data Channel
Datachannel is a network channel which can be used for bidirectional peer-to-peer transfers of arbitrary data. For more information visit our GstRrWebRTC Data Channel page.
ICE Trickle
Ice-Trickle speeds up the initial connection process by exchanging individual ICE candidates.
Media Send+Receive
GstRrWebRTC is able to send and/or receive media or data of a pair at the same time.
RTCP Muxing
GstRrWebRtc is able to enable that RTP and RTCP share the same socket and connection
Codec Agnostic
GstRrWebRtc is not forced to use only some kinds of encoders or decoders, it could use any kind of codec while the messages can be understood
Extensible Signaler Support
GstRrWebRTC has 4 different signalers and also allows you to create a different one and use it with GstRrWebRTC. For more information visit our GstRrWebRTC Signaler page.
Simultaneous Media and Data Support
With GstWebRc you can send and/or recieve Audio, Video, Data, or any combination of them.
Candidates Filtering
This support allows you to remove not needed ICE candidates to speed connection process.


Previous: GstWebRTCBin Properties Index Next: Data Channel