[gst-devel] GStreamer Plugin
flavyobr at yahoo.com.br
Thu Mar 24 13:43:53 CET 2005
Gstreamer has an interface for binding plugins that can either
be a source of or destination for media content. I am aware it can
transcode content as well before delivery to a plugin. Hence,
presumably a rtp plugin would be something that can be used either as a
source or sink.
The simplest form of streaming would be to tap a gstreamer endpoint
plugin, and arbitrarly divide it into some fixed size packets. That
would not be ideal, but it could be done.
Presumably, gstreamer can in some manner identify the encoding type of
the data supported by the endpoint, or the endpoint can in some manner
notify gstreamer about the encodings it can accept?
With that, it could be possible to make a rtp based plugin that is aware
of certain specific media types and their expected rtp properties.
Processing mpeg, for example, from gstreamer hopefully can be done
simply by requesting the n bytes of data from gstreamer that are the
mpeg audio header of the next fragment, looking at that, requesting the
next n bytes of data, and then shipping that out as a single packet
through rtp. Does this kind of approach actually match the way gstreamer
communicates with plugins?
More information about the gstreamer-devel