alsasink produces stuttering output [breezy]

Bug #21638 reported by Holger Bauer
12
Affects Status Importance Assigned to Milestone
gst-plugins0.8 (Ubuntu)
Invalid
Medium
Martin Pitt

Bug Description

Running gstreamer using the alsasink produces a stuttering or distorted output.
I had no problems with alsasink before I upgraded from hoary.
There is no soundserver running. Ossink works like a charm. Playing sound using
aplay also works. gstreamer-properties produces stutterin output with alsasink
and autosink.

I was playing aorund with gst-launch too.
works: gst-launch-0.8 filesrc location="Some.ogg" ! oggdemux ! vorbisdec !
audioconvert ! ossink
works: gst-launch-0.8 filesrc location="Some.mp3" ! mad ! osssink
does not work: gst-launch-0.8 filesrc location="Some.ogg" ! oggdemux ! vorbisdec
! audioconvert ! alsasink
does not worK: gst-launch-0.8 filesrc location="Some.mp3" ! mad ! alsasink

I have no old /etc/asound.conf or ~/.asoundrc on my system.

Installed are alsa-base 1.0.9b-3ubuntu1, gstreamer0.8-alsa 0.8.11-0ubuntu3 and
linux-image-2.6.12-8-k7.

Revision history for this message
Holger Bauer (umarmung-planet) wrote :

Created an attachment (id=3790)
Output of lspci -v

Revision history for this message
Matt Zimmerman (mdz) wrote :

Can you try booting the old kernel from Hoary, and see if that changes things?

Revision history for this message
Holger Bauer (umarmung-planet) wrote :

I booted my old kernel (2.6.10-5-k7) and still get the same symptoms.

However I noticed some error messages on bootup. I get those lines only on first
boot, after I switched kernels. When I boot a 2nd time the same kernel again, I
don't see that.
This repeated when I switched back from hoary to breezy kernel.

/etc/init.d/alsa-utils:
Warning:'alsactl restore' failed with the error message 'alsactl:
set_control:894:warning: name mismatch (Off_hook Switch/DAC Volume) for control #23
alsactl:896:warning: index mismatch(0/0) for control #23
alsactl:944:bad control.23.value type'

Revision history for this message
Matt Zimmerman (mdz) wrote :

Does it help if you adjust the mixer levels? Those messages indicate that (due
to the kernel change) your mixer settings couldn't be fully restored

Revision history for this message
Holger Bauer (umarmung-planet) wrote :

No. Adjusting mixer levels doesn't help.

Revision history for this message
Holger Bauer (umarmung-planet) wrote :

Finally I found a solution after discovering this debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323447

I have to run alsasink with period-size=1024 and buffer-size=16384
Setting only period-size like suggested in the debian bugreport is not enough.

Revision history for this message
Martin Pitt (pitti) wrote :

This bug has been marked as a duplicate of bug 17770.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.