No subject

is done in gdppay, is dangerous for multifdsink since multifdsink only seems to
care about the streamheader and whether it changes, and the code that handles
the streamheader is not modified by the patch. The patch only removes the
duplicate sending (as buffers sent along the pipeline) of some buffers (the
ones encoding newsegments/tags/caps if they didn't change).
So I believe that multifdsink would only have to send the buffers in its
streamheader for a new connection, later if upstream changes segment, gdppay
with that patch would both update the streamheader and send a buffer with the
gdp-encoded newsegment event, as it does without the patch.
@thomas if you still think that multifdsink would need some adaptation, then
there is something I did not understand, and I would like to have it explained
to me :)

Also, the method employed in the patch in gdpdepay has plenty of drawbacks
(listed in my previous comment), and I can't really think of another way to do
that.
@thomas if you have a set-up that makes it easy to test various segment cases
with flumotion, it would be cool to try these patches on it.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.