<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">On Tue, Oct 1, 2019 at 1:08 PM Steven Kruyswijk <<a href="mailto:stevenkruyswijk@gmail.com">stevenkruyswijk@gmail.com</a>> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ah... I only now realize that I need to utilize jackd1. Raspbian comes with<br>
jackd2 as standard.<br></blockquote><div><br></div><div><div style="font-family:arial,helvetica,sans-serif" class="gmail_default"><br><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">jack1 can't do anything that jack2 can't do (with respect to this problem). <br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">it's just that the zalsa_{in,out} functionality is implemented as an internal client in jack1, which makes it easier to invoke directly from the command given to start the JACK server.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">you can do the same thing using the separate zalsa_{inlout} clients with jack2.</div></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote></div></div>