[...]
> interestingly, the design of ASIO only allows 2 interrupts per
> hardware buffer. ALSA is much more flexible in handling this kind of
> thing.
A huge mistake of ASIO IMHO. On the Audiowerk8 for example,
running 3 interrupts per buffer allows using the input DMA interrupt
only; this interr
>The MAudio driver setup card was downright dishonest. It said "latency:
>128 samples", when actually latency was 256... that should have been
>labeled "buffer size" to be more honest.
michael - windows and linux use the term "buffer" in different
ways. on windows, it generally means "the chunk o
On Sat, 2004-06-12 at 17:01, Benno Senoner wrote:
> As said low latencies are cool so everyone tries to cheat and provide
> the per-fragment latencies in their settings/specs.
The MAudio driver setup card was downright dishonest. It said "latency:
128 samples", when actually latency was 256... th
Michael Ost wrote:
Well, no responses, no surprise... since this is a Windows/Mac issue.
But if you are curious, we scoped a win2k machine with a audiophile card
running vstack.
The latencies showed that the 128 sample setting matches an ALSA "semi
buffer". That is, a minimum of 256 samples of la
Well, no responses, no surprise... since this is a Windows/Mac issue.
But if you are curious, we scoped a win2k machine with a audiophile card
running vstack.
The latencies showed that the 128 sample setting matches an ALSA "semi
buffer". That is, a minimum of 256 samples of latency. This despite
Hi.
Does anyone out there know what the audio buffer size settings in
Windows and MacOS really mean? If you say "128 samples" does that
translate to 2 buffers of 128 samples --- one buffer playing, one buffer
filling --- or 2 buffers of 64 samples? Is it 256 samples of latency or
128?
I realize t
