From: Lee Revell <rlrevell@joe-job.com>
To: "Valin, Jean-Marc (ICT Centre, Marsfield)" <jean-marc.valin@csiro.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rt11 and low-latency audio xruns (interrupt latency problem?)
Date: Thu, 30 Mar 2006 01:15:32 -0500 [thread overview]
Message-ID: <1143699333.15145.20.camel@mindpipe> (raw)
In-Reply-To: <1143695638.7328.5.camel@theorix.CeNTIE.NET.au>
On Thu, 2006-03-30 at 16:13 +1100, Valin, Jean-Marc (ICT Centre,
Marsfield) wrote:
> In this case,
> I'm running with two periods of 16 samples each (48 kHz), but I've
> seen
> that error occur with periods up to 64 samples.
It's possible that your hardware simply isn't capable of this and you'll
have to get a multichannel soundcard (more channels means you can use a
smaller buffer before hitting the lower limit of a PCI transfer) or use
a period of 128 samples or more.
Lee
next prev parent reply other threads:[~2006-03-30 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 5:13 2.6.16-rt11 and low-latency audio xruns (interrupt latency problem?) Valin, Jean-Marc (ICT Centre, Marsfield)
2006-03-30 6:15 ` Lee Revell [this message]
2006-03-30 6:19 ` Valin, Jean-Marc (ICT Centre, Marsfield)
2006-04-06 4:09 ` Valin, Jean-Marc (ICT Centre, Marsfield)
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=1143699333.15145.20.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jean-marc.valin@csiro.au \
--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