[gstreamer-bugs] [Bug 171754] New: sound recorder won't play more than once with CA0106 driver for Audigy LS, reports GStreamer error

bugzilla-daemon at bugzilla.gnome.org bugzilla-daemon at bugzilla.gnome.org
Sat Mar 26 16:22:29 PST 2005


Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=171754
 GStreamer | don't know | Ver: 0.8.8

           Summary: sound recorder won't play more than once with CA0106
                    driver for Audigy LS, reports GStreamer error
           Product: GStreamer
           Version: 0.8.8
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: don't know
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: damon at larrymite.com.au
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: all-bugs at bugzilla.gnome.org


Please describe the problem:
I've just installed new alsa-drivers for the recently supported Creative Audigy
LS.  Using Gnome-sound-recorder I can open a sound file, play it once, then if I
press play again a dialog appears with:
Internal GStreamer error: pad problem.  File a bug.

Running 
gnome-sound-recorder --gst-debug-level=1
gives:


Steps to reproduce:
1. run: gnome-sound-recorder --gst-debug-level=1
2. open any wav file
3. play it once
4. press play again


Actual results:
Error dialog appears, saying
Internal GStreamer error: pad problem.  File a bug.

On the console, the debug output says:
ERROR (0x8059ed0 - 308857:16:21.058420000)        GST_PADS( 7818)
gstpad.c(3280):gst_pad_pull:<src_0> pull on pad src_0:sink but it was unlinked

Expected results:
Sound plays again

Does this happen every time?
Yes, as user and root

Other information:
I have recently installed the new alsa driver for the Creative Audigy LS, and
I'm pretty sure that's where the problem is.

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.




More information about the Gstreamer-bugs mailing list