[gst-devel] addition of a buffer flag

David Schleef ds at schleef.org
Wed May 12 14:07:04 CEST 2004

On Wed, May 12, 2004 at 07:17:02PM +0200, Thomas Vander Stichele wrote:
> Seriously, this is not what caps are supposed to be used for.

Actually, it is.  The caps rewrite had this specifically as one
of its goals.

> > (e.g. caps: video/x-theora,width=(int)384,height=(int)288,
> > codec_data=(buffer)fe56ba3c810c).
> Ok, so I can read and interpret those caps, *except* for the
> codec_data.  What does it tell me ?

It tells you that we'd love to provide that as human-readable data,
but in the interest of expediency in 0.8, we don't.

> > Of course,I'm open to suggestions from others if they see different
> > (better) solutions to the problem drawn above.
> Tell me how the buffer flag approach fails for you.

  ... ! oggdemux ! identity ! blah ...

Play for 10 seconds, then disconnect identity and blah, and connect
identity to vorbisdec.  How does vorbisdec get the header packets?

We've always known that out-of-band data is required to properly
parse a format.  For some streams, it's called "height" and "width".
For others, it's a large blob of bits that we call "codec_data".

Personally, I feel that the large the blob of bits, the less you
can call it a "stream", but apparently codec writers disagree.


More information about the gstreamer-devel mailing list