From: Takashi Iwai <tiwai@suse.de>
To: Chris Meadors <clubneon@hereintown.net>
Cc: Russ Garrett <rg@tcslon.com>,
root@chaos.analogic.com, Jaroslav Kysela <perex@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Audio skipping with alsa
Date: Wed, 10 Sep 2003 20:27:06 +0200 [thread overview]
Message-ID: <s5hhe3kbith.wl@alsa2.suse.de> (raw)
In-Reply-To: <1063217788.2251.51.camel@clubneon.priv.hereintown.net>
At 10 Sep 2003 14:16:28 -0400,
Chris Meadors wrote:
>
> I'll agree that larger buffers are not the answer. I sometimes mess
> with live audio effects. That is recording some audio, processing it in
> some way, and then playing it back. If the buffer is too large, a
> noticeable delay would be introduced. Takashi and Jaroslav I'm pretty
> sure know the problem this causes with musicians, who need to hear what
> they played or sang in a very short period of time, or it messes with
> the brain.
to handle the data in a short period can be never guaranteed if the
process runs without the real-time priority.
the simple and only solution is to run such an application with
RT scheduling, IMO.
(the playback of xmms is a slightly different problem because it's
not designed (purposed) as a real-time process.)
--
Takashi Iwai <tiwai@suse.de> SuSE Linux AG - www.suse.de
ALSA Developer ALSA Project - www.alsa-project.org
prev parent reply other threads:[~2003-09-10 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 14:14 Audio skipping with alsa Russ Garrett
2003-09-10 13:23 ` Takashi Iwai
2003-09-10 13:38 ` Jaroslav Kysela
2003-09-10 13:45 ` Takashi Iwai
2003-09-10 14:45 ` Richard B. Johnson
2003-09-10 15:28 ` Con Kolivas
2003-09-10 15:43 ` Takashi Iwai
2003-09-10 17:47 ` Russ Garrett
2003-09-10 18:16 ` Chris Meadors
2003-09-10 18:27 ` Takashi Iwai [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=s5hhe3kbith.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rg@tcslon.com \
--cc=root@chaos.analogic.com \
/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