All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Rusty Phillips <rustyp@freeshell.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Crackling sounds with Omnistudio USB
Date: Fri, 21 Jan 2005 17:44:40 -0500	[thread overview]
Message-ID: <1106347480.3232.67.camel@krustophenia.net> (raw)
In-Reply-To: <1106345994.17958.31.camel@localhost.localdomain>

On Fri, 2005-01-21 at 17:19 -0500, Rusty Phillips wrote:
> I've done a lot to narrow this down, and I know I'm getting crackles and
> pops on my Omnistudio USB from within the computer (it has zero latency
> monitoring, so I can hear what happens on the device).
> 
> This only happens when recording - not playback, and I know it happens
> on both my Intel 440BX motherboard (which doesn't have any problems
> reported - not sure of the actual model) and my Abit KG7, which has a
> Via 686B southbridge, which is reported to show such problems.
> 
> The Abit board is dual-boot, and I found a Windows USB patch from VIA
> called the "USB filter patch."  This got rid of the pops and crackles
> when recording in Windows.  

Please give some more information about what the USB filter patch does.
Got a link?

What kernel are you using?

Lee



-------------------------------------------------------
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

  reply	other threads:[~2005-01-21 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 22:19 Crackling sounds with Omnistudio USB Rusty Phillips
2005-01-21 22:44 ` Lee Revell [this message]
2005-01-22  1:03   ` Rusty Phillips
2005-01-27 22:23   ` Omnistudio USB further problem report Rusty Phillips
2005-01-28 18:23     ` Clemens Ladisch
2005-01-29  3:14       ` Rusty Phillips

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=1106347480.3232.67.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rustyp@freeshell.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.