From: Jan Depner <eviltwin69@cableone.net>
To: Tim Goetze <tim@quitte.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: [ot] Re: Xruns with Audiophile 2496 M-audio
Date: Sat, 29 May 2004 10:32:10 -0500 [thread overview]
Message-ID: <1085844730.21679.33.camel@eviltwin> (raw)
In-Reply-To: <Pine.LNX.4.58.0405291614570.566@autumn>
On Sat, 2004-05-29 at 09:31, Tim Goetze wrote:
> depends on what 'system' we're talking about, which isn't really clear
> in the first place (nor is it too important, but here goes anyway ...
> :)
>
> you can see the whole setup as the system, then latency is the time
> from keypress to voltage change at the DAC out. or you can just look
> at the kernel side as as you do. or you can look at the time from MIDI
> interrupt to the audio DAC converting the first affected audio sample.
>
> all examples of valid 'systems' to look at in this context, depending
> on whether you assume the musician's, the kernel- or the audio
> application-programmer's view.
>
Agreed. But the problem that keeps popping up on the lists is that
people who are not doing live sound, have cards that do hardware
monitoring, and don't need to use a tiny buffer size waste their time
trying to get the minimum buffer size because they think they need to
get 2-3ms latency. So, they get xruns out the wazoo and wonder how to
fix it. In this case he *needs* a small buffer size though since he's
doing, essentially, a live application.
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 15:32 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
2004-05-29 12:06 ` [Alsa-devel] " 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 [this message]
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=1085844730.21679.33.camel@eviltwin \
--to=eviltwin69@cableone.net \
--cc=alsa-devel@lists.sourceforge.net \
--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.