From: Jan Depner <eviltwin69@cableone.net>
To: Remi Bernhard <rgbmlist2@free.fr>
Cc: Tim Goetze <tim@quitte.de>,
alsa-user@lists.sourceforge.net,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Xruns with Audiophile 2496 M-audio
Date: Sat, 29 May 2004 06:31:17 -0500 [thread overview]
Message-ID: <1085830277.21677.17.camel@eviltwin> (raw)
In-Reply-To: <20040529131601.641aa202@pentium233.krystal.net>
On Sat, 2004-05-29 at 06:16, Remi Bernhard wrote:
> So i have 2.6.5 kernel, and not 2.4.x. Do you think i should install
> 2.4.25 instead ?
>
> >
> > (i gather that 2.4 is still the better choice for low-latency
> > operations.)
> >
>
> I read the alsa-* archives, and i saw a thread with two people who had
> good latency results with 2.6.x.
> Could someone tell me if man can achieve a buffer size <=128 with
> audiophile 2496 and kernel 2.6.x ?
>
Yes. The 2.4 kernels with low latency patch are better than 2.6 at
present (even the mm series). The buffer sizes you can achieve are
dependent on so many different things (disks, FSB, memory,
configuration...) that there is no way to tell. You just have to try it
and find out. As far as minimizing buffer size is concerned - if you
are doing live audio or you want to monitor recording with inboard
effects turned on you need to have a small buffer size. With the envy24
chipset cards you can use hardware monitoring so you can set the buffer
size to 2048 and have zero latency monitoring. Don't confuse monitoring
latency with system latency.
Jan
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-05-29 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 9:49 Xruns with Audiophile 2496 M-audio Remi Bernhard
2004-05-29 10:52 ` Tim Goetze
2004-05-29 11:16 ` [Alsa-devel] " Remi Bernhard
2004-05-29 11:31 ` Jan Depner [this message]
2004-05-29 12:06 ` Remi Bernhard
2004-05-29 12:13 ` Tim Goetze
2004-05-29 14:01 ` Jan Depner
2004-05-29 14:31 ` [ot] " Tim Goetze
2004-05-29 15:32 ` Jan Depner
2004-05-29 16:34 ` Tim Goetze
2004-05-29 11:44 ` Tim Goetze
2004-05-29 14:00 ` [Alsa-devel] " Remi Bernhard
2004-05-29 14:34 ` Tim Goetze
2004-05-30 9:09 ` [Alsa-devel] " Remi Bernhard
2004-05-30 13:35 ` Jan Depner
2004-05-30 14:55 ` Remi Bernhard
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=1085830277.21677.17.camel@eviltwin \
--to=eviltwin69@cableone.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=rgbmlist2@free.fr \
--cc=tim@quitte.de \
/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.