SOLVED: Cadence / JACK2 won't start under Deb Jessie

[danboid]

I know that I've had Cadence running under Debian before but I'm not sure I ever had it running under Deb/KDE - certainly not recently under Deb Jessie, thats for sure.

When I try to start Cadence, I get the errors:

Code: Select all

Wed Apr 16 15:56:12 2014: Starting jack server...
Wed Apr 16 15:56:12 2014: JACK server starting in realtime mode with priority 10
Wed Apr 16 15:56:12 2014: self-connect-mode is "Don't restrict self connect requests"
Wed Apr 16 15:56:12 2014: ERROR: cannot register object path "/org/freedesktop/ReserveDevice1/Audio0": A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Wed Apr 16 15:56:12 2014: ERROR: Failed to acquire device name : Audio0 error : A handler is already registered for /org/freedesktop/ReserveDevice1/Audio0
Wed Apr 16 15:56:12 2014: ERROR: Audio device hw:0 cannot be acquired...
Wed Apr 16 15:56:12 2014: ERROR: Cannot initialize driver
Wed Apr 16 15:56:12 2014: ERROR: JackServer::Open failed with -1
Wed Apr 16 15:56:12 2014: ERROR: Failed to open server

I do not have Pulseaudio installed, nor has it ever been installed on this fresh Jessie (amd64) install, so its not a PA clash.

Code: Select all

lsof | grep asound
kded4     2260             d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
QInotifyF 2260 2296        d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
jackdbus  2497             d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
a2jmidid  2499             d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
kmix      2607             d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
QInotifyF 2607 2609        d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0

Code: Select all

cat /proc/asound/cards
 0 [HDMI           ]: HDA-Intel - HDA Intel HDMI
                      HDA Intel HDMI at 0xf7e14000 irq 49
 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7e10000 irq 45

I thought it could be KDE's sound system blocking JACK from using hw:1 so I disabled it under System Settings -> App and System Notifications -> Player Settings -> No audio output but I just get the same Cadence/JACK error.

Starting Cadence with

Code: Select all

cadence-session-start -s

Doesn't help either.

JACK/Cadence doesn't even offer me hw:1 as an option. lsof says kded4 is using asound but it shouldn't be after having disabled its audio notifications output, right?

Hopefully it doesn't require rebuilding KDE to fix this as IIRC KXStudio has patched KDE's sound system somehow. Was that just to stop the "Do you want to forget about this device?" prompts or did it fix this issue too?

[danboid]

As I said in the OP, I had already checked PA wasn't installed but I thought I'd run

Code: Select all

sudo apt-get purge pulseaudio*

and that removed 0 packages proving there is no trace of PA installed here.

So, I installed fluxbox and rebooted into that, via kdm. Now I get:

Code: Select all

lsof | grep asound
jackdbus  2307                d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0
a2jmidid  2309                d76  mem       REG                8,2  1011856 1315129 /usr/lib/x86_64-linux-gnu/libasound.so.2.0.0

Still I cannot choose hw:1 under JACK/Cadence so I'm out of ideas now - it prob wasn't kded grabbing my audio device after all.

I'm not running anything else except fluxbox and I'm loading a very bare set of services too - nothing audio reated.

[danboid]

Another weird thing is that JACK appears to start if I start it from the terminal with either

Code: Select all

jackd -d alsa -d hw:1,0

or

Code: Select all

jackd -d alsa -d hw:1

but if I then run the following

Code: Select all

jack_control status
--- status
stopped

Plus qtractor also tells me JACK isn't running after starting it via the terminal.

[danboid]

Code: Select all

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

[danboid]

Good points. I'll try installing J1 instead.

[danboid]

Yep - alls working fine as soon as I switched to jackd1. Of course, cadence auto-installs jackd2 when you install it via the KX repos.

I also had to add

Code: Select all

snd-aloop

To /etc/modules to get the ALSA bridge working on boot but that was all.

I'll have to report this to Mr Knoth.

[danboid]

It was a win for J1 but I'd still like to see the Jessie jackd2 package working again as I'd prefer to be running J2 so I can use j2ds.

Since I wrote j2ds, I mainly get by day-to-day using just that and kmix to control my sound devices. Its only really on the odd occasion when I need to change the JACK input device or when JACK needs to be force restarted do I need to open Cadence. I may want to switch to J1 when Cadence gains profile (and hopefully auto device switching) support.