Re: When netone jack backend is connected to jack_netsource, zita-ajbridge crashes.

--===============6953310098424712432==
Content-Type: multipart/alternative; boundary="000000000000fcfd8a05906acf24"

--000000000000fcfd8a05906acf24
Content-Type: text/plain; charset="UTF-8"

netone runs on my desktop computer(192.168.30.2). jack_netsource runs on
Raspberry Pi 3 B+(192.168.30.1). My desktop computer and Raspberry Pi  3B+
are connected directly by an ethernet cable.
Raspberry Pi 3 B+ runs for 24 hours a day. I turn on my desktop computer
when I want to use it.

On Mon, Aug 19, 2019 at 3:50 AM Chris Caudle <[email protected]> wrote:

> On Sun, August 18, 2019 7:17 am, crocket wrote:
> > After starting netone jack backend, zita-a2j, and zita-j2a, I started
> > jack_netsource.
>
> If you did that all on the same jack server you are starting up
> incorrectly.  The jack server should be started with netjack backend on
> the slave, then jack_netsource on the master jack server (i.e. t he jack
> server running the ALSA backend).
> See:
>
> https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_NetJack
>
>
>     Start JACK on the master machine as you usually do (using a JACK
> controler like qjackctl, pyjackctl, or on the command line)
>     Start JACK with the net backend on the slave machine
>     jackd -R -d net
>     or for jack2
>     jackd -R -d netone
>     For jack1: Remember not to connect any clients to the slave JACK until
> we've connected both machines ! This limitation is gone with jack2,
> however, some clients might crash, when jack is changing the buffer
> size.
>     Launch 'jack_netsource' on the master JACK to connect your slave:
>     jack_netsource -H <slave jack hostname>
>
>
> --
> Chris Caudle
>
>
> > zita-a2j and zita-j2a printed "Fatal error condition, terminating." and
> > exited.
> > _______________________________________________
> > Jack-Devel mailing list
> > [email protected]
> > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> >
>
>
> _______________________________________________
> Jack-Devel mailing list
> [email protected]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>

--000000000000fcfd8a05906acf24
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">netone runs on my desktop computer(192.168.30.2). jack_net=
source runs on Raspberry Pi 3 B+(192.168.30.1). My desktop computer and Ras=
pberry Pi=C2=A0 3B+ are connected directly by an ethernet cable.<div>Raspbe=
rry Pi 3 B+ runs for 24 hours a day. I turn on my desktop computer when I w=
ant to use it.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Mon, Aug 19, 2019 at 3:50 AM Chris Caudle &lt;<a hre=
f=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, August 18, =
2019 7:17 am, crocket wrote:<br>
&gt; After starting netone jack backend, zita-a2j, and zita-j2a, I started<=
br>
&gt; jack_netsource.<br>
<br>
If you did that all on the same jack server you are starting up<br>
incorrectly.=C2=A0 The jack server should be started with netjack backend o=
n<br>
the slave, then jack_netsource on the master jack server (i.e. t he jack<br=
>
server running the ALSA backend).<br>
See:<br>
<a href=3D"https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrou=
gh_User_NetJack" rel=3D"noreferrer" target=3D"_blank">https://github.com/ja=
ckaudio/jackaudio.github.com/wiki/WalkThrough_User_NetJack</a><br>
<br>
<br>
=C2=A0 =C2=A0 Start JACK on the master machine as you usually do (using a J=
ACK<br>
controler like qjackctl, pyjackctl, or on the command line)<br>
=C2=A0 =C2=A0 Start JACK with the net backend on the slave machine<br>
=C2=A0 =C2=A0 jackd -R -d net<br>
=C2=A0 =C2=A0 or for jack2<br>
=C2=A0 =C2=A0 jackd -R -d netone<br>
=C2=A0 =C2=A0 For jack1: Remember not to connect any clients to the slave J=
ACK until<br>
we&#39;ve connected both machines ! This limitation is gone with jack2,<br>
however, some clients might crash, when jack is changing the buffer<br>
size.<br>
=C2=A0 =C2=A0 Launch &#39;jack_netsource&#39; on the master JACK to connect=
 your slave:<br>
=C2=A0 =C2=A0 jack_netsource -H &lt;slave jack hostname&gt;<br>
<br>
<br>
-- <br>
Chris Caudle<br>
<br>
<br>
&gt; zita-a2j and zita-j2a printed &quot;Fatal error condition, terminating=
.&quot; and<br>
&gt; exited.<br>
&gt; _______________________________________________<br>
&gt; Jack-Devel mailing list<br>
&gt; <a href=3D"mailto:[email protected]" target=3D"_blank">Ja=
[email protected]</a><br>
&gt; <a href=3D"http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudi=
o.org" rel=3D"noreferrer" target=3D"_blank">http://lists.jackaudio.org/list=
info.cgi/jack-devel-jackaudio.org</a><br>
&gt;<br>
<br>
<br>
_______________________________________________<br>
Jack-Devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Jack-De=
[email protected]</a><br>
<a href=3D"http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org=
" rel=3D"noreferrer" target=3D"_blank">http://lists.jackaudio.org/listinfo.=
cgi/jack-devel-jackaudio.org</a><br>
</blockquote></div>

--000000000000fcfd8a05906acf24--

--===============6953310098424712432==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Jack-Devel mailing list
[email protected]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

--===============6953310098424712432==--