From: john slee <indigoid@higherplane.net>
To: clock@atrey.karlin.mff.cuni.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: Inadmissible sound dropouts on 2.2.18
Date: Sun, 4 Feb 2001 23:43:52 +1100 [thread overview]
Message-ID: <20010204234352.D32071@higherplane.net> (raw)
In-Reply-To: <20010204120728.48319@ghost.btnet.cz>
In-Reply-To: <20010204120728.48319@ghost.btnet.cz>; from clock@ghost.btnet.cz on Sun, Feb 04, 2001 at 12:07:28PM +0100
On Sun, Feb 04, 2001 at 12:07:28PM +0100, clock@ghost.btnet.cz wrote:
> The crackling is not dependent on the buffer size you can set up in the C code.
> The crackling is dependent on the frequency of the sine. It's clearly audible
> (read: annoying) at 10kHz, audible at 1kHz, inaudible at 100Hz. So I think
> they are sample dropouts - the card stops playing and repeats one sample until
> kernel gets the breath and whips itself up to supply next audio data.
hrm, i just ran your test progam. i don't hear this on my gus classic /
celeron 533 / 320mb ram. at least nothing that *sounds* like crackling.
just a high pitched annoying noise. using 2.4.1 + andrew morton's
lowlatency patches. (which are wonderful, thanks andrew!)
jiggle the cable from the GUS to wherever it goes to.
j.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-04 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 11:07 Inadmissible sound dropouts on 2.2.18 clock
2001-02-04 12:43 ` john slee [this message]
2001-02-10 22:32 ` Pavel Machek
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=20010204234352.D32071@higherplane.net \
--to=indigoid@higherplane.net \
--cc=clock@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox