[Gstreamer-bugs] [Bug 111362] Changed - osssink plugin blocks forever when dsp device is being used

[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=111362

Changed by gjc at inescporto.pt.

--- shadow/111362	Thu Apr 24 18:54:14 2003
+++ shadow/111362.tmp.28617	Fri Apr 25 07:28:44 2003
@@ -39,6 +39,23 @@
 2) If that succeeds (device is available), it closes the device and
 opens it again in blocking mode.
 
 So it should give an error when the device is in use and work in most
 other cases. It's probably the best we can do currently where we need
 the device opened in blocking mode.
+
+------- Additional Comments From gjc at inescporto.pt  2003-04-25 07:28 -------
+  First, I think you can open in non-blocking mode, and if that
+succeeds *change* to blocking mode (I'm almost sure you can do that
+with fcntl).  If you close and reopen, it is possible that another app
+is already trying to open in blocking mode and when osssing closes the
+device, that application completes the open() operation, then ossink
+tries to reopen in blocking mode and blocks.
+
+  However, that doesn't completely explain my problem.  I'm pretty
+sure gstreamer blocks (blocking the whole pipeline, in fact), when
+/dev/dsp is in use.  So there must a bug either in osssink or in my
+device driver (via82cxxx_audio).  However, xmms always reports an
+error when the device is busy, so I'm more inclined to believe it's
+gstreamer's fault.
+
+  Anyway, maybe I'll try to debug this myself...