14 Oct
2010
14 Oct
'10
8:59 p.m.
Hi
I would like to get my echo audiofire 2 working on Debian testing,
Thinkpad T61. It;s fully supported according to ffado, but I have some
issues.
When I start the ffado-mixer I get:
00718932192: (ffado-dbus-server.cpp)[ 270] main: Discovering devices...
00718957076: Fatal (devicemanager.cpp)[ 191] initialize: No firewire
adapters (ports) found.
00718957285: Error (ffado-dbus-server.cpp)[ 277] main: Could not
initialize device manager
00718957465: Debug (ffado-dbus-server.cpp)[ 202] exitfunction: Debug
output flushed...
no message buffer overruns
Also: 20:53:32 logginghandler: Could not communicate with the FFADO
DBus service...
/etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Kernel: *32, debian testing
$ aptitude search ffado
i ffado-dbus-server
- FFADO D-Bus server
i ffado-mixer-qt4
- FFADO D-Bus mixer applets (QT4)
i ffado-tools
- FFADO debugging and firmware tools
i libffado-dev
- FFADO API - development files
i A libffado2
- FFADO API
$ aptitude search jackd
i A jackd
- JACK Audio Connection Kit (default
server package)
v jackd-firewire
-
p jackd1
- JACK Audio Connection Kit (server and
example clients)
p jackd1-firewire
- JACK Audio Connection Kit (FFADO
backend)
i jackd2
- JACK Audio Connection Kit (server and
example clients)
i A jackd2-firewire
- JACK Audio Connection Kit (FFADO and
FreeBoB backends)
i A libjack-jackd2-0
- JACK Audio Connection Kit (libraries)
i libjack-jackd2-dev
- JACK Audio Connection Kit
(development files)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15 Oct
15 Oct
8:29 a.m.
rosea grammostola wrote:
00718957076: Fatal (devicemanager.cpp)[ 191]
initialize: No firewire adapters (ports) found.
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
It looks as if your kernel uses the new FireWire stack, but
libraw1394 is still configured to look for the old one.
(This is why your Debian is called "testing".)
See <http://ieee1394.wiki.kernel.org/index.php/Juju_Migration>.
Regards,
Clemens
10:58 a.m.
On Fri, Oct 15, 2010 at 8:31 AM, Clemens Ladisch <clemens(a)ladisch.de> wrote:
rosea grammostola wrote:
Hmm, what do you recommend me?
@Harry, which distro and kernel do you use with the audiofire 2?
Other people with experience with this device?
Kind regards,
\r
00718957076: Fatal (devicemanager.cpp)[ 191]
initialize: No firewire adapters (ports) found.
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
It looks as if your kernel uses the new FireWire stack, but
libraw1394 is still configured to look for the old one.
(This is why your Debian is called "testing".)
See <http://ieee1394.wiki.kernel.org/index.php/Juju_Migration>. 
11:13 a.m.
On 10/14/2010 08:59 PM, rosea grammostola wrote:
/etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
Best,
Jeremy
11:59 a.m.
On Fri, Oct 15, 2010 at 11:13 AM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
On 10/14/2010 08:59 PM, rosea grammostola wrote:
I did remove that, right.
I use ffado from svn.
I could start it once pretty ok, even played a little with yoshimi,
but then jackd died and couldn't get it up again.
Regards,
\r
/etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
12:06 p.m.
On Fri, Oct 15, 2010 at 11:59 AM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On Fri, Oct 15, 2010 at 11:13 AM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
I have it working @window XP and Reaper now, so it seems the hardware is ok.
\r
On 10/14/2010 08:59 PM, rosea grammostola wrote:
I did remove that, right.
I use ffado from svn.
I could start it once pretty ok, even played a little with yoshimi,
but then jackd died and couldn't get it up again.
/etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
12:31 p.m.
On 10/15/2010 11:59 AM, rosea grammostola wrote:
On Fri, Oct 15, 2010 at 11:13 AM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
What does jackd output if you start it?
Best,
Jeremy
On 10/14/2010 08:59 PM, rosea grammostola wrote:
I did remove that, right.
I use ffado from svn.
I could start it once pretty ok, even played a little with yoshimi,
but then jackd died and couldn't get it up again.
Regards,
\r /etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
12:47 p.m.
On Fri, Oct 15, 2010 at 12:31 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
On 10/15/2010 11:59 AM, rosea grammostola wrote:
Again, I got it runnin for a while, but when it died, I can't get JACK up again:
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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 server starting in realtime mode with priority 10
00907922154: (ffado.cpp)[ 92] ffado_streaming_init: libffado
2.999.0-1913 built Oct 15 2010 00:12:04
12:40:44.977 ALSA connection change.
12:40:44.979 ALSA connection graph change.
12:40:47.036 Server configuration saved to "/home/derick/.jackdrc".
12:40:47.041 Statistics reset.
12:40:47.055 Client activated.
12:40:47.082 JACK connection change.
12:40:47.088 JACK connection graph change.
12:41:12.930 XRUN callback (1).
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
12:41:20.380 XRUN callback (2).
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
12:41:23.764 XRUN callback (3).
12:41:28.731 JACK connection graph change.
12:41:28.734 JACK connection change.
12:41:28.777 JACK connection graph change.
12:41:28.989 JACK connection change.
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
12:41:37.925 XRUN callback (4).
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:41:44.517 XRUN callback (5).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:41:48.045 XRUN callback (6).
JackEngine::XRun: client = yoshimi was not run: state = 2
JackAudioDriver::ProcessAsync Process error
12:42:12.569 JACK connection change.
12:42:12.676 JACK connection graph change.
12:42:14.435 JACK connection change.
12:42:14.494 JACK connection graph change.
JackAudioDriver::ProcessAsync: read error, skip cycle
12:42:24.171 XRUN callback (7).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:43:43.688 Statistics reset.
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
12:44:20.351 XRUN callback (1).
JackAudioDriver::ProcessAsync: read error, skip cycle
12:44:25.752 XRUN callback (2).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
jackd: src/libutil/TimestampedBuffer.cpp:1029: void
Util::TimestampedBuffer::incrementFrameCounter(unsigned int,
ffado_timestamp_t): Assertion `nbframes == m_update_period' failed.
12:44:51.744 Shutdown notification.
12:44:51.793 JACK is being forced...
JackSocketClientChannel read fail
12:44:51.845 JACK has crashed.
12:44:51.994 JACK was stopped successfully.
12:44:51.994 Post-shutdown script...
12:44:51.995 killall jackd
jackd: no process found
12:44:52.402 Post-shutdown script terminated with exit status=256.
12:45:29.341 Startup script...
12:45:29.342 artsshell -q terminate
Jack server was closed but clients are still allocated, cleanup...
Cleanup client ref = 2
Cannot write socket fd = 15 err = Broken pipe
Cannot write socket fd = 15 err = Broken pipe
Could not read result type = 7
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
jack server is not running or cannot be started
sh: artsshell: not found
12:45:29.744 Startup script terminated with exit status=32512.
12:45:29.744 JACK is starting...
12:45:29.745 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p1024 -n2
12:45:29.766 JACK was started with PID=3535.
no message buffer overruns
no message buffer overruns
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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 server starting in realtime mode with priority 10
01192926381: (ffado.cpp)[ 92] ffado_streaming_init: libffado
2.999.0-1913 built Oct 15 2010 00:12:04
12:45:40.849 Could not connect to JACK server as client. - Overall
operation failed. - Server communication error. Please check the
messages window for more info.
firewire ERR: Could not start streaming threads
Cannot start driver
JackServer::Start() failed with -1
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
Cannot connect to the server
no message buffer overruns
Failed to start server
12:45:41.384 JACK was stopped with exit status=255.
12:45:41.384 Post-shutdown script...
12:45:41.385 killall jackd
jackd: no process found
12:45:41.792 Post-shutdown script terminated with exit status=256.
12:45:45.275 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:45:54.258 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:46:11.914 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
On Fri, Oct 15, 2010 at 11:13 AM, Jeremy
Jongepier
<jeremy(a)autostatic.com> wrote:
What does jackd output if you start it? On 10/14/2010 08:59 PM, rosea grammostola wrote:
I did remove that, right.
I use ffado from svn.
I could start it once pretty ok, even played a little with yoshimi,
but then jackd died and couldn't get it up again.
Regards,
\r /etc/modules
firewire-sbp2
loop
~$ cat /lib/udev/rules.d/50-raw-firewire.rules
KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
1:08 p.m.
On 10/15/2010 12:47 PM, rosea grammostola wrote:
On Fri, Oct 15, 2010 at 12:31 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
You get a lot of xruns, then jackd says no and crashes. If it is
possible to power off/on your FireWire card then try that. Another
option might be to unload and reload the FireWire kernel module. But
first of all you need to get rid of those xruns. Try raising jackd's
prio, it's now running with prio 10 while the default is 50. Did you
lower it yourself? And I don't know what other tweaks you did. As the
co-author of the LinuxMusicians System Configuration wiki I assume you
probably tweaked your system to the max already ;)
Best,
Jeremy
On 10/15/2010 11:59 AM, rosea grammostola wrote:
Again, I got it runnin for a while, but when it died, I can't get JACK up again:
On Fri, Oct 15, 2010 at 11:13 AM, Jeremy
Jongepier
<jeremy(a)autostatic.com> wrote:
What does jackd output if you start it? On 10/14/2010 08:59 PM, rosea grammostola wrote:
> /etc/modules
>
> firewire-sbp2
> loop
>
> ~$ cat /lib/udev/rules.d/50-raw-firewire.rules
> KERNEL=="raw1394", GROUP="audio"
Hello,
According to /etc/modules you're using the new stack so the udev rule is
not necessary anymore afaik. Which version of FFADO are you using? You
need 2.0.1 in order to be able to use the new FireWire stack.
I did remove that, right.
I use ffado from svn.
I could start it once pretty ok, even played a little with yoshimi,
but then jackd died and couldn't get it up again.
Regards,
\r
1:16 p.m.
On Fri, Oct 15, 2010 at 1:10 PM, Jeremy Jongepier <jeremy(a)autostatic.com> wrote:
On 10/15/2010 01:08 PM, Jeremy Jongepier wrote:
I see myself more as a communicator between the real experts and the n00bs ;)
Afaik, 10 is default and is good (I recall a conversation on IRC with
an expert).
So far so good!
Thanks.
\r
Try raising jackd's
prio, it's now running with prio 10 while the default is 50.
I'm not sure about this, but at least on my machines default prio is 50
afaik.
1:25 p.m.
On 10/15/2010 01:16 PM, rosea grammostola wrote:
On Fri, Oct 15, 2010 at 1:10 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
Checked the default prio, it's 10. I mixed up the rtprio and prio
columns of the ps -eLo pid,cls,rtprio,pri,nice,cmd command :$
So the information on Florian Paul Schmidt's site is outdated?
http://tapas.affenbande.org/wordpress/?page_id=40
Best,
Jeremy
On 10/15/2010 01:08 PM, Jeremy Jongepier wrote:
I see myself more as a communicator between the real experts and the n00bs ;)
Afaik, 10 is default and is good (I recall a conversation on IRC with
an expert).
Try raising jackd's
prio, it's now running with prio 10 while the default is 50.
I'm not sure about this, but at least on my machines default prio is 50
afaik. 
3:25 p.m.
On Fri, Oct 15, 2010 at 01:25:23PM +0200, Jeremy Jongepier wrote:
On 10/15/2010 01:16 PM, rosea grammostola wrote:
why is it outdated ?
you seem to be mixing up some different default priorities.
default priorities of threaded irqs.
default jack1 priorities.
default jack2 priorities.
the priority the threaded soundcard irq is running at...
--
torben Hohn
On Fri, Oct 15, 2010 at 1:10 PM, Jeremy Jongepier
<jeremy(a)autostatic.com> wrote:
Checked the default prio, it's 10. I mixed up the rtprio and prio
columns of the ps -eLo pid,cls,rtprio,pri,nice,cmd command :$
So the information on Florian Paul Schmidt's site is outdated?
http://tapas.affenbande.org/wordpress/?page_id=40 On 10/15/2010 01:08 PM, Jeremy Jongepier wrote:
I see myself more as a communicator between the real experts and the n00bs ;)
Afaik, 10 is default and is good (I recall a conversation on IRC with
an expert).
Try raising jackd's
prio, it's now running with prio 10 while the default is 50.
I'm not sure about this, but at least on my machines default prio is 50
afaik.
3:46 p.m.
Hi,
It seems to work pretty ok now (using jackd in shell with patchage).
Also with midi. On the new firewire stack, latest ffado from svn.
Thanks for the support!
Best regards,
\r
9:22 p.m.
On Fri, Oct 15, 2010 at 3:46 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Hi,
It seems to work pretty ok now (using jackd in shell with patchage).
Also with midi. On the new firewire stack, latest ffado from svn.
My midi keyboard usb works. But my midi device (echo audiofire)
doesn't show up in patchage. Only midi through....
So I seems I can't connect my masterkeyboard midi (non-usb) right now :(
\r
9:50 p.m.
On Fri, Oct 15, 2010 at 9:22 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On Fri, Oct 15, 2010 at 3:46 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
Looks like a bug: http://subversion.ffado.org/ticket/233
I'll talk with the ffado heroes....
Hi,
It seems to work pretty ok now (using jackd in shell with patchage).
Also with midi. On the new firewire stack, latest ffado from svn.
My midi keyboard usb works. But my midi device (echo audiofire)
doesn't show up in patchage. Only midi through....
So I seems I can't connect my masterkeyboard midi (non-usb) right now :(
16 Oct
16 Oct
4:17 p.m.
On Fri, Oct 15, 2010 at 9:50 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On Fri, Oct 15, 2010 at 9:22 PM, rosea grammostola
<rosea.grammostola(a)gmail.com> wrote:
On the stable ffado svn branch I see the midi devices, but can't get
sound out of it...
Testing on Windows xp gives me the same problem. Usb midi keybd is
working, via MIDI cable not... :/
Breakout cable broke?!?
On Fri, Oct 15, 2010 at 3:46 PM, rosea
grammostola
<rosea.grammostola(a)gmail.com> wrote:
Looks like a bug: http://subversion.ffado.org/ticket/233
I'll talk with the ffado heroes.... Hi,
It seems to work pretty ok now (using jackd in shell with patchage).
Also with midi. On the new firewire stack, latest ffado from svn.
My midi keyboard usb works. But my midi device (echo audiofire)
doesn't show up in patchage. Only midi through....
So I seems I can't connect my masterkeyboard midi (non-usb) right now :(
20 Oct
20 Oct
3:50 p.m.
My midi keyboard usb works. But my midi device (echo
audiofire)
doesn't show up in patchage. Only midi through....
So I seems I can't connect my masterkeyboard midi (non-usb) right now :(
Looks like a bug: http://subversion.ffado.org/ticket/233
I'll talk with the ffado heroes....
3:55 p.m.
rosea grammostola wrote:
Yes (if the breakout cable is plugged in before switching on the device).
FFADO is not a general-purpose driver; the MIDI port will not show up
outside Jack unless a Jack-to-ALSA MIDI bridge is used.
Regards,
Clemens
Breakout cable
broke?!?
Does anyone has this device working via MIDI cable (not usb midi)?
15 Oct
15 Oct
3:52 p.m.
On 10/15/2010 03:25 PM, torbenh wrote:
why is it outdated ?
you seem to be mixing up some different default priorities.
default priorities of threaded irqs.
default jack1 priorities.
default jack2 priorities.
the priority the threaded soundcard irq is running at...
Hello Torben,
I didn't say it is outdated, I only raised the question if it is
outdated. For me the information makes sense, I run jackd at 70 or 69,
depending on other priorities. So I wondered why 10? And if some expert
says 10 is good then why does some other expert recommend to run it with
prio 70?
Or am I really mixing up things?
Best,
Jeremy
1:12 p.m.
ffado-test BusReset, made it able to restart it. It looks better now,
with a little help from Adrian @ #ffado
\r
t does jackd output if you start it?
Again, I got it runnin for a while, but when it died, I can't get JACK up again:
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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 server starting in realtime mode with priority 10
00907922154: (ffado.cpp)[ 92] ffado_streaming_init: libffado
2.999.0-1913 built Oct 15 2010 00:12:04
12:40:44.977 ALSA connection change.
12:40:44.979 ALSA connection graph change.
12:40:47.036 Server configuration saved to "/home/derick/.jackdrc".
12:40:47.041 Statistics reset.
12:40:47.055 Client activated.
12:40:47.082 JACK connection change.
12:40:47.088 JACK connection graph change.
12:41:12.930 XRUN callback (1).
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
12:41:20.380 XRUN callback (2).
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
12:41:23.764 XRUN callback (3).
12:41:28.731 JACK connection graph change.
12:41:28.734 JACK connection change.
12:41:28.777 JACK connection graph change.
12:41:28.989 JACK connection change.
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
12:41:37.925 XRUN callback (4).
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:41:44.517 XRUN callback (5).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:41:48.045 XRUN callback (6).
JackEngine::XRun: client = yoshimi was not run: state = 2
JackAudioDriver::ProcessAsync Process error
12:42:12.569 JACK connection change.
12:42:12.676 JACK connection graph change.
12:42:14.435 JACK connection change.
12:42:14.494 JACK connection graph change.
JackAudioDriver::ProcessAsync: read error, skip cycle
12:42:24.171 XRUN callback (7).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
12:43:43.688 Statistics reset.
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
JackAudioDriver::ProcessAsync: read error, skip cycle
12:44:20.351 XRUN callback (1).
JackAudioDriver::ProcessAsync: read error, skip cycle
12:44:25.752 XRUN callback (2).
JackPosixMutex::Unlock res = 1
JackPosixMutex::Unlock res = 1
jackd: src/libutil/TimestampedBuffer.cpp:1029: void
Util::TimestampedBuffer::incrementFrameCounter(unsigned int,
ffado_timestamp_t): Assertion `nbframes == m_update_period' failed.
12:44:51.744 Shutdown notification.
12:44:51.793 JACK is being forced...
JackSocketClientChannel read fail
12:44:51.845 JACK has crashed.
12:44:51.994 JACK was stopped successfully.
12:44:51.994 Post-shutdown script...
12:44:51.995 killall jackd
jackd: no process found
12:44:52.402 Post-shutdown script terminated with exit status=256.
12:45:29.341 Startup script...
12:45:29.342 artsshell -q terminate
Jack server was closed but clients are still allocated, cleanup...
Cleanup client ref = 2
Cannot write socket fd = 15 err = Broken pipe
Cannot write socket fd = 15 err = Broken pipe
Could not read result type = 7
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
jack server is not running or cannot be started
sh: artsshell: not found
12:45:29.744 Startup script terminated with exit status=32512.
12:45:29.744 JACK is starting...
12:45:29.745 /usr/bin/jackd -dfirewire -dhw:0 -r44100 -p1024 -n2
12:45:29.766 JACK was started with PID=3535.
no message buffer overruns
no message buffer overruns
jackdmp 1.9.6
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2010 Grame.
jackdmp 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 server starting in realtime mode with priority 10
01192926381: (ffado.cpp)[ 92] ffado_streaming_init: libffado
2.999.0-1913 built Oct 15 2010 00:12:04
12:45:40.849 Could not connect to JACK server as client. - Overall
operation failed. - Server communication error. Please check the
messages window for more info.
firewire ERR: Could not start streaming threads
Cannot start driver
JackServer::Start() failed with -1
Cannot connect to server socket err = Connection refused
Cannot connect to server socket
Cannot connect to the server
no message buffer overruns
Failed to start server
12:45:41.384 JACK was stopped with exit status=255.
12:45:41.384 Post-shutdown script...
12:45:41.385 killall jackd
jackd: no process found
12:45:41.792 Post-shutdown script terminated with exit status=256.
12:45:45.275 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:45:54.258 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
12:46:11.914 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
5162
days inactive
5168
days old
linux-audio-user@lists.linuxaudio.org
21 comments
4 participants
participants (4)
-
Clemens Ladisch -
Jeremy Jongepier -
rosea grammostola -
torbenh