I worked around the issue by making zita-a2j and zita-j2a start after "system:playback_1" and "system:playback_2" appear. They appear only after netone is connected to jack_netsource.
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
> Jack-Devel@lists.jackaudio.org
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
Jack-Devel mailing list
Jack-Devel@lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org