Introduction to webrtc concept -- an article on understanding source, track, sink and mediastream

A term is used to explain

source： Media streaming providers

track： The media stream held by the application , Can be used to play

sink： Media stream recipients

source Is the production of media resources ,sink Responsible for consumption

source —( Provide media streaming )—> track —( Output media stream )—> sink

For streaming media systems , The device that generates data is called Source, The device that receives data is called Sink.

If one source Can belong to more than one track, So you can make different sink Bind the same source, It will lead to inability to cope with multiple states

track Some status information and processing are saved in , This is the same as source decoupling

webrtc In the abstract VideoSourceInterface and VideoSinkInterface respectively Source and Sink

source After the camera captures the image , Save the video , Become a video source , Coding and local rendering require consuming images for processing , Similar to the concept of production and consumption
For consumers , That is to say sink Come on , If I want to add a consumer , I inherit sink Interface , Plug it into the instance where the video source is saved , Let the instance continue to fill me with data for my consumption （onFrame）, therefore sink The interface definition of is easy to understand

The header file ：media_stream_interface.h