From: Anthony <avan@uwm.edu>
To: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 noise
Date: Sat, 31 Jan 2004 13:57:52 -0600 [thread overview]
Message-ID: <20040131195752.GA4224@ice_nine.wi.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401311125130.1876@pnote.perex-int.cz>
* 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
I hope not! I think it occurs on all channels, but have
yet to reproduce it today to verify. I'm thinking about
installing a windows OS and testing there. I've also
noticed immediately after upgrading to 1.0.2 that I get
occasional drop outs on playback...they are not xruns,
at least they dont sound as harsh and jackd doesn't
report them - just an instant of silence.
--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
next prev parent reply other threads:[~2004-01-31 19:57 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 [this message]
2004-02-05 6:50 ` Anthony
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=20040131195752.GA4224@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 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.