From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000853]: Clicks or pops are produced in Griffin USB iMic PCM output
Date: Fri, 28 Jan 2005 08:28:18 +0100 [thread overview]
Message-ID: <57dfd609ecfc74b81e6ad4c5742e497d@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=853>
======================================================================
Reported By: vtowel
Assigned To: Clemens Ladisch
======================================================================
Project: ALSA - driver
Issue ID: 853
Category: USB - usb-audio
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Gentoo
Kernel Version: 2.6.10-gentoo-r2, with low latency patch
======================================================================
Date Submitted: 01-28-2005 08:28 CET
Last Modified: 01-28-2005 08:28 CET
======================================================================
Summary: Clicks or pops are produced in Griffin USB iMic PCM
output
Description:
I've been spending the longest time trying to figure out why FluidSynth has
been producing these inconsistent clicks while I play MIDI through it. I
finally determined that this behaviour is not specific to FluidSynth, but
to my USB iMic sound card, since the problem does not occur when I
configure FluidSynth to use my internal sound card. I am also able to hear
these clicks through the iMic by just playing an MP3 through them,
although it's not as frequent. It seems that the frequency of the clicks
is dependent on my CPU load; the more I stress my system, the easier it is
to hear these clicks/pops. But it's difficult to determine whether there's
a direct relationship there or not, because this behaviour is so
inconsistent. But I can always cause the clicks to happen within at most a
couple minutes, especially if I'm playing MIDI through FluidSynth.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-28-05 08:28 vtowel New Issue
01-28-05 08:28 vtowel Distribution => Gentoo
01-28-05 08:28 vtowel Kernel Version => 2.6.10-gentoo-r2,
with low latency patch
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-28 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 7:28 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-15 13:19 [ALSA - driver 0000853]: Clicks or pops are produced in Griffin USB iMic PCM output bugtrack
2005-09-15 13:48 bugtrack
2005-09-15 14:14 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57dfd609ecfc74b81e6ad4c5742e497d@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.