<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#333333" text="#FFFFFF">
<div class="moz-cite-prefix">On 08/15/16 14:11, xan wrote:<br>
</div>
<blockquote cite="mid:f77691c2-4c75-8bb0-9791-c7efd2590d2f@0l3.de"
type="cite">
<pre wrap="">Hi,
after some weeks of silence, I got back to this issue. I installed zita-njbridge on both my machines, started the JACK server and tried to run the commands.
'zita-j2n b`s-ip port' is running on A and 'zita-n2j a`s-ip port' is running on B.
However, I don`t know the port I`m supposed to use and I couldn` find out.
The command seems to run on A but fails on B: "Failed to connect to socket. Cannot assign request address."
I`d appreciate some debugging here.
Thanks in advance,
xan.
Am 19.07.2016 um 07:13 schrieb Athanasios Silis:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Fons,
i'm not implying there was something wrong with zita-*2*, i'm sure in fact it is some network issue that caused the jitter from the speakers, it was nonetheless a jitter.
Now where zita-*2* offered jitter ,alsa_* did not , provided the same arguments where used (ie for low latency).
I am sure had I spend more time on it I would have found a solution - i do not question zita-* is "future" while alsa_* is "obsolete", but for the given transition to zita-* , I had to revert to alsa_*
On Thu, Jul 14, 2016 at 8:53 PM, Fons Adriaensen <<a class="moz-txt-link-abbreviated" href="mailto:fons@linuxaudio.org">fons@linuxaudio.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:fons@linuxaudio.org"><mailto:fons@linuxaudio.org></a>> wrote:
On Thu, Jul 14, 2016 at 04:32:29PM +0300, Athanasios Silis wrote:
> in a similar setup zita* stuff has not worked great for me - I got alot of
> noise , so I switched to using the more primitive alsa_in and alsa_out.
There a many ways a link using zita-*2* can go wrong, depending on
network performance and if your Jack systems by themselves are OK
or not. But 'noise' is not one of the possible results.
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Jack-Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:Jack-Devel@lists.jackaudio.org"><mailto:Jack-Devel@lists.jackaudio.org></a>
<a class="moz-txt-link-freetext" href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a>
_______________________________________________
Jack-Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a>
<a class="moz-txt-link-freetext" href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Jack-Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Jack-Devel@lists.jackaudio.org">Jack-Devel@lists.jackaudio.org</a>
<a class="moz-txt-link-freetext" href="http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org">http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org</a>
</pre>
</blockquote>
<br>
<p>b should also have b's ip. i use ports in the 46xx range - not
sure why. it works.<br>
</p>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-abbreviated" href="http://www.the-temp-agency.com/lollipop-factory">www.the-temp-agency.com/lollipop-factory</a></pre>
</body>
</html>