GNOME Bugzilla – Bug 342085
[alsasink] doesn't set buffer-time correctly
Last modified: 2006-06-16 11:05:59 UTC
Hi, with gstreamer 0.10.6 / gst-plugins-base 0.10.7 the alsasink doesn't always get the buffer-time correct. For example with an Aureal Vortex 2 the following happens: terminates immediately: GST_DEBUG=3 GST_DEBUG_NO_COLOR=1 gst-launch-0.10 filesrc location=smash.mp3 ! mad ! alsasink &> gst1.log http://librarian.launchpad.net/2686912/gst1.log plays but is distorted: GST_DEBUG=3 GST_DEBUG_NO_COLOR=1 gst-launch-0.10 filesrc location=smash.mp3 ! mad ! alsasink buffer-time=200 &> gst2.log http://librarian.launchpad.net/2686914/gst2.log plays but has some audible clicks: GST_DEBUG=3 GST_DEBUG_NO_COLOR=1 gst-launch-0.10 filesrc location=smash.mp3 ! mad ! alsasink buffer-time=1000 &> gst3.log http://librarian.launchpad.net/2686921/gst3.log Setting the buffer-time to 900 or 1100 makes it exit immediately too. exits immediately: GST_DEBUG=3 GST_DEBUG_NO_COLOR=1 gst-launch-0.10 audiotestsrc ! audioconvert ! alsasink &> gst4.log http://librarian.launchpad.net/2686934/gst4.log Bye Ubuntu Bug: https://launchpad.net/distros/ubuntu/+source/gst-plugins-base0.10/+bug/44943
Following patch should fix this, please reopen if it does not. * ext/alsa/gstalsasink.c: (set_hwparams): If we fail to set the buffer_time and period_time alsa parameters, post a warning and leave alsa select a default instead of failing. Fixes #342085