I spent a lot of time trying to figure out why jack was not running. As it turns out, it is:
Code:
# ps uax | grep jack
root 955 0.0 0.1 12848 2200 - I<s 00:22 0:00.00 daemon: /usr/local/bin/jackd[956] (daemon)
luc 956 0.0 6.3 149684 129300 - I<s 00:22 0:00.17 /usr/local/bin/jackd -R -doss -r48000 -p1024 -n1 -w16 --capture /dev/dsp0 --playback /dev/dsp0
luc 1157 0.0 0.3 18248 6196 - Ss 00:45 0:00.69 /usr/local/bin/jackdbus auto
root 1287 0.0 0.0 436 252 0 R+ 01:27 0:00.00 grep jack
And there is a socket:
Code:
# ls -la /tmp/jack_default_1001_0
srwxr-xr-x 1 luc wheel 0 Mar 3 00:22 /tmp/jack_default_1001_0
But cadence, catia, qjackctl and qtractor cannot connect to it.
Cadence has this in the log:
Code:
Fri Mar 3 00:45:59 2023: ------------------
Fri Mar 3 00:45:59 2023: Controller activated. Version 1.9.22 ([]) built on Sat Feb 18 07:28:18 2023
Fri Mar 3 00:45:59 2023: ERROR:
Fri Mar 3 00:45:59 2023: ERROR: jack_get_descriptor returns null for 'jack_inprocess.so'
Fri Mar 3 00:45:59 2023: ERROR:
Fri Mar 3 00:45:59 2023: ERROR: jack_get_descriptor returns null for 'jack_intime.so'
Fri Mar 3 00:45:59 2023: ERROR:
Fri Mar 3 00:45:59 2023: ERROR: jack_get_descriptor returns null for 'jack_internal_metro.so'
Fri Mar 3 00:45:59 2023: Loading settings from "/home/luc/.config/jack/conf.xml" using expat_2.5.0 ...
Fri Mar 3 00:45:59 2023: setting parameter 'engine':'driver':'(null)' to value "dummy"
Fri Mar 3 00:45:59 2023: setting parameter 'drivers':'dummy':'rate' to value "48000"
Fri Mar 3 00:45:59 2023: Listening for D-Bus messages
Fri Mar 3 00:47:42 2023: Starting jack server...
Fri Mar 3 00:47:42 2023: ERROR: `default' server already active
Fri Mar 3 00:47:42 2023: ERROR: Failed to open server
Catia gives me this terminal output:
Code:
catia
Cannot read socket fd = 14 err = Socket is not connected
CheckRes error
JackSocketClientChannel read fail
Cannot open catia client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
The cadence log is more interesting. It says:
Code:
Fri Mar 3 00:45:59 2023: Loading settings from "/home/luc/.config/jack/conf.xml" using expat_2.5.0 ...
This is the content of /home/luc/.config/jack/conf.xml:
Code:
<?xml version="1.0"?>
<!--
JACK settings, as persisted by D-Bus object.
You probably don't want to edit this because
it will be overwritten next time jackdbus saves.
-->
<!-- Fri Mar 3 00:51:04 2023 -->
<jack>
<engine>
<option name="driver">dummy</option>
</engine>
<drivers>
<driver name="dummy">
</driver>
<driver name="oss">
</driver>
<driver name="loopback">
</driver>
<driver name="net">
</driver>
<driver name="netone">
</driver>
<driver name="proxy">
</driver>
</drivers>
<internals>
<internal name="netmanager">
</internal>
<internal name="audioadapter">
</internal>
<internal name="profiler">
</internal>
<internal name="netadapter">
</internal>
</internals>
</jack>
I see it's selecting the "dummy" driver instead of "oss." And I can't edit it because jackdbus will overwrite it.
I checked the cadence configuration dialogs and found something intriguing.
This is cadence in FreeBSD:
This is cadence in Linux:
How come cadence in Linux has an ALSA tab and cadence in FreeBSD doesn't have an OSS tab?
Is that supposed to be correct?
Would cadence be able to connect if it could "see" the oss driver?
What about the other applications? Why can't they connect to jack?
vermaden.wordpress.com
