[Bug 723850] Elements in rtpbin don't set PROXY_ALLOCATION flag

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=723850
  GStreamer | gst-plugins-good | 1.2.2

--- Comment #5 from Jason Litzinger <jlitzingerdev at gmail.com> 2014-02-16 15:49:50 UTC ---
In my case, I was trying to negotiate a bufferpool for the entire receive
pipeline.  I only had a single source, so setting the flag on those ssrcdemux
and ptdemux worked, however, as you pointed out, it doesn't much help for the
case where multiple synchronization sources exist.

I was trying to follow existing patterns for bufferpool implementations, so the
sink (in my case alsasink) was providing the pool.  This required adding the
proxy flag to the depayloader and forwarding the query in the jitterbuffer as
well (unlike the change above which buffers the query).

I was trying to negotiate a bufferpool within an entire RTP receiver pipeline,
preferably without modifying any elements.  My original thought was to send the
allocation queries myself, until I read through the bufferpool notes in the
design docs.  After that, I overrode the sink's propose_allocation method in my
application, which led me to discover that the query never made it to the
udpsrc, which led to this bug.

As a note, once all the PROXY_ALLOCATION changes I mentioned above were made,
it "worked", however, it was apparent that it wasn't a great overall solution,
but rather one very case-specific to a single SSRC.

On idea is for the rtpbin emit a signal when it receives an allocation query
and rely on the application to forward it to the correct jitterbuffer.

-- 
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.