<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Does JACK cause any additional buffering/latency in the signal flow
in comparison with pure ALSA? We have to take care of the lowest
latency as possible.<br>
<br>
<div class="moz-cite-prefix">On 10/22/2014 02:17 PM, Paul Davis
wrote:<br>
</div>
<blockquote
cite="mid:CAFa_cKma9pwGtie=a5w6xXsy-=cRxBJGE9PxH2BVRe=muLS2+g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 22, 2014 at 5:39 AM,
Vaclav Mach <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:vaclav.mach@artisys.aero" target="_blank">vaclav.mach@artisys.aero</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
</span>we have a bad experience with Jack: we were running
jack on a computer<br>
with external and internal sound cards simultaneously.
Jack was<br>
complaining that there is no clock sync (since there is no
clock sync<br>
possibility on internal HDA / sound blaster sound cards).</blockquote>
<div><br>
</div>
<div>sure, but this doesn't have anything to do with your
current issue or the system design you are using.<br>
<br>
</div>
<div>JACK is perfectly capable of using any number of audio
interfaces whether they are clock synced or not. It just
isn't a good idea and isn't how a professional system
would be built. It also isn't done by using the -P and -C
arguments to the backend, because this doesn't do any
resampling to keep the streams synchronized, but by using
bridge clients like zita_a2j.<br>
</div>
<div><br>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>