[Jack-Devel] When netone jack backend is connected to jack_netsource, zita-ajbridge crashes. - JackAudio - lists.linuxaudio.org

List overview All Threads
Download

[Jack-Devel] When netone jack backend is connected to jack_netsource, zita-ajbridge crashes.

[Jack-Devel] Why does ionice...

[Jack-Devel] Port number limitation

crocket

18 Aug 2019 18 Aug '19

7:17 a.m.

After starting netone jack backend, zita-a2j, and zita-j2a, I started jack_netsource. zita-a2j and zita-j2a printed "Fatal error condition, terminating." and exited.

Attachments:

attachment.html (text/html — 207 bytes)

Reply

Show replies by date

Chris Caudle

18 Aug 18 Aug

1:50 p.m.

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_Net… 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(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Reply

crocket

4:21 p.m.

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 <chris(a)chriscaudle.org> 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_Net… 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(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

_______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Reply

crocket

23 Aug 23 Aug

8:50 a.m.

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 Mon, Aug 19, 2019 at 3:50 AM Chris Caudle <chris(a)chriscaudle.org> 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_Net… 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(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

_______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Reply

1702

days inactive

1707

days old

jackaudio@lists.linuxaudio.org

Manage subscription

3 comments

2 participants

tags (0)

participants (2)

Chris Caudle
crocket