From: Florian Schmidt <mista.tapas@gmx.net>
To: Brian L Scipioni <brian@gaugetheory.org>
Cc: Jack O'Quin <joq@io.com>,
alsa-user@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] ALSA, JACK, ASIO
Date: Sat, 12 Feb 2005 13:32:06 +0100 [thread overview]
Message-ID: <20050212133206.7f0dc7a7@mango.fruits.de> (raw)
In-Reply-To: <1108029414.1806.23.camel@radium.gaugetheory.org>
On Thu, 10 Feb 2005 04:56:55 -0500
Brian L Scipioni <brian@gaugetheory.org> wrote:
> Thanks. A couple more ASIO questions:
>
> Could the ASIO protocol be implemented on top of ALSA or within JACK?
> Would it provide for low(er) latency operation on cards that support it?
> Would ASIO perhaps just provide some parallel functionality that is
> already represented in ALSA and/or JACK?
AFAIK ASIO was introduced because the win32 mm drivers sucked badly and
didn't allow to use a soundcard to its full potential. As ALSA doesn't
have the problem of being completely braindead (as the win 32 mm driver
(architecture) were), there's no need for ASIO on linux..
To answer the other post: With a modern Realtime Preemption kernel and
an M-Audio Delta 66 i can use buffersizes of 32 or even 16 frames
without dropouts (except for those produced by badly coded apps) with
jack using its ALSA driver. The cpu load goes up a bit though with such
small periodsizes due to context switch overhead, etc. It's very well
suited for noodling my guitar through jack-rack though :) At a
samplerate of 48khz a buffersize of 16 frames corresponds to an input
latency of 0.3ms. The same for output latency. Disregarding any
processing latencies by effects i use this gives a total roundtrip
latency of around 0.6ms. I find a buffer size of 32 frames (1.2ms
roundtrip latency) still perfectly usable with no audible delay (at
least for my ears),,
Your results might differ greatly depending on the soundcard used. For
example my CS46xx based terratec dmx xfire 1024 always produced some
xruns, even at 512 frames. I suspect either a driver or a hardware
problem.
Flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-12 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e47339105020710162d246fed@mail.gmail.com>
[not found] ` <s5his52u6et.wl@alsa2.suse.de>
[not found] ` <9e473391050208182623c5b3ea@mail.gmail.com>
[not found] ` <1107982073.1806.10.camel@radium.gaugetheory.org>
[not found] ` <87y8dxp9fm.fsf@sulphur.joq.us>
2005-02-10 9:56 ` ALSA, JACK, ASIO Brian L Scipioni
2005-02-12 12:32 ` Florian Schmidt [this message]
2005-02-10 10:47 ` Brian L Scipioni
2005-02-10 15:11 ` [Alsa-user] " Rick B
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=20050212133206.7f0dc7a7@mango.fruits.de \
--to=mista.tapas@gmx.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=brian@gaugetheory.org \
--cc=joq@io.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 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.