Hide Forgot
Description of problem: playing back music using "Amarok" and the command line "aplay" skips music on this USB audio device (Alesis IO|2). Internal Intel HDA audio works, however the sound quality is bad. The IO|2 device works fine in Mac OS X on the same computer. Playback sometimes skips for many seconds even a minute, when the sound is completely mute and it comes back with a loud cracking sound. Since it is supposed to be a professional device I cannot record any music with it until this problem persists. Could you also point me to some instructions that would describe how to debug such problems? Version-Release number of selected component (if applicable): I've thoroughly tested and got annoyed by it on F14 and many previous versions. How reproducible: Every time an application plays sound. Steps to Reproduce: 1. Find music file 2. open it with amarok or play it with 'aplay' 3. Notice the skips and cracks Actual results: The sound sips and cracks Expected results: The sound doesn't disappear and plays back smoothly. Additional info:
For lack if any other data, best guess is that it's a driver issue (esp since it's reproducible with a simple aplay). not sure the best place to triage this, alsa-lib vs kernel ?
I did some more digging and found this in /var/log/messages Jan 18 01:22:56 tiger kernel: [ 217.313486] ALSA sound/usb/clock.c:242: 2:1:1: cannot get freq at ep 0x1 also these Jan 18 01:23:33 tiger pulseaudio[3491]: ratelimit.c: 3310 events suppressed Jan 18 01:23:33 tiger pulseaudio[3491]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Jan 18 01:23:33 tiger pulseaudio[3491]: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA developers. Jan 18 01:23:33 tiger pulseaudio[3491]: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. Jan 18 01:23:33 tiger pulseaudio[3491]: client.c: Freed 6 "libphonon" Jan 18 01:23:33 tiger pulseaudio[3491]: protocol-native.c: Connection died. Jan 18 01:23:33 tiger pulseaudio[3491]: client.c: Created 16 "Native client (UNIX socket client)" Jan 18 01:23:34 tiger pulseaudio[3491]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 Jan 18 01:23:34 tiger pulseaudio[3491]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 Jan 18 01:23:48 tiger pulseaudio[3491]: client.c: Created 17 "Native client (UNIX socket client)" Jan 18 01:23:48 tiger pulseaudio[3491]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 Jan 18 01:23:48 tiger pulseaudio[3491]: client.c: Freed 17 "ALSA plug-in [kded4]" Jan 18 01:23:48 tiger pulseaudio[3491]: protocol-native.c: Connection died. Jan 18 01:23:48 tiger pulseaudio[3491]: client.c: Created 18 "Native client (UNIX socket client)" Jan 18 01:23:48 tiger pulseaudio[3491]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 Jan 18 01:23:48 tiger pulseaudio[3491]: client.c: Freed 18 "ALSA plug-in [kded4]" Jan 18 01:23:48 tiger pulseaudio[3491]: protocol-native.c: Connection died. Jan 18 01:23:48 tiger pulseaudio[3491]: client.c: Created 19 "Native client (UNIX socket client)" Jan 18 01:23:48 tiger pulseaudio[3491]: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1 I am more concerned about the 'Please report this issue to the ALSA developers.' part. Should I file it in the ALSA bugzilla?
> Should I file it in the ALSA bugzilla? If I were you, yes.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping