[Gstreamer-bugs] [Bug 131720] New - Strange queue behavior when in gconf key (spider / nego issues?)

bugzilla-daemon at widget.gnome.org bugzilla-daemon at widget.gnome.org
Fri Jan 16 11:34:52 PST 2004


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=131720

Changed by mnews2 at wp.pl.

--- shadow/131720	Fri Jan 16 14:34:52 2004
+++ shadow/131720.tmp.8255	Fri Jan 16 14:34:52 2004
@@ -0,0 +1,27 @@
+Bug#: 131720
+Product: GStreamer
+Version: HEAD CVS
+OS: Linux
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: normal
+Priority: Normal
+Component: gstreamer (core)
+AssignedTo: gstreamer-maint at bugzilla.gnome.org                            
+ReportedBy: mnews2 at wp.pl               
+QAContact: gstreamer-maint at bugzilla.gnome.org
+TargetMilestone: HEAD
+URL: 
+Summary: Strange queue behavior when in gconf key (spider / nego issues?)
+
+Putting { queue max-size-time=1000000000 ! osssink } as default audio sink
+in gconf produces no output in apps using it (ok, I tested in RB only). 
+Just { queue ! osssink } doesn't work either. Changing it to max-level=100
+makes it work however. Also, using audio/x-raw-int ! identity ! { queue
+max-size-time=1000000000 ! osssink } (for Benjamin it worked w/o
+audio/x-raw-int) makes it work too.
+
+Possible cause:
+Nego issues, probably spider. What's strange is that using 0.6 syntax makes
+it work w/o all that filtered caps babbling.




More information about the Gstreamer-bugs mailing list