Confirmed users
321
edits
TPEPlatform/WebRTC B2G: Difference between revisions
Jump to navigation
Jump to search
→Threads in WebRTC
| Line 125: | Line 125: | ||
#(MediaStreamGraph) Media stream graph run thread: audio/video coding.(MediaStreamGraphImpl::RunThread in MediaStreamGraph.cpp) | #(MediaStreamGraph) Media stream graph run thread: audio/video coding.(MediaStreamGraphImpl::RunThread in MediaStreamGraph.cpp) | ||
#(Network) Socket transport service: send/receive packets. (Entry point of user space callback function??) | #(Network) Socket transport service: send/receive packets. (Entry point of user space callback function??) | ||
#(Capture) Camera capture thread | #(Capture) Camera capture thread: On FFOS, video frames are callback through MediaEngineWebRTCVideoSource::OnNewFrame and the source is camera api. For other platforms, the images are from MediaEngineWebRTCVideoSource::DeliverFrame, the callback interface of GIPS, and the source is implemented in GIPS. Then MSG thread keeps pulling the latest frames by MediaEngineWebRTCVideoSource::NotifyPull. | ||
#(Capture) Audio capture thread: recieve audio frame from microphone. ( | #(Capture) Audio capture thread: recieve audio frame from microphone. All audio streams are input through MediaEngineWebRTCAudioSource::Process. In "Process" function, the audio is saving to media track. The mechanism may change since it has clock drift problem(bug 884365). | ||
#(Process) Process thread (worker threads in GIPS): doing many other tasks. Process thread has a task queue for client to inject tasks into. | #(Process) Process thread (worker threads in GIPS): doing many other tasks. Process thread has a task queue for client to inject tasks into. | ||