LinuxMusicians

Posted: **Sat Jun 07, 2014 6:34 pm**

I'm running Arch Linux and have installed cadence 0.8.1-1 and running jack2-dbus-1.9.9.5-4.

I tried installing jack2-kxstudio but it would not install:
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: jack2-kxstudio and jack2-kxstudio-dbus are in conflict

Proceeding On:

In Cadence I selected the firewire driver, left setting at defaults,
and for the Bridge selected ALSA -> JACK.

JACK starts but nothing is able to connect to it.
I've tried Ardour, Hydrogen, mplayer -ao jack, etc...

Example:

Code: Select all

mplayer -ao jack test.mp3
   Cannot connect to server socket err = No such file or directory
   Cannot connect to server request channel
   jack server is not running or cannot be started
   [JACK] cannot open server
   Failed to initialize audio driver 'jack'
   Could not open/initialize audio device -> no sound.

JACK log:

Code: Select all

Sat Jun  7 12:27:25 2014: Starting jack server...
Sat Jun  7 12:27:25 2014: JACK server starting in realtime mode with priority 10
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Rec 1_in'
Sat Jun  7 12:27:35 2014: New client 'firewire_pcm' with PID 0
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Rec 2_in'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Rec 3_in'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Rec 4_in'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Midi In_in'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 1_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 2_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 3_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 4_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 5_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 6_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 7_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 8_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 9_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Play 10_out'
Sat Jun  7 12:27:35 2014: graph reorder: new port 'firewire_pcm:00130e0100010c0b_Midi Out_out'

Earlier I did see the following error in the JACK log but it has not occurred lately:

Code: Select all

ERROR: firewire MSG: Starting FFADO backend (libffado 2.1.0-Unversioned directory

Here the firewire devices:

Code: Select all

ffado-test ListDevices
=== 1394 PORT 0 ===
  Node id  GUID                  VendorId     ModelId   Vendor - Model
   0       0x0000ba0000000026  0x000000BA  0x00000000   Linux Firewire -
   1       0x00130e0100010c0b  0x0000130E  0x00000000   Focusrite - Saffire
   no message buffer overruns

I tested the connection to the Saffire with ffado-mixer and had no problems making changes to the settings, so I don't feel like it is a FFADO issue.

Checking permissions:

Code: Select all

ls -l /dev/fw*
   crw-rw----  1 root audio 250, 0 Jun  7 09:14 /dev/fw0
   crw-rw----+ 1 root audio 250, 1 Jun  7 09:14 /dev/fw1

I am a member of the audio group

Any help appreciated...

Posted: **Sat Jun 07, 2014 8:54 pm**

I ran strace against mplayer and found the with the following:

Code: Select all

connect(14, {sa_family=AF_LOCAL, sun_path="/dev/shm/jack_default_1000_0"}, 110) = -1 ENOENT (No such file or directory)
write(2, "Cannot connect to server socket "..., 64Cannot connect to server socket err = No such file or directory
) = 64
close(14)

Here is a listing of /dev/shm/

Code: Select all

ls -l /dev/shm/
   total 21284
   -rw-rw-rw-  1 tc1384 tc1384    70712 Jun  7 11:35 jack-shm-registry
   drwxr-xr-x 21 root     root         3460 Jun  7 11:56 ..
   -rw-r--r--  1 tc1384 tc1384 21701018 Jun  7 12:27 jack-1000-0
   -rw-r--r--  1 tc1384 tc1384      994 Jun  7 12:27 jack-1000-1
   -rwxr-xr-x  1 tc1384 tc1384       32 Jun  7 12:27 sem.jack_sem.1000_firewire_system
   -rwxr-xr-x  1 tc1384 tc1384       32 Jun  7 12:27 sem.jack_sem.1000_firewire_freewheel
   srwxr-xr-x  1 tc1384 tc1384        0 Jun  7 12:27 jack_firewire_1000_0
   -rwxr-xr-x  1 tc1384 tc1384       32 Jun  7 12:27 sem.jack_sem.1000_firewire_dbusapi
   drwxrwxrwt  2 root     root          180 Jun  7 15:23 .

At this point I havn't figured out why there is a socket name discrepancy.

Posted: **Sat Jun 07, 2014 9:23 pm**

Ok - I figured it out.

I had changed the "Server name" in Cadence from its default value of "default"

I did a cadence-session-start --reset and now everything works...

Edit:

/dev/shm/ now contains:

srwxr-xr-x 1 tc1384 tc1384 0 Jun 8 08:55 jack_default_1000_0

which is apparently is the socket name the apps are looking for.

LinuxMusicians

Apps Unable to Connect to Jack

Apps Unable to Connect to Jack

Re: Apps Unable to Connect to Jack

Re: Apps Unable to Connect to Jack