Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony <avan@uwm.edu>
To: Anthony <avan@uwm.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 noise
Date: Thu, 5 Feb 2004 00:50:09 -0600	[thread overview]
Message-ID: <20040205065009.GA30274@ice_nine.wi.rr.com> (raw)
In-Reply-To: <20040131195752.GA4224@ice_nine.wi.rr.com>

* Anthony <avan@uwm.edu> [Jan 31 04 14:43]:
> * Jaroslav Kysela <perex@suse.cz> [Jan 31 04 13:16]:
> > It looks like that something is wrong with DACs.                            
> > Does the noise occur on all outputs?                                         
> >                                                                              
> >                                       Jaroslav                               

FWIW, the crackling noise was due to my NIC. I hadn't
noticed it before since my bandwidth was recently 
increased by my ISP. I guess its a good thing in some 
way.

I'm still getting some bizarre behaviour when running
an ardour session recorded at 44.1Khz. Occasionally
I get a pop and envy24control shows the output levels
constantly maxed out. This doesn't make sense to me
since jack should of already opened the device and is
writing silence. I vaugely remember this being a problem
when I first got the card that eventually disappeared.
That, or I haven't been doing much of anything at 44.1
to notice.

--ant


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

      reply	other threads:[~2004-02-05  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  6:09 ice1712 noise Anthony
2004-01-31 10:26 ` Jaroslav Kysela
2004-01-31 19:57   ` Anthony
2004-02-05  6:50     ` Anthony [this message]

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=20040205065009.GA30274@ice_nine.wi.rr.com \
    --to=avan@uwm.edu \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox