Jack a2j question

Sorry if this issue isn’t appropriate for this forum, so apologies in advance but…

I downloaded a .deb of ChowDSP’s Multi-Tool yesterday and installed it on Ubuntu Studio 22.04

during the install’s flurry of terminal info flying by I noticed it some apps/utilities were being deleted but thought maybe it was upgrading sound libs and things…long mix session & tired

everything seemed OK after the install until I booted into UbStu again today and Jack wouldn’t start

The install apparently hosed some parts of Jack & a2j

so I reinstalled Jack and a2j and got my system (sound & midi) working again

except for one small issue:

  • if I start my ICON M+ controller before I start Jack/a2j etc. Jack/ALSA doesn’t pick up the presence of the M+ controller

//it used to be that the launch sequence didn’t matter…J/A just knew what was connected

  • if I start Jack THEN turn on my M+ controller, it shows up as expected in the Jack graph a2j IO blocks (as well as the Carla patchbay) and connects to Ardour via the Mackie control in/out ports as expected

  • something in my system changed after the ChowDSP .deb install so I’m assuming the install might have deleted something in ALSA and/or a2j land but I can’t figure out what

Any hints, links or RTFMs appreciated! :slight_smile:

KC

My first guess would be that ChowDSP installed a new udev rule which does something new when the ICON is detected.
The udev files are in /usr/lib/udev/rules.d but I don’t have a good starting guess what the file might look like.
Does apt have a way to list what files in a particular package? If so you could look for a file with .rules extension on the filename in the ChowDSP package.

1 Like

I looked in /usr/lib/udev/rules.d & the only file recently created was /usr/lib/udev/rules.d/64-xorg-xkb.rules which imports keyboard layout. That file was created on June 8 (a Kubuntu update) the day after I installed ChowDSP Multi-Tool.

comment in the file:
// #import keyboard layout from /etc/default/keyboard .

here are the contents of the ChowMultiTool-Linux-x64-1.1.0.deb file


dpkg -c ~/Downloads/ChowMultiTool-Linux-x64-1.1.0.deb
drwxr-xr-x runner/docker     0 2024-02-13 10:09 ./
drwxr-xr-x runner/docker     0 2024-02-13 10:09 ./usr/
drwxr-xr-x runner/docker     0 2024-02-13 10:09 ./usr/bin/
-rwxr-xr-x runner/docker 19594624 2024-02-13 10:09 ./usr/bin/ChowMultiTool
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/clap/
-rwxr-xr-x runner/docker 20684448 2024-02-13 10:09 ./usr/lib/clap/ChowMultiTool.clap
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/lv2/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/lv2/ChowMultiTool.lv2/
-rw-r--r-- runner/docker    37696 2024-02-13 10:09 ./usr/lib/lv2/ChowMultiTool.lv2/dsp.ttl
-rw-r--r-- runner/docker 20593384 2024-02-13 10:09 ./usr/lib/lv2/ChowMultiTool.lv2/libChowMultiTool.so
-rw-r--r-- runner/docker     4963 2024-02-13 10:09 ./usr/lib/lv2/ChowMultiTool.lv2/manifest.ttl
-rw-r--r-- runner/docker      657 2024-02-13 10:09 ./usr/lib/lv2/ChowMultiTool.lv2/ui.ttl
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/vst3/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/vst3/ChowMultiTool.vst3/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/vst3/ChowMultiTool.vst3/Contents/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/lib/vst3/ChowMultiTool.vst3/Contents/x86_64-linux/
-rw-r--r-- runner/docker 21091424 2024-02-13 10:09 ./usr/lib/vst3/ChowMultiTool.vst3/Contents/x86_64-linux/ChowMultiTool.so
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/share/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/share/ChowMultiTool/
drwxr-xr-x runner/docker        0 2024-02-13 10:09 ./usr/share/ChowMultiTool/doc/
-rw-r--r-- runner/docker      232 2024-02-13 10:09 ./usr/share/ChowMultiTool/doc/changelog.Debian.gz
-rw-r--r-- runner/docker    35149 2024-02-13 10:09 ./usr/share/ChowMultiTool/doc/copyright

I’m guessing it’s how they set up the install script b/c a lot of Jack/ALSA stuff got hosed in the process

I contacted ChowDSP about this and am waiting to hear from them about remedying this but in the meantime I can live with retweaking my launch sequence.

thanks for the suggestion! :slight_smile:

The file list you posted actually looks perfectly normal for a Debian package installing into the shared /usr/bin / /usr/lib / /usr/share directories: those top-level directories are jointly shared by every package which installs under them, and the ChowMultiTool....deb package has behaved perfectly (AFAICT looking at that listing).

Note that /usr/lib/udev/rules.d/64-xorg-xkb.rules is not listed as being owned by that package, which is actually kind of normal (those are config files, not software files). On my system, exactly one of the 100+ files in /usr/lib/udev/rules.d/ is owned by any package at all:

$ dpkg-query --search /usr/lib/udev/rules.d/*
dpkg-query: no path found matching pattern /usr/lib/udev/rules.d/01-md-raid-creating.rules
...
dpkg-query: no path found matching pattern /usr/lib/udev/rules.d/85-hplj10xx.rules
util-linux: /usr/lib/udev/rules.d/85-hwclock.rules
dpkg-query: no path found matching pattern /usr/lib/udev/rules.d/85-nm-unmanaged.rules
...
dpkg-query: no path found matching pattern /usr/lib/udev/rules.d/99-vmware-scsi-udev.rules