[gstreamer-bugs] [Bug 578118] New: [multifdsink] add option to not resend the streamheader when it changes in the caps
bugzilla-daemon at bugzilla.gnome.org
Mon Apr 6 03:06:40 PDT 2009
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
GStreamer | gst-plugins-base | Ver: git
Summary: [multifdsink] add option to not resend the streamheader
when it changes in the caps
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: j.urbanski at students.mimuw.edu.pl
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
The attached patch adds a new property in multifdsink, resend-streamheader.
If this property is false, the multifdsink will not send the streamheader if
there's already one set for a particular client.
There are some formats in which every stream needs to start with a certain
blob, but you can't inject this blob at leisure. If the producer wants to
change the blob in question and sets in as the streamheader on the outgoing
buffers' caps, new clients of multifdsink will get the new streamheader, but
old clients will break, because they'll see the blob in the middle of the
The property is true by default, so existing code will not see any difference.
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=578118.
More information about the Gstreamer-bugs