[Gstreamer-bugs] [Bug 123542] New - inactive pads should be able to push a buffer if their peer is active.

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=123542

Changed by thomas at apestaart.org.

--- shadow/123542	Tue Sep 30 04:38:41 2003
+++ shadow/123542.tmp.5520	Tue Sep 30 04:38:41 2003
@@ -0,0 +1,31 @@
+Bug#: 123542
+Product: GStreamer
+Version: 0.6.3
+OS: Linux
+OS Details: RH80
+Status: NEW   
+Resolution: 
+Severity: normal
+Priority: Normal
+Component: gstreamer (core)
+AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
+ReportedBy: thomas at apestaart.org               
+QAContact: gstreamer-maint at bugzilla.gnome.org
+TargetMilestone: HEAD
+URL: 
+Summary: inactive pads should be able to push a buffer if their peer is active.
+
+inactive pads should be able to push a buffer if their peer is active.
+
+Suppose a { filesrc ! vorbisfile ! queue } ! osssink pipeline.
+Whenever something in the input thread needs to change, the pipeline needs
+to pause.  The queue is still being pulled from, but it cannot push the
+data out since queue itself doesn't have active pads.
+
+So one fix is to make sure elements can push if their peer pad is active,
+and that's what this patch does.
+
+In the long run, I think I'd prefer if there is some way the element can
+now a push doesn't work at this time (ie, have pad_push return a gboolean),
+and then the queue can decide to store these unpushed buffers in a glist to
+try again later.