Mediastreamer2 library - a modular sound and video processing and streaming
Mediastreamer2 is a powerful engine to make audio and video streams.
Filter: A filter is a Mediastreamer2 component that process data. A filter has 0 or several INPUT pins and 0 or several OUTPUT pins. Here is a list of possible use of filters:
capture audio or video data.
play audio or display video data.
send or receive RTP data.
encode or decode audio or video data.
mix audio/video data.
Graph: A graph is a manager of filters connected together. It will transfer data from OUTPUT pins to INPUT pins and will be responsible for running filters.
Mediastreamer2 can be used for a lot of different purpose. The primary use is to manage RTP audio and video session. You will need to use the API to build filters, link them together in a graph. Then the ticker API will help you to start and stop the graph.
Basic graph sample:
AUDIO CAPTURE --> ENCODE --> RTP
FILTER --> FILTER --> FILTER
The above graph is composed of three filters. The first one has no input: tt captures audio data directly from the drivers and provide it to the OUTPUT pin. This data is sent to the INPUT pin of the encoder which of course encode the data and send it to its OUTPUT pin. This pin is connected to the INPUT pin of a filter capable to build and send RTP packets.
The modular design helps you to encode in many different format just by replacing the "ENCODE FILTER" with another one. mediastreamer2 contains internal support for g711u, g711a, speex and gsm. You can add new encoding format by implementing new filters which can then be dynamically loaded.
Mediastreamer2 already provides a large set of filters. Here is a complete list of built-in filters.
All supported platforms:
RTP receiver
RTP sender
Audio Filters:
audio capture
audio playback
several audio encoder/decoder: PCMU, PCMA, speex, gsm
wav file reader.
wav file recorder.
resampler.
conference bridge.
volume analyser.
acoustic echo canceller.
dtmf generation filter.
Video Filters:
video capture
video display
several audio encoder/decoder: H263-1998, MP4V-ES, theora
image resizer.
format converter. (RBG24, I420...)
Plugin Filters:
iLBC decoder/encoder.
Refer to : http://download.savannah.gnu.org/releases-noredirect/linphone/mediastreamer/doc/group__mediastreamer2.html
Mediastreamer2 - the multimedia streaming engine
Mediastreamer2 is a powerful and light weighted streaming engine specialized for voice/video telephony applications.
It is the library that is responsible for all the receiving and sending of multimedia streams in linphone, including voice/video capture, encoding and decoding, and rendering.
Features
★ Read/Write from to an alsa device, an oss device, a windows waveapi device
★ Send and receive RTP packets
★ Encode and decode the following formats: speex, G711, GSM, H263, theora, iLBC, MPEG4, and H264.
★ Read and write from/to a wav file
★ Dual tones generation
★ Echo cancelation, using the extraordinary echo canceller algorithm from the speex library
★ Audio conferencing
★ Audio parametric equalizer using a FIR filter
★ Volume control, automatic gain control
★ Works on linux, windows XP
Mediastreamer2 can be extended with dynamic plugins, currently a H264 and an ILBC codec plugins are available.
Each processing entity is contained within a MSFilter object. MSFilter(s) have inputs and/or outputs that can be used to connect from and to other MSFilters.
A trivial example to understand:
☆ MSRtpRecv is a MSFilter that receives RTP packets from the network, unpacketize them and post them on its only output.
☆ MSSpeexDec is a MSFilter that takes everything on its input assuming these are speex encoded packets, and decodes them and put the result on its output.
☆ MSFileRec is a MSFilter that takes everything on its input and write it to wav file (assuming the input is 16bit linear pcm).
MSFilters can be connected together to become filter chain. If we assemble the three above examples, we obtain a processing chain that receives RTP packet, decode them and write the uncompressed result into a wav file.
The execution of the media processing work is scheduled by a MSTicker object, a thread that wakes up every 10 ms to process data in all the MSFilter chains it manages. Several MSTicker can be used simultaneously, for example one for audio filters, one for video filters, or one on each processor of the machine where it runs.
If your intent is simply to create audio and video streams, a simple API is defined in audiostream.h and videostream.h to create audio and video stream.
It can be as simple as:
AudioStream *as=audio_stream_start(.../*list of parameters*/);sleep(10);
audio_stream_stop(as);
If your intent is to add new functionalities to mediastreamer2, you'll be glad to know that implementing a mediastreamer2 filter is very straightforward: no complex declarations, inheritance or such like this.
As an example, have a look at this: it is the 'MSVolume' MSFilter, whose goal is to measure and control loudness of an audio stream.
Thanks to this lightweighted framework, developers can concentrate on what matters: the implementation of the algorithm !
Mediastreamer2 is also suitable for embedded systems
★ Mediastreamer2 is light. For example on linux/x86 the full-featured shared library takes around 800ko unstripped and compiled with -g (debug). Data messages that carries the media data within mediastreamer2 chains are optimized using the famous sys-V mblk_t structure. This is to avoid copies as long it is possible and allow low cost fragmentation/re-assemble operations that are very common especially when processing video streams.
★ Mediastreamer2 is written in C.
★ Mediastreamer2 compiles on arm with gcc.
★ Mediastreamer2 has only oRTP and libc as minimal dependencies. Others (ffmpeg, speex, alsa...) can be added optionnaly if you need all features.
Thanks to its plugin architecture, mediastreamer2 can be extended to interface with hardware codecs, for example video codecs dsp.
Refer to : http://www.linphone.org/index.php/eng/code_review/mediastreamer2