From: Lee Revell <rlrevell@joe-job.com>
To: A list for linux audio users <linux-audio-user@music.columbia.edu>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [linux-audio-user] Again on sudden and occasional Jack crackling sound
Date: Thu, 11 Aug 2005 11:33:34 -0400 [thread overview]
Message-ID: <1123774415.6980.18.camel@mindpipe> (raw)
In-Reply-To: <1123702719.24369.24.camel@mindpipe>
On Wed, 2005-08-10 at 15:38 -0400, Lee Revell wrote:
> So in both cases we're operating in mmap mode and ALSA is returning a
> slightly incorrect hardware pointer which leads to crackling.
Another thing to find out is whether this bug is more common when using
sample rates like 44100, 88200, where the number of periods per buffer
is not an integer.
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
prev parent reply other threads:[~2005-08-11 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42F02BB2.3000201@virgilio.it>
[not found] ` <42F62AE8.60604@virgilio.it>
[not found] ` <87r7d4xmxm.fsf@localhost.localdomain>
[not found] ` <42F7D849.3030000@virgilio.it>
[not found] ` <87ll3byh42.fsf@localhost.localdomain>
[not found] ` <1123557715.25617.32.camel@localhost.localdomain>
[not found] ` <42F8A6AE.6010609@virgilio.it>
[not found] ` <7q8xzb5ekw.fsf@io.com>
[not found] ` <42F92B60.9020909@virgilio.it>
[not found] ` <1123620561.25617.58.camel@localhost.localdomain>
2005-08-10 2:12 ` [linux-audio-user] Again on sudden and occasional Jack crackling sound Lee Revell
2005-08-10 19:38 ` Lee Revell
2005-08-11 15:33 ` Lee Revell [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=1123774415.6980.18.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-audio-user@music.columbia.edu \
/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.