Using Manjaro MATE (community edition) and running JACK2 audio-server, with Cadence and the integrated audio-device Intel NM10/ICH7 , Cadence does not always launch JACK automatically, though having entered the auto-start option on Cadence.
It launch it more times (not always) if there are selected Input and Output Devices, in ALSA Driver settings, instead of selecting on the Device/Interface option (though actually it's the same ports).
These are the JACK's logs:
Wed Apr 22 07:52:08 2020: Controller activated. Version 1.9.14 (unknown) built on Tue Nov 19 19:56:27 2019
Wed Apr 22 07:52:08 2020: ERROR: Could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
Wed Apr 22 07:52:08 2020: ERROR: Could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
Wed Apr 22 07:52:08 2020: ERROR: jack_get_descriptor : dll jack_firewire.so is not a driver
Wed Apr 22 07:52:08 2020: ERROR: jack_get_descriptor returns null for 'jack_firewire.so'
Wed Apr 22 07:52:08 2020: ERROR: Could not open component .so '/usr/lib/jack/jack_firewire.so': libffado.so.2: cannot open shared object file: No such file or directory
Wed Apr 22 07:52:08 2020: Loading settings from "/home/porru/.config/jack/conf.xml" using expat_2.2.9 ...
Wed Apr 22 07:52:08 2020: setting parameter 'engine':'driver':'(null)' to value "alsa"
Wed Apr 22 07:52:08 2020: setting parameter 'engine':'realtime-priority':'(null)' to value "10"
Wed Apr 22 07:52:08 2020: setting parameter 'drivers':'alsa':'device' to value "hw:Intel,0"
Wed Apr 22 07:52:08 2020: setting parameter 'drivers':'alsa':'rate' to value "48000"
Wed Apr 22 07:52:08 2020: setting parameter 'drivers':'alsa':'period' to value "2048"
Wed Apr 22 07:52:08 2020: setting parameter 'drivers':'alsa':'inchannels' to value "0"
Wed Apr 22 07:52:08 2020: setting parameter 'drivers':'alsa':'outchannels' to value "0"
Wed Apr 22 07:52:08 2020: Listening for D-Bus messages
Wed Apr 22 07:52:08 2020: Starting jack server...
Wed Apr 22 07:52:08 2020: JACK server starting in realtime mode with priority 10
Wed Apr 22 07:52:08 2020: self-connect-mode is "Don't restrict self connect requests"
Wed Apr 22 07:52:14 2020: Device reservation request with priority 2147483647 denied for "Audio0": org.freedesktop.DBus.Error.NoReply (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply,
Wed Apr 22 07:52:14 2020: ERROR: Failed to acquire device name : Audio0 error : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broke
Wed Apr 22 07:52:14 2020: ERROR: Audio device hw:Intel,0 cannot be acquired...
Wed Apr 22 07:52:14 2020: ERROR: Cannot initialize driver
Wed Apr 22 07:52:14 2020: ERROR: JackServer::Open failed with -1
Wed Apr 22 07:52:14 2020: ERROR: Failed to open server
This occurs mainly in Arch-based distros, though it also has occurred to me on Debian.
Using Manjaro MATE (community edition) and running JACK2 audio-server, with Cadence and the integrated audio-device Intel NM10/ICH7 , Cadence does not always launch JACK automatically, though having entered the auto-start option on Cadence.
It launch it more times (not always) if there are selected Input and Output Devices, in ALSA Driver settings, instead of selecting on the Device/Interface option (though actually it's the same ports).
These are the JACK's logs:
This occurs mainly in Arch-based distros, though it also has occurred to me on Debian.
The same issue in Manjaro's Forum: JACK 2 not autostarting via Cadence