6 Sep
2005
6 Sep
'05
2:23 p.m.
Full-duplex I/O with a minimal number of intervening buffers required (i.e.
very low throughput latency), preferably accessed through a callback
interface like JACK's. Last time I tried this it was quite complicated.
Maybe this has gotten easier in the last 2 years, but the docs don't seem to
be any different.
-Ben
OK.
So what exactly is meant here by "synchronized I/O"?
Lee
6 Sep
6 Sep
2:39 p.m.
On Tue, 2005-09-06 at 12:05 -0500, Ben Loftis wrote:
Full-duplex I/O with a minimal number of intervening
buffers required (i.e.
very low throughput latency), preferably accessed through a callback
interface like JACK's. Last time I tried this it was quite complicated.
Maybe this has gotten easier in the last 2 years, but the docs don't seem to
be any different.
2:40 p.m.
On Tue, 2005-09-06 at 12:05 -0500, Ben Loftis wrote:
Full-duplex I/O with a minimal number of intervening
buffers required (i.e.
very low throughput latency), preferably accessed through a callback
interface like JACK's. Last time I tried this it was quite complicated.
Maybe this has gotten easier in the last 2 years, but the docs don't seem to
be any different.
if it was simpler, i would hope that some kind soul would have stepped
up with patches to save JACK's ALSA backend from itself :) since nobody
has, i can only conclude that its much the same as its always been.
--p
7047
days inactive
7047
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
2 participants
participants (2)
-
Ben Loftis -
Paul Davis