[gst-devel] GStreamer Plugin
flavyobr at yahoo.com.br
Mon Mar 28 07:01:09 CEST 2005
In gstreamer, a "chunk" of mpeg audio might be the same as a "mpeg
frame" (header + data section)? If so, then it would seem the chunks
could be passed accross with rtp directly in individual packets.
Exchanging extended type information could be done in special packets,
or through a secondary protocol. That would also look much more like
"gstreamer" over rtp than "mpeg" or a specific encoded format over rtp.
On Thu, 2005-03-24 at 23:24 +0100, Ronald S. Bultje wrote:
> Hi Flavio,
> On Thu, 2005-03-24 at 18:40 -0300, Flavio Oliveira wrote:
> > 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?
> Sure, look at bytestream. Although it's non-ideal, it's better to accept
> full frames of compressed audio, e.g. audio/mpeg,framed=true.
More information about the gstreamer-devel