5 Oct
2015
5 Oct
'15
11:59 p.m.
Ok it looks like I randomly selected jack and not jack2 on arch, so that
probably explains why it Just Works. Next time I'll try jack1 on debian
too.
Thx for the help all.
On 10/05/2015 07:40 AM, Paul Davis wrote:
Actually, this is still wrong (as was my comment).
JACK1 adds no
latency, and a very small amount of overhead. JACK2 run in its default
mode adds latency, and a very small amount of overhead. JACK2 run in
sync mode discards almost every benefit of using JACK2, adds no
latency and a very small amount of overhead.
I tend to forget this difference between JACK1 and JACK2.
On Mon, Oct 5, 2015 at 5:45 AM, Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
On 10/05/2015 01:25 AM, Ben Burdette wrote:
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user I've heard from someone else who seemed to
know things that jack does
add latency, but I haven't measured it myself... I'd be interested to
read about this lack of latency. But latency aside jack can be a
monumental hassle, don't get me started.
JACK does not add latency. It does
add some overhead, Jack2 some more
than Jack1, and especially on small ARM dev boards like the bananapi.
This overhead could get in the way of achieving the lowest latency
possible compared to using plain ALSA. So if you're using an ARM board
to output sound from a single application you might be better off using
plain ALSA.
Jeremy
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user