mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-22 09:41:07 +00:00
Code Issues 1 Projects Releases Wiki Activity

some streamheader updates

Browse source 
Original commit message from CVS:
some streamheader updates
This commit is contained in:
Thomas Vander Stichele 2006-05-14 21:16:50 +00:00
parent d619a982a8
commit c3de49400d
1 changed files with 9 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/random/streamheader
View file

@ -39,11 +39,18 @@ Rules for sending streamheaders:
- when all streamheader buffers are collected in the element, pad caps should
be set, including this streamheader
- streamheader buffers should be sent consecutively, and before any of the
data (non-IN_CAPS) buffers they apply to.
data (non-IN_CAPS) buffers they apply to. If necessary, the element
should internally queue non-IN_CAPS buffers until the streamheaders
are completely assembled.
- when new streamheader buffers need to be pushed out, this process is
repeated. Receiving a new IN_CAPS buffer after a non-IN_CAPS buffer
signifies resetting streamheader, as does the new set_caps with different
streamheader right before.
streamheader right before. (FIXME: it's probably better to explicitly
have an event/buffer that clears streamheaders; consider the case of
an element like GDP that has created streamheader from the first newsegment
and the first caps, and then receives a new tag event that it also wants
to put on the streamheader - it should be able to invalidate the previous
ones)
Elements that can send streamheader caps:
- vorbisenc