Confirmed users
35
edits
PeerConnection Transport Ramblings: Difference between revisions
no edit summary
(Created page with "<p>This page is place holder for capturing design ideas, architecture and related aspects for the RTCWeb peer-connection transport aspects. </p>") |
No edit summary |
||
| Line 1: | Line 1: | ||
<p>This page is place holder for capturing design ideas, architecture and related aspects for the RTCWeb peer-connection transport aspects. | <p>This page is place holder for capturing design ideas, architecture and related aspects for the RTCWeb peer-connection transport aspects. Most of the specific aspects of this discussion points to WebRTC media-engine. | ||
</p> | </p> | ||
Media Flow Path | |||
This section explains a typical media flow from acquisition till sending the captured media | |||
- Media Acquisition | |||
- Media Capture | |||
- Media Encoding | |||
- Media Transport | |||
On the reception side, we have the following path | |||
- Media Reception | |||
- Media Decoding | |||
MediaEngine Resources that has to be kept in mind: | |||
- Channel | |||
- Encoder | |||
- Decoder | |||
- Physical Devices - Camera, speaker, Mic | |||
Specifically, in the WebRTC media engine, we need | |||
- Ref-counted Interface pointers to different parts of video and voice engine | |||
- VideoEngine Instance - one per process | |||
- VoiceEngine Instance - one per process | |||