27 Mar
2009
27 Mar
'09
8:27 p.m.
On Sat Mar 28 6:37 , Atte André Jensen sent:
Hi
I went ahead and got myself a edirol fa-66. Having no experience with
firewire I have no idea why it doesn't work. The problem is that jack
(qjackctl) seems to start up fine, but dies after a few seconds. My jack
settings are IMO conservative: buffer size of 256.
Here's what's printed in "messages":
19:39:10.306 Patchbay activated.
19:39:10.354 Statistics reset.
19:39:10.364 Startup script...
19:39:10.365 artsshell -q terminate
19:39:10.403 ALSA connection graph change.
19:39:10.787 Startup script terminated with exit status=256.
19:39:10.788 JACK is starting...
19:39:10.788 /usr/bin/jackd -R -P80 -m -dfreebob -dhw:0 -r48000 -p128 -n3 -D
19:39:10.790 JACK was started with PID=10604.
jackd 0.109.2
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
Freebob using Firewire port 0, node -1
19:39:10.989 MIDI active patchbay scan...
19:39:10.992 ALSA connection change.
19:39:11.192 MIDI active patchbay scan...
19:39:11.715 ALSA connection graph change.
libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the
oPCR[0] plug for node 0.
LibFreeBoB ERR: Could not do CMP for connection 0
FreeBoB ERR: Could not start streaming threads
DRIVER NT: could not start driver
cannot start driver
19:39:11.793 MIDI active patchbay scan...
19:39:11.795 ALSA connection change.
19:39:31.721 Could not connect to JACK server as client. - Overall
operation failed. - Server communication error. Please check the
messages window for more info.
jackd watchdog: timeout - killing jackd
could not attach as JACK client (server has exited)
19:39:31.918 ALSA connection graph change.
19:39:31.919 JACK was stopped successfully.
19:39:31.919 Post-shutdown script...
19:39:31.920 killall jackd
19:39:31.920 JACK has crashed.
jackd: no process killed
19:39:32.335 Post-shutdown script terminated with exit status=256.
20:27:22.325 MIDI active patchbay scan...
20:27:22.327 ALSA connection change.
20:27:22.528 MIDI active patchbay scan...
What I did + info about my system (ubuntu 8.04):
atte@vestbjerg:~$ uname -r
2.6.24-21-rt
atte@vestbjerg:~$ lsmod | grep 1394
dv1394 20664 0
raw1394 29400 0
ohci1394 34096 1 dv1394
ieee1394 95544 4 dv1394,raw1394,sbp2,ohci1394
atte@vestbjerg:~$ grep disk /etc/udev/rules.d/40-permissions.rules
ATTRS{removable}!="1", GROUP="disk"
KERNEL=="raw1394", GROUP="disk"
ATTRS{type}=="0", GROUP="disk"
atte@vestbjerg:~$ grep disk /etc/group
disk:x:6:atte
This is what dmesg says when plugging the fa-66 in:
[ 3824.579054] ieee1394: Node changed: 0-01:1023 -> 0-00:1023
[ 3824.579064] ieee1394: Node suspended: ID:BUS[0-00:1023]
GUID[0040ab0000c37a87]
[ 3830.249545] ieee1394: Error parsing configrom for node 0-00:1023
[ 3830.249623] ieee1394: Node changed: 0-00:1023 -> 0-01:1023
[ 3831.383625] doh, someone wants to mess with state set
[ 3831.453179] ieee1394: Node resumed: ID:BUS[0-00:1023]
GUID[0040ab0000c37a87]
Besides this, I'm not sure what to look for. Any help appreciated!
--
Atte
http://atte.dk http://modlys.dk
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
)
I'm also a newbie with firewire, but had more success with FFADO, (it is more
current anyway).. I don't have an edirol, but a focusrite saffire pro 10.
Simply install it, fire up ffado-dbus-server run qjackctl and select firewire as
the driver. I am able to get better latency performance with ffado, way better
than freebob but even better than ALSA (under 3ms with 44100 and 48000 khz)...
28 Mar
28 Mar
5:43 a.m.
New subject: firewire newbie in trouble
sonofzev(a)iinet.net.au wrote:
I'm also a newbie with firewire, but had more
success with FFADO, (it is more
current anyway).. I don't have an edirol, but a focusrite saffire pro 10.
Simply install it, fire up ffado-dbus-server run qjackctl and select firewire as
the driver. I am able to get better latency performance with ffado, way better
than freebob but even better than ALSA (under 3ms with 44100 and 48000 khz)...
Ok, sounds like a plan.
The problem is that I get "jackd: unknown driver 'firewire'" when
starting jack, (much) more info follows:
I added the following to /etc/apt/sources.list:
deb http://www.ffado.org/apt gutsy contrib
and installed:
apt-get install libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4
running the ffado-dbus-server seems to work just fine (it should be run
as regular user and left running, right?):
atte@vestbjerg:~$ ffado-dbus-server
-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 1.999.40-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------
00230394308: (ffado-dbus-server.cpp)[ 269] main: Discovering devices...
00230430676: Debug (devicemanager.cpp)[ 332] discover: Starting discovery...
00230517933: Debug (Configuration.cpp)[ 162] showSetting: Group: (null)
00230517986: Debug (Configuration.cpp)[ 184] showSetting: vendorid =
16555 (0x000040AB)
00230518074: Debug (Configuration.cpp)[ 184] showSetting: modelid =
65609 (0x00010049)
00230518088: Debug (Configuration.cpp)[ 208] showSetting: vendorname
= EDIROL
00230518108: Debug (Configuration.cpp)[ 208] showSetting: modelname
= FA-66
00230518125: Debug (Configuration.cpp)[ 184] showSetting: driver = 1
(0x00000001)
00230518149: Debug (Configuration.cpp)[ 208] showSetting: mixer =
EdirolFa66Control
00230518413: Debug (devicemanager.cpp)[ 594] discover: driver found for
device 1
00230542353: Debug (bebob_avdevice.cpp)[ 734] loadFromCache: filename
/home/atte/.ffado/cache/0040ab0000c37a87/0000006005070704.xml
00230560983: Debug (serialize_libxml.cpp)[ 229] checkVersion: Cache
version: 1.999.40-, expected: 1.999.40-.
00230718461: Debug (avc_unit.cpp)[ 489] discoverPlugConnections:
Discovering PCR plug connections...
00230756492: Debug (avc_unit.cpp)[ 500] discoverPlugConnections:
Discovering External plug connections...
00230832189: Debug (bebob_avdevice_subunit.cpp)[ 102]
discoverConnections: Discovering connections...
00230832211: Debug (avc_subunit.cpp)[ 148] discoverConnections:
Discovering connections...
00230832249: Debug (avc_subunit.cpp)[ 148] discoverConnections:
Discovering connections...
00230832284: Debug (bebob_avdevice_subunit.cpp)[ 102]
discoverConnections: Discovering connections...
00230832300: Debug (avc_subunit.cpp)[ 148] discoverConnections:
Discovering connections...
00230832316: Debug (avc_subunit.cpp)[ 148] discoverConnections:
Discovering connections...
00230832389: Debug (bebob_avdevice.cpp)[ 758] loadFromCache: could
create valid bebob driver from
/home/atte/.ffado/cache/0040ab0000c37a87/0000006005070704.xml
00230832416: Debug (bebob_mixer.cpp)[ 126]
addElementForAllFunctionBlocks: Adding elements for functionblocks...
00230834213: Debug (devicemanager.cpp)[ 631] discover: discovery of node
1 on port 0 done...
00230834234: Debug (devicemanager.cpp)[ 639] discover: Discovery finished...
00230834651: Debug (devicemanager.cpp)[1087] showDeviceInfo: =====
Device Manager =====
00230834665: Debug (Element.cpp)[ 121] show: Element DeviceManager
00230834670: Debug (devicemanager.cpp)[1095] showDeviceInfo: ---
IEEE1394 Service 0 ---
Iso handler info:
Dumping IsoHandlerManager Stream handler information...
State: 2
00230834695: Debug (devicemanager.cpp)[1105] showDeviceInfo: --- Device
0 ---
00230834702: Debug (bebob_avdevice.cpp)[ 480] showDevice: Device is a
BeBoB device
00230834732: Debug (ffadodevice.cpp)[ 224] showDevice: Attached to
port.......: 0 (ohci1394)
00230834752: Debug (ffadodevice.cpp)[ 225] showDevice:
Node...................: 1
00230834771: Debug (ffadodevice.cpp)[ 227] showDevice: Vendor
name............: EDIROL
00230834788: Debug (ffadodevice.cpp)[ 229] showDevice: Model
name.............: EDIROL FA-66
00230834800: Debug (ffadodevice.cpp)[ 231] showDevice:
GUID...................: 0040ab0000c37a87
00230834810: Debug (ffadodevice.cpp)[ 236] showDevice: Assigned ID....: dev0
00230834828: Debug (devicemanager.cpp)[1108] showDeviceInfo: Clock sync
sources:
00230834886: Debug (devicemanager.cpp)[1117] showDeviceInfo: Type:
Erratic type , Id: 0, Valid: 1, Active: 0, Locked 1, Slipping: 0,
Description: Device Controlled
00230834937: (ffado-dbus-server.cpp)[ 312] main: Starting DBUS service...
00230847688: (ffado-dbus-server.cpp)[ 328] main: Running... (press
ctrl-c to stop & exit)
00230847752: Debug (ffado-dbus-server.cpp)[ 331] main: dispatching...
However when selecting "firewire" in qjackctl, I get this in qjackctls
"Messages":
<snip>
10:34:55.956 JACK is starting...
10:34:55.957 /usr/bin/jackd -R -P80 -m -dfirewire -dplughw:0 -r48000
-p256 -n3
10:34:55.960 JACK was started with PID=7798.
jackd: unknown driver 'firewire'
10:34:55.966 JACK was stopped with exit status=1.
<snip>
--
Atte
http://atte.dk http://modlys.dk
6:08 a.m.
New subject: firewire newbie in trouble
Atte André Jensen wrote:
<snip>
10:34:55.956 JACK is starting...
10:34:55.957 /usr/bin/jackd -R -P80 -m -dfirewire -dplughw:0 -r48000
-p256 -n3
10:34:55.960 JACK was started with PID=7798.
jackd: unknown driver 'firewire'
10:34:55.966 JACK was stopped with exit status=1.
<snip>
i would guess that you are using a self-compiled version of jack, and
you compiled it *before* you installed the ffado-devel package, hence,
no ffado support was built.
11:39 a.m.
New subject: firewire newbie in trouble
Jörn Nettingsmeier wrote:
i would guess that you are using a self-compiled
version of jack, and
you compiled it *before* you installed the ffado-devel package, hence,
no ffado support was built.
Nope, jack from repos:
atte@vestbjerg:~$ jackd --version
jackd version 0.109.2 tmpdir /dev/shm protocol 22
--
Atte
http://atte.dk http://modlys.dk
11:55 a.m.
New subject: firewire newbie in trouble
Atte André Jensen wrote:
Nope, jack from repos:
atte@vestbjerg:~$ jackd --version
jackd version 0.109.2 tmpdir /dev/shm protocol 22
Some distro's don't compile with FFADO support by default. You may need to
compile JACK from source and enable FFADO.
-gabriel
11:57 a.m.
New subject: firewire newbie in trouble
Gabriel M. Beddingfield wrote:
Atte André Jensen wrote:
If I'm right, 64studio 3.0 supports FFADO (don't know if it is in beta
already)
Nope, jack from repos:
atte@vestbjerg:~$ jackd --version
jackd version 0.109.2 tmpdir /dev/shm protocol 22
Some distro's don't compile with FFADO support by default. You may need to
compile JACK from source and enable FFADO.
12:20 p.m.
New subject: firewire newbie in trouble
Gabriel M. Beddingfield wrote:
Some distro's don't compile with FFADO support
by default. You may need to
compile JACK from source and enable FFADO.
Any way of finding out about weather that's the case before I tear my
system apart?
Should/could I keep my original jack installation? Could I install in
parallel and just use the compiled version?
The following packages will be REMOVED:
jackd qjackctl supercollider supercollider-emacs supercollider-gedit
supercollider-server
If I remove jack it seems I need to compile supercollider by hand. Would
the old binary from-repo supercollider work with a compiled-by-hand
jack? In general can anything be said about if software from the repo
(expecting the jackd from the repos) would work with my compiled-by-hand
jack?
--
Atte
http://atte.dk http://modlys.dk
12:45 p.m.
New subject: firewire newbie in trouble
Atte André Jensen wrote:
$ jackd --help
[snip]
-d backend [ ... backend args ... ]
The backend can be `alsa', `coreaudio', `dummy',
`freebob', `oss', `sun', or `portaudio'.
$ jackd -d freebob
jackd: unknown driver 'freebob'
$ jackd -d firewire
jackd: unknown driver 'firewire'
$ jackd -d ffado
jackd: unknown driver 'ffado'
I don't have it on *my* system. If you get the same... then neither do you.
Some
distro's don't compile with FFADO support by default. You may need to
compile JACK from source and enable FFADO.
Any way of finding out about weather that's the case before I tear my
system apart? Should/could I keep my original jack installation?
Could I install in
parallel and just use the compiled version?
The JACK devs say that you should LEAVE your jack package in-tact and overwrite it.
$ tar xzf jack-audio-connection-kit-0.116.1.tar.gz
$ cd jack-audio-connection-kit-0.116.1
$ ./configure --prefix=/usr
### MAKE SURE IT ENABLED FFADO OR FREEBOB... whichever one you want.
$ make
$ sudo make install
To do it without overwriting the distro's package (using --prefix=/usr/local) is
a little more involved, and if I tell you to do that I may receive unbearable
scorn from Paul Davis (the lead JACK dev).
Peace,
Gabriel
29 Mar
29 Mar
3:58 a.m.
New subject: firewire newbie in trouble
Gabriel M. Beddingfield wrote:
The JACK devs say that you should LEAVE your jack
package in-tact and overwrite it.
$ tar xzf jack-audio-connection-kit-0.116.1.tar.gz
$ cd jack-audio-connection-kit-0.116.1
$ ./configure --prefix=/usr
### MAKE SURE IT ENABLED FFADO OR FREEBOB... whichever one you want.
jack-audio-connection-kit 0.116.2 :
| Build with ALSA support............................... : true
| Build with old FireWire (FreeBob) support............. : false
| Build with new FireWire (FFADO) support............... : true
| Build with OSS support................................ : true
| Build with Sun audio support.......................... : false
| Build with CoreAudio support.......................... : false
| Build with PortAudio support.......................... : false
| Build with NetJack support............................ : true
| Build with Celt support............................... : false
| Build with dynamic buffer size support................ : yes
| Compiler optimization flags........................... : -g
| Compiler full flags................................... :
-I$(top_srcdir)/config -I$(top_srcdir) -I$(top_srcdir) -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS -Wall -g
| Install dir for libjack + backends.................... :
${exec_prefix}/lib/jack
|
| Default driver backend................................ : "alsa"
| Shared memory interface............................... : "System V"
| IPC Temporary directory............................... : /dev/shm
| Install prefix........................................ : /usr
| Default tmp dir....................................... : /dev/shm
It (kind of) works. However even at a setting of buffer size 512 (34ms
latency), my chuck system stutters (~.2 secs audio, ~1 sec silence).
Also EnergyXT doesn't seen to output any sound at all. A simple test
tone in supercollider seem to work though.
Basically very flaky and useless. What can I do?
--
Atte
http://atte.dk http://modlys.dk
30 Mar
30 Mar
2:44 a.m.
New subject: firewire newbie in trouble
Atte André Jensen wrote:
jack-audio-connection-kit 0.116.2 :
| Compiler optimization flags........................... : -g
this is profiling support iiuc. you might want to optimize
(--enable-optimize iirc). same goes for ffado (scons -h will give you
the available options).
It (kind of) works. However even at a setting of
buffer size 512 (34ms
latency), my chuck system stutters (~.2 secs audio, ~1 sec silence).
Also EnergyXT doesn't seen to output any sound at all. A simple test
tone in supercollider seem to work though.
Basically very flaky and useless. What can I do?
post your jackd commandline. are you using -R? with some firewire
devices, it's pretty much mandatory. also, post "cat /proc/interrupts".
also, which firewire controller do you have? (lspci might help.)
best,
jörn
5511
days inactive
5514
days old
linux-audio-user@lists.linuxaudio.org
9 comments
5 participants
participants (5)
-
Atte André Jensen -
Gabriel M. Beddingfield -
Grammostola Rosea -
Jörn Nettingsmeier -
sonofzev＠iinet.net.au