GNOME Bugzilla – Bug 365429
Ticking sound when playing in 5.1 config
Last modified: 2006-12-09 14:51:17 UTC
I'm currently using .asoundrc > pcm.!default { > type plug > slave.pcm "surround51" > slave.channels 6 > route_policy duplicate > } to enable 5.1 sound on my Card: Intel ICH5 Chip: C-Media Electronics CMI9780 Sound quality is great when using alsaplayer or xine. However, when using Totem-GStreamer, or any other GStreamer player (Rhythmbox). The sound is ticking badly. I've tried several scripts to enable 5.1 sound, but the all had the same outcome. Not using the script, when only playing sound from 2 speakers, I can not notice any ticks. > GStreamer0.10.10-1ubuntu1 > Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
Created attachment 75470 [details] Output from : GST_DEBUG="*:2,alsa*:4" totem 2>alsa.log Output from GST_DEBUG="*:2,alsa*:4" totem 2>alsa.log as requested on mailing list.
Is there any other information I can supply? GStreamer seems to become the standard for audio playback. So this is a major problem for me.
the first think that looks bad is: alsa pcm_hw.c:1246:snd_pcm_hw_open:alsalib error: open /dev/snd/pcmC0D0p failed: Device or resource busy gstalsasink.c:636:gst_alsasink_open:<autoaudiosink0-actual-sink-alsadmix> error: Device 'default' is busy can you do something like: gst-launch filesrc location=my.mp3 ! mad ! alsasink what does 'aplay -l' say? can you experiment with the 'device' option of alsasink?
aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ICH5 [Intel ICH5], device 0: Intel ICH [Intel ICH5] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ICH5 [Intel ICH5], device 4: Intel ICH - IEC958 [Intel ICH5 - IEC958] Subdevices: 1/1 Subdevice #0: subdevice #0
Created attachment 77887 [details] GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:2,alsa*:4" gst-launch-0.10 2>alsa.log filesrc location=2.mp3 ! mad ! alsasink Output from : GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:2,alsa*:4" gst-launch-0.10 2>alsa.log filesrc location=2.mp3 ! mad ! alsasink No ticking sound when using this.
gst-launch case (works) ----------------------- alsasink_parse_spec:<alsasink0> Linear format : depth=32, width=32, sign=1, bigend=0 set_hwparams:<alsasink0> Negotiating to 2 channels @ 44100 Hz (format = S32_LE) set_hwparams:<alsasink0> buffer time 200000, min 22, max 56871 set_hwparams:<alsasink0> period time 10000, min 41, max 56875 set_hwparams:<alsasink0> periods min 0, max 2508 set_hwparams:<alsasink0> buffer size 2508, period size 418 totem (can't open device -> fails) ---------------------------------- alsasink_parse_spec:<autoaudiosink0-actual-sink-alsa> Linear format : depth=16, width=16, sign=1, bigend=0 set_hwparams:<autoaudiosink0-actual-sink-alsa> Negotiating to 2 channels @ 44100 Hz (format = S16_LE) set_hwparams:<autoaudiosink0-actual-sink-alsa> buffer time 200000, min 45, max 113765 set_hwparams:<autoaudiosink0-actual-sink-alsa> period time 10000, min 62, max 113771 set_hwparams:<autoaudiosink0-actual-sink-alsa> periods min 0, max 2509 set_hwparams:<autoaudiosink0-actual-sink-alsa> buffer size 5017, period size 5017 difference is that totel uses 'autoaudiosink' and not the alsasink, as set in gconf.
I'm running Ubuntu feisty now. So I'm on a "clean" system with: Advanced Linux Sound Architecture Driver Version 1.0.13 (Sun Oct 22 08:56:16 2006 UTC). and GStreamer 0.10.11-0ubuntu1 The ticking is less bad, but still present. I'll attach a full log. 0:00:06.317665000 8023 0x83c0ab0 WARN alsa pcm_hw.c:517:snd_pcm_hw_hwsync: alsalib error: SNDRV_PCM_IOCTL_HWSYNC failed: Broken pipe
Created attachment 77985 [details] GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:2,alsa*:4" totem 2>alsa.log Output from GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:2,alsa*:4" totem 2>alsa.log On ubuntu Feisty
This is an Alsa problem. Only weird that it doesn't show when using xine. Can be closed now. thnx for the help.
What I was getting where in fact underruns An "xrun" can be either a (buffer underrun)? or a (buffer overrun)?. In both cases an audio app was either not fast enough to deliver data to the ALSA audio buffer or not fast enough to process data from the ALSA audio buffer. Usually xruns are audible as crackles or pops.