• warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.
  • warning: Creating default object from empty value in /home/ffado/ on line 488.

Reverse engineered

MOTU is hostile towards Linux

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

sysex via traveler's midi out


Would you know if the traveler transmits realtime sysex data (to control parameters of an external synth) properly?


Re: sysex via traveler's midi out

To be honest I'm not sure. I would suggest you test it and find out. Having said that, I can see no reason why sysex messages wouldn't work: the traveler transmits all other MIDI data as far as I can tell, and at the level that FFADO works there's really nothing special about sysex messages. The only thing I can think of is that sysex messages tend to be quite long, and perhaps the various rate control buffers in FFADO are not long enough. However, I am reasonably sure that I made them quite large. If it turns out that it doesn't work because of buffer sizes there's no reason we couldn't increase the sizes to suit the larger sysex messages.

Is it as simple as traveler + jack?

Do I understand it right that I shouldn't need to do anything but plug in the traveler and start jack?

It doesn't appear that the traveler is being recognized.

OS XFCE 4.8.0 Remix OS
FFADO 2.0.1
Jack 1.9.8

cat /proc/asound/cards returns only the onboard soundcard for the laptop.
Firewire drives using the same cable show up.

Got my Traveler working on Ubuntu Studio 12.04, but...

When sound plays, ALL of the output LEDs light up green, INCLUDING the S/PDIF and AES output LEDs! Does this mean that my Traveler is putting out audio on every single output or do you think it's just the LEDs being lit? This wouldn't wear the device out would it, putting out that much audio all at once all the time? I was trying to figure out a way of just getting the output LEDs for channels 1 & 2 to light up, or none at all when using "phones". This is how my Traveler behaved in Win 7. Maybe someone else has had this happen with their Traveler in Ubuntu and can advise me please?
I got it running fairly easily. I started QJackCtl first, then after a while I realised I hadn't ran FFADO. The mixer came up for the Traveler, fortunately, then I ran QJackQtl again, changed that one parameter on the top of the far right column in QJackCtl settings or options to "firewire", then changed the output in Audacious to "Jack" and I had sound. I think maybe the lights issue has something to do with how Patchbay in "Jack" is configured, but I don't know how to wire it at the moment...


Re: Got my Traveler working on Ubuntu Studio 12.04 ...

The green output LEDs you speak of indicate that audio of some description is being sent to each respective output socket on the back of the unit. If you are not sending audio to all outputs this does seem a little strange. It is certainly not behaviour that I have seen with my Traveler. Have you checked the outputs to see what audio is being sent there?

I should also pause to ask which Traveler you have - the original or the more recent Mk3 model? Also, could you find out (from your package manager perhaps) which version of ffado is in use on your machine?

Having audio go to all outputs will not wear anything out. However, if it is not the desired outcome then clearly it's something which needs to be fixed. Assuming everything is working correctly, the only way that all output LEDs could be lit in unison is if the same signal was being routed to all of them. This could occur as a result of the built-in mixer's settings or decisions made by software running on the computer. For example, if Audacious (for example) decided to send its audio to all available outputs then all the Traveler's output LEDs would light up. I don't know if Audacious does this - I'm using it as an example for the moment.

Another option is that your particular setup has hit a bug in ffado. While this would be surprising in the case of the original traveler (which I have and which has had extensive testing) it could be the case for the mk3 variant which has had far less testing and which I don't personally own.

Note that the audio streaming functionality provided by jackd/qjackctl is completely separate from the mixer control given by ffado-mixer. You do not need ffado-mixer running in order to run jackd, nor does jackd require ffado-mixer to be running. Certainly at times it is convenient that both be running, but there is no requirement for this.

Thanks for replying so soon.

Thanks for replying so soon. Ok, to answer your questions... I have the Traveler mk2... And I'm running ffado-mixer-qt4 2.0.99+svn2019-1ubuntu1

I think it may be how Jack is configured in the patchbay, but it doesn't give me the option to disconnect individual patches. Every single readable client/output port connection under PulseAudio Jack Sink is patched to writeable client/output port firewire_pcm.... And all my firewire_pcm output port connections are patched to PulseAudio Jack Source. This has to be the problem, right? I just didn't want to mess with it myself yet, so I posted on here.


Re: Thanks for replying so soon.

Thank you for the additional information. The version of FFADO that you are running is fairly old, but it should be fine for driving the original Traveler (for the newer Mark3 variant you'll need something more recent). In any case, from your descriptions I think jackd/ffado is running just fine with your interface as far as audio streaming goes.

Based on your patchbay description, I agree that it's the patchbay that's the problem. It sounds like the output from PulseAudio is patched to every single MOTU output which would totally explain the observation that audio is sent to every MOTU output. This would be something that's set up by the patchbay or some other related program: neither FFADO nor jackd would do this itself. Your best best therefore would be to experiment with the patch bay and see if you can disable this automatic patching. I suspect this will be possible, but since I don't run that software myself I can't point you in a specific direction.

Let us know if you have further questions.

Re: Is it as simple as traveler + jack?

> Do I understand it right that I shouldn't need to do anything but plug in the traveler and start jack?

Theoretically yes, but you (a) need the appropriate software versions, and (b) need to tell jackd to use firewire devices.

Regarding (a), ffado 2.0.1 should be acceptable for the MOTU Traveler so long as it is *not* the mk3 variant. In terms of (b) you will need to include at least the

-d firewire

option to jackd so jackd knows to use firewire devices. The default is to use ALSA devices. For reference, I tend to use the following jackd command line:

jackd -R -P70 -d firewire -p 1024 -n 4

The "-R" and "-P70" options are not required for recent versions of jackd (I'm not sure if jack2 1.9.8 qualifies). Giving "-p 1024 -n 4" is fairly conservative in terms of latency (that is, it results in a fairly high latency) but it's a good place to start. One can always fine-tune things later.

As for the output of /proc/asound/cards, this will only list sound devices driven by ALSA. At present the firewire devices supported by ffado are driven directly by ffado from userspace, so ALSA plays no part at all. In other words, it's normal that your firewire device does not show up in /proc/asound/cards. Note that firewire drives will not show up under /proc/asound/cards but they will show up via other avenues.

To progress (and assuming you're not running a Traveler Mk3), I suggest you try starting jackd with at least the "-d firewire" option as described above. Unfortunately there are a number of reasons why this may not work straight away; we can diagnose things later if this turns out to be the case. If there are problems, probably the first step is to join the ffado-devel mailing list and make contact with me via that list. Begin by posting the exact jackd command you used (including all command line parameters), any error messages you get from jackd along and the output of the ffado-diag command. This information will give us an idea of what to pursue.

If you are running a Traveler Mk3, please contact me via the ffado-devel mailing list. Support for this interface is a work in progress and we can work through the issues easier though the list. Long story short: audio streaming should work for certain device configurations, with others to follow once (a) I have time to add the support and (b) we have someone to test the resulting code. Like other mk3 devices ffado-mixer doesn't yet support the Traveler mk3 but again with time and testers we can remedy that.

MOTU Traveler (old one)

Hi, there!

Firstly, thanks a lot for the FFADO :)

My config:
Linux Mint 10 (ubuntu 10.10)
FFADO v2.0.1
Jackd1 0.118 (tried Jackd2 as well)
Firewire: Agere Systems (FW322 onboard)
+ (Texas Instruments PCI - same probs as with onboard fw port)
Additional: Wineasio 0.9.0

Everything seemed to work fine at first: successful creation of server, ffado mixer works 100% - and I can see moving of sliders on LCD of Traveler, I even heard a sound(background music) from my MOTU when was installing an application through wine, though the duration was about 2 secs!

What happens next I can't get why - after some time Jack terminates the server (why?). Also, server stoped always when I tried to load Cubase (before installing Wineasio, after Wineasio it doesn't close but I can't get any sound from MOTU. Tried Cubase versons 3.1.1 and 5.1 [jack out-2 is not active by some reasons, while jack in 1 and 2, out 1 are active in Cubase 5.1 Device Setup]). Moreover, server stops even if I don't load anything, just staring at it :)

Please tell me if I can give you more info, I hope we can solve the situation, come on I heard the sound once lol ;)

Here is the log from Jack:

22:00:45.075 Patchbay deactivated.
22:00:45.106 Statistics reset.
22:00:45.113 D-BUS: Service not available (org.jackaudio.service aka jackdbus).
22:00:49.481 Startup script...
22:00:49.481 artsshell -q terminate
sh: artsshell: not found
22:00:49.883 Startup script terminated with exit status=32512.
22:00:49.883 JACK is starting...
22:00:49.883 /usr/bin/jackd -r -dfirewire -r44100 -p1024 -n8
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
22:00:49.889 JACK was started with PID=1984.
Cannot create thread 1 Operation not permitted
JACK compiled with System V SHM support.
loading driver ..
Cannot create thread 1 Operation not permitted
SSE2 detected
ERROR: messagebuffer not initialized: 00299975760: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0- built Aug 11 2010 00:17:24
00000000 00 13 04 40 82 22 ff ff - 00 00 15 7a 04 7d 80 00
00000010 0b 00 ff ff bf ff ff bf - 00 00 3d ff fd c1 00 00
00000020 02 ff ff e4 00 00 14 ff - ff f2 ff ff f5 ff ff ea
00000030 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000040 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000050 00 00 00 00 00 00 17 a7 - 04 7e 80 00 0b 00 ff ff
00000060 c8 ff ff c8 00 00 06 ff - fe 10 ff ff d8 ff ff f3
00000070 ff ff e7 00 00 0a ff ff - ee 00 00 01 00 00 00 00
00000080 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000090 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
000000a0 00 00 19 d4 04 7f 80 00 - 0b 00 ff ff c6 ff ff c6
000000b0 00 00 35 ff fe 00 ff ff - e5 ff ff f9 00 00 0d ff
000000c0 ff fb 00 00 0e 00 00 1f - 00 00 00 00 00 00 00 00
000000d0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
000000e0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 20 02
000000f0 04 00 80 00 0b 00 ff ff - bd ff ff bd 00 00 2f ff
00000100 fd b3 ff ff f1 ff ff f1 - 00 00 04 00 00 1d 00 00
00000110 19 ff ff f3 00 00 00 00 - 00 00 00 00 00 00 00 00
00000120 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000130 00 00 00 00 00 00 00 00 - 00 00 22 2e 04 01 80 00
00000140 0b 00 ff ff bc ff ff bc - 00 00 4d ff fd a6 ff ff
00000150 d3 00 00 00 00 00 04 ff - ff fa ff ff ef ff ff fe
00000160 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000170 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000180 00 00 00 00 00 00 24 5b - 04 02 80 00 0b 00 ff ff
00000190 cb ff ff cb 00 00 1e ff - fe 30 00 00 0d ff ff eb
000001a0 00 00 11 00 00 13 00 00 - 03 00 00 07 00 00 00 00
000001b0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
000001c0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
000001d0 00 00 26 89 4c 02 80 00 - 0b 00 ff ff c1 ff ff c1
000001e0 ff ff fb ff fd d2 ff ff - f1 ff ff f9 00 00 07 ff
000001f0 ff e8 00 00 07 ff ff ee - 00 00 00 00 00 00 00 00
00000200 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000210 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 28 b6
00000220 04 04 80 00 0b 00 ff ff - b9 ff ff b9 00 00 32 ff
00000230 fd 93 00 00 1c ff ff e1 - 00 00 0f 00 00 09 ff ff
00000240 f4 ff ff fb 00 00 00 00 - 00 00 00 00 00 00 00 00
00000250 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00000260 00 00 00 00 00 00 00 00 -
22:00:51.931 Server configuration saved to "/home/anna/.jackdrc".
22:00:51.932 Statistics reset.
22:00:51.933 Client activated.
22:00:51.936 JACK connection change.
22:00:51.944 JACK connection graph change.
SSE2 detected
22:01:07.045 Transport start.
22:01:17.064 XRUN callback (1).
22:01:31.190 JACK connection change.
22:01:39.456 JACK connection change.
22:01:42.529 JACK connection change.
22:01:45.015 JACK connection change.
22:01:47.129 JACK connection change.
firewire ERR: wait status < 0! (= -1)
DRIVER NT: could not run driver cycle
22:02:00.638 JACK connection graph change.
*** glibc detected *** /usr/bin/jackd: free(): invalid pointer: 0x0000000000c7e3d0 ***
======= Backtrace: =========
======= Memory map: ========
00400000-00405000 r-xp 00000000 08:01 20450165 /usr/bin/jackd
00604000-00605000 r--p 00004000 08:01 20450165 /usr/bin/jackd
00605000-00606000 rw-p 00005000 08:01 20450165 /usr/bin/jackd
007e8000-00da4000 rw-p 00000000 00:00 0 [heap]
7f4bd2ffe000-7f4bd2fff000 ---p 00000000 00:00 0
7f4bd2fff000-7f4bd37ff000 rw-p 00000000 00:00 0
7f4bd37ff000-7f4bd3800000 ---p 00000000 00:00 0
7f4bd3800000-7f4bd4000000 rw-p 00000000 00:00 0
7f4bd4000000-7f4bd4021000 rw-p 00000000 00:00 0
7f4bd4021000-7f4bd8000000 ---p 00000000 00:00 0
7f4bd813a000-7f4bd813b000 ---p 00000000 00:00 0
7f4bd813b000-7f4bd893b000 rw-p 00000000 00:00 0
7f4bd893b000-7f4bd893c000 ---p 00000000 00:00 0
7f4bd893c000-7f4bd913c000 rw-p 00000000 00:00 0
7f4bd913c000-7f4bd913d000 ---p 00000000 00:00 0
7f4bd913d000-7f4bd993d000 rw-p 00000000 00:00 0
7f4bd993d000-7f4bd993e000 ---p 00000000 00:00 0
7f4bd993e000-7f4bda13e000 rw-p 00000000 00:00 0
7f4bda13e000-7f4bda13f000 ---p 00000000 00:00 0
7f4bda13f000-7f4bda93f000 rw-p 00000000 00:00 0
7f4bda93f000-7f4bda940000 ---p 00000000 00:00 0
7f4bda940000-7f4bdb140000 rw-p 00000000 00:00 0
7f4bdb140000-7f4bdb141000 ---p 00000000 00:00 0
7f4bdb141000-7f4bdb941000 rw-p 00000000 00:00 0
7f4bdb941000-7f4bdb942000 ---p 00000000 00:00 0
7f4bdb942000-7f4bdc142000 rw-p 00000000 00:00 0
7f4bdc142000-7f4bdc14f000 r-xp 00000000 08:01 20451475 /usr/lib/
7f4bdc14f000-7f4bdc34f000 ---p 0000d000 08:01 20451475 /usr/lib/
7f4bdc34f000-7f4bdc350000 r--p 0000d000 08:01 20451475 /usr/lib/
7f4bdc350000-7f4bdc351000 rw-p 0000e000 08:01 20451475 /usr/lib/
7f4bdc351000-7f4bdc35d000 r-xp 00000000 08:01 20451170 /usr/lib/
7f4bdc35d000-7f4bdc55c000 ---p 0000c000 08:01 20451170 /usr/lib/
7f4bdc55c000-7f4bdc55d000 r--p 0000b000 08:01 20451170 /usr/lib/
7f4bdc55d000-7f4bdc55e000 rw-p 0000c000 08:01 20451170 /usr/lib/
7f4bdc55e000-7f4bdc584000 r-xp 00000000 08:01 15728713 /lib/
7f4bdc584000-7f4bdc784000 ---p 00026000 08:01 15728713 /lib/
7f4bdc784000-7f4bdc786000 r--p 00026000 08:01 15728713 /lib/
7f4bdc786000-7f4bdc787000 rw-p 00028000 08:01 15728713 /lib/
7f4bdc787000-7f4bdc860000 r-xp 00000000 08:01 20450015 /usr/lib/
7f4bdc860000-7f4bdca5f000 ---p 000d9000 08:01 20450015 /usr/lib/
7f4bdca5f000-7f4bdca65000 r--p 000d8000 08:01 20450015 /usr/lib/
7f4bdca65000-7f4bdca66000 rw-p 000de000 08:01 20450015 /usr/lib/
7f4bdca66000-7f4bdcd84000 r-xp 00000000 08:01 20448717 /usr/lib/
7f4bdcd84000-7f4bdcf83000 ---p 0031e000 08:01 20448717 /usr/lib/
7f4bdcf83000-7f4bdcf95000 r--p 0031d000 08:01 20448717 /usr/lib/
7f4bdcf95000-7f4bdcfa0000 rw-p 0032f000 08:01 20448717 /usr/lib/
7f4bdcfa0000-7f4bdcfa2000 rw-p 00000000 00:00 0
7f4bdcfa2000-7f4bdcfa7000 r-xp 00000000 08:01 22158552 /usr/lib/jack/
7f4bdcfa7000-7f4bdd1a6000 ---p 00005000 08:01 22158552 /usr/lib/jack/
7f4bdd1a6000-7f4bdd1a7000 r--p 00004000 08:01 22158552 /usr/lib/jack/
7f4bdd1a7000-7f4bdd1a8000 rw-p 00005000 08:01 22158552 /usr/lib/jack/
7f4bdd1a8000-7f4bdd1a9000 ---p 00000000 00:00 0
7f4bdd1a9000-7f4bdd9a9000 rw-p 00000000 00:00 0
7f4bddaaa000-7f4bddbaa000 rw-s 00000000 00:04 1638424 /SYSV00000000 (deleted)
7f4bddbaa000-7f4bddbda000 r-xp 00000000 08:01 15728779 /lib/
7f4bddbda000-7f4bdddd9000 ---p 00030000 08:01 15728779 /lib/
7f4bdddd9000-7f4bdddda000 r--p 0002f000 08:01 15728779 /lib/
7f4bdddda000-7f4bddddb000 rw-p 00030000 08:01 15728779 /lib/
7f4bddddb000-7f4bdddde000 r-xp 00000000 08:01 20450954 /usr/lib/
7f4bdddde000-7f4bddfdd000 ---p 00003000 08:01 20450954 /usr/lib/
7f4bddfdd000-7f4bddfde000 r--p 00002000 08:01 20450954 /usr/lib/
7f4bddfde000-7f4bddfdf000 rw-p 00003000 08:01 20450954 /usr/lib/
7f4bddfdf000-7f4bddff5000 r-xp 00000000 08:01 15728836 /lib/
7f4bddff5000-7f4bde1f5000 ---p 00016000 08:01 15728836 /lib/
7f4bde1f5000-7f4bde1f6000 r--p 00016000 08:01 15728836 /lib/
7f4bde1f6000-7f4bde1f7000 rw-p 00017000 08:01 15728836 /lib/
22:02:00.807 JACK connection change.
22:02:00.808 Shutdown notification.
7f4bde1f7000-7f4bde20c000 r-xp 00000000 08:01 15728720 /li
22:02:00.809 JACK is being forced...
7f4bde20c000-7f4bde40b000 ---p 00015000 08:01 15728720 /lib/
7f4bde40b000-7f4bde40c000 r--p 00014000 08:01 15728720 /lib/
7f4bde40c000-7f4bde40d000 rw-p 00015000 08:01 15728720 /lib/
7f4bde40d000-7f4bde4f5000 r-xp 00000000 08:01 20451552 /usr/lib/
7f4bde4f5000-7f4bde6f4000 ---p 000e8000 08:01 20451552 /usr/lib/
7f4bde6f4000-7f4bde6fc000 r--p 000e7000 08:01 20451552 /usr/lib/
7f4bde6fc000-7f4bde6fe000 rw-p 000ef000 08:01 20451552 /usr/lib/
7f4bde6fe000-7f4bde713000 rw-p 00000000 00:00 0
7f4bde713000-7f4bde7f3000 r-xp 00000000 08:01 15728724 /lib/
7f4bde7f3000-7f4bde9f2000 ---p 000e0000 08:01 15728724 /lib/
7f4bde9f2000-7f4bde9f3000 r--p 000df000 08:01 15728724 /lib/
7f4bde9f3000-7f4bde9f4000 rw-p 000e0000 08:01 15728724 /lib/
7f4bde9f4000-7f4bde9f5000 rw-p 00000000 00:00 0
7f4bde9f5000-7f4bde9f9000 r-xp 00000000 08:01 20451074 /usr/lib/
7f4bde9f9000-7f4bdebf8000 ---p 00004000 08:01 20451074 /usr/lib/
7f4bdebf8000-7f4bdebf9000 r--p 00003000 08:01 20451074 /usr/lib/
7f4bdebf9000-7f4bdebfa000 rw-p 00004000 08:01 20451074 /usr/lib/
7f4bdebfa000-7f4bdebff000 r-xp 00000000 08:01 20451514 /usr/lib/
7f4bdebff000-7f4bdedfe000 ---p 00005000 08:01 20451514 /usr/lib/
7f4bdedfe000-7f4bdedff000 r--p 00004000 08:01 20451514 /usr/lib/
7f4bdedff000-7f4bdee00000 rw-p 00005000 08:01 20451514 /usr/lib/
7f4bdee00000-7f4bdee49000 r-xp 00000000 08:01 20450990 /usr/lib/
7f4bdee49000-7f4bdf049000 ---p 00049000 08:01 20450990 /usr/lib/
7f4bdf049000-7f4bdf04a000 r--p 00049000 08:01 20450990 /usr/lib/
7f4bdf04a000-7f4bdf04b000 rw-p 0004a000 08:01 20450990 /usr/lib/
7f4bdf04b000-7f4bdf04c000 rw-p 00000000 00:00 0
7f4bdf04c000-7f4bdf0a6000 r-xp 00000000 08:01 20450946 /usr/lib/
7f4bdf0a6000-7f4bdf2a6000 ---p 0005a000 08:01 20450946 /usr/lib/
7f4bdf2a6000-7f4bdf2a8000 r--p 0005a000 08:01 20450946 /usr/lib/
7f4bdf2a8000-7f4bdf2aa000 rw-p 0005c000 08:01 20450946 /usr/lib/
7f4bdf2aa000-7f4bdf3ee000 r-xp 00000000 08:01 20448645 /usr/lib/
7f4bdf3ee000-7f4bdf5ed000 ---p 00144000 08:01 20448645 /usr/lib/
7f4bdf5ed000-7f4bdf5f5000 r--p 00143000 08:01 20448645 /usr/lib/
7f4bdf5f5000-7f4bdf5f7000 rw-p 0014b000 08:01 20448645 /usr/lib/
7f4bdf5f7000-7f4bdf5f8000 rw-p 00000000 00:00 0
7f4bdf5f8000-7f4bdf61d000 r-xp 00000000 08:01 20448652 /usr/lib/
7f4bdf61d000-7f4bdf81c000 ---p 00025000 08:01 20448652 /usr/lib/
7f4bdf81c000-7f4bdf81e000 r--p 00024000 08:01 20448652 /usr/lib/
7f4bdf81e000-7f4bdf81f000 rw-p 00026000 08:01 20448652 /usr/lib/
7f4bdf84a000-7f4bdf84b000 ---p 00000000 00:00 0
7f4bdf84b000-7f4be004b000 rw-p 00000000 00:00 0
7f4be004b000-7f4be0084000 rw-s 00000000 00:04 1572886 /SYSV00000000 (deleted)
7f4be0084000-7f4be0085000 ---p 00000000 00:00 0
7f4be0085000-7f4be0885000 rw-p 00000000 00:00 0
7f4be0885000-7f4be09ff000 r-xp 00000000 08:01 15732357 /lib/
7f4be09ff000-7f4be0bfe000 ---p 0017a000 08:01 15732357 /lib/
7f4be0bfe000-7f4be0c02000 r--p 00179000 08:01 15732357 /lib/
7f4be0c02000-7f4be0c03000 rw-p 0017d000 08:01 15732357 /lib/
7f4be0c03000-7f4be0c08000 rw-p 00000000 00:00 0
7f4be0c08000-7f4be0c0a000 r-xp 00000000 08:01 15732373 /lib/
7f4be0c0a000-7f4be0e0a000 ---p 00002000 08:01 15732373 /lib/
7f4be0e0a000-7f4be0e0b000 r--p 00002000 08:01 15732373 /lib/
7f4be0e0b000-7f4be0e0c000 rw-p 00003000 08:01 15732373 /lib/
7f4be0e0c000-7f4be0e24000 r-xp 00000000 08:01 15732359 /lib/
7f4be0e24000-7f4be1023000 ---p 00018000 08:01 15732359 /lib/
7f4be1023000-7f4be1024000 r--p 00017000 08:01 15732359 /lib/
7f4be1024000-7f4be1025000 rw-p 00018000 08:01 15732359 /lib/
7f4be1025000-7f4be1029000 rw-p 00000000 00:00 0
7f4be1029000-7f4be10ab000 r-xp 00000000 08:01 15732364 /lib/
7f4be10ab000-7f4be12aa000 ---p 00082000 08:01 15732364 /lib/
7f4be12aa000-7f4be12ab000 r--p 00081000 08:01 15732364 /lib/
7f4be12ab000-7f4be12ac000 rw-p 00082000 08:01 15732364 /lib/
7f4be12ac000-7f4be12b3000 r-xp 00000000 08:01 15732355 /lib/
7f4be12b3000-7f4be14b2000 ---p 00007000 08:01 15732355 /lib/
7f4be14b2000-7f4be14b3000 r--p 00006000 08:01 15732355 /lib/
7f4be14b3000-7f4be14b4000 rw-p 00007000 08:01 15732355 /lib/
7f4be14b4000-7f4be14d5000 r-xp 00000000 08:01 20450169 /usr/lib/
7f4be14d5000-7f4be16d4000 ---p 00021000 08:01 20450169 /usr/lib/
7f4be16d4000-7f4be16d5000 r--p 00020000 08:01 20450169 /usr/lib/
7f4be16d5000-7f4be16d7000 rw-p 00021000 08:01 20450169 /usr/lib/
7f4be16d7000-7f4be16df000 rw-p 00000000 00:00 0
7f4be16df000-7f4be16ff000 r-xp 00000000 08:01 15732365 /lib/
7f4be17bd000-7f4be17dd000 rw-s 00000000 00:05 6529 /dev/fw1
7f4be17dd000-7f4be18dd000 rw-s 00000000 00:04 1605655 /SYSV00000000 (deleted)
7f4be18dd000-7f4be18e2000 rw-p 00000000 00:00 0
7f4be18f9000-7f4be18fa000 rw-s 00000000 00:04 1671193 /SYSV00000000 (deleted)
7f4be18fa000-7f4be18fc000 rw-s 00000000 00:04 851989 /SYSV00282929 (deleted)
7f4be18fc000-7f4be18ff000 rw-p 00000000 00:00 0
7f4be18ff000-7f4be1900000 r--p 00020000 08:01 15732365 /lib/
7f4be1900000-7f4be1901000 rw-p 00021000 08:01 15732365 /lib/
7f4be1901000-7f4be1902000 rw-p 00000000 00:00 0
7fff007c4000-7fff007e5000 rw-p 00000000 00:00 0 [stack]
7fff007ff000-7fff00800000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
cannot continue execution of the processing graph (Resource temporarily unavailable)
zombified - calling shutdown handler
22:02:01.010 JACK was stopped successfully.
22:02:01.227 Post-shutdown script...
22:02:01.228 killall jackd
22:02:01.228 JACK has crashed.
QProcess: Destroyed while process is still running.
jackd: no process found
22:02:01.633 Post-shutdown script terminated with exit status=256.

Re: MOTU Traveler (old one)


It appears the spam filter decided the original post was no good. I've released it for you. :-)

The symptoms you describe are consistent with scheduling problems - that is, ffado isn't getting to run as often as it needs to. This in turn is usually indicates some sort of configuration problem. Looking at the output you provided I see this:

22:00:49.883 /usr/bin/jackd -r -dfirewire -r44100 -p1024 -n8
jackd 0.118.0
Cannot create thread 1 Operation not permitted
JACK compiled with System V SHM support.
loading driver ..
Cannot create thread 1 Operation not permitted

These two messages indicate that jack was not able to get the realtime scheduling permission which it requires in order to guarantee reliable operation. You might like to have a quick read through, and in particular the section on "realtime scheduling". Let me know if you need additional guidance here.

Finally, the guff at the end which starts with

*** glibc detected *** /usr/bin/jackd: free(): invalid pointer: 0x0000000000c7e3d0 ***

occurs because for some reason ffado doesn't exit cleanly on some systems. The underlying cause is not presently known. I can trigger it on my development system if both libffado and its precursor (libfreebob) are installed at the same time but I'm not sure that's not just a symptom. I would be interested to see the result of "ls -l /usr/local/lib/jack/" if you could post it for me.

MOTU Traveler


I got a problem with my MOTU Traveler.I'm trying to get it working for about half a year but didn't ever succeed.I am still a noob on Linux and havn't understood anything about how to set it up.The first question is which programs do i have to start first?Jackctrl?or ffado?or something else?how do i have to configure the programs?Basically how can i check if the firewire port is working?I need a really detailed tutorial but didn't find one anywhere!I sent an email to the MOTU support but havn't got any answer.Please help me doing this, i don't wanna have to get back to windows!


Re: MOTU Traveler

There isn't anything overly special about the MOTU Traveler (or any of the other MOTU interfaces which work with ffado). One simply follows the standard FFADO installation instructions. Once everything is in place, your MOTU Traveler should just work in the same way that any of the other supported interfaces do.

From the outset I should tell you that you won't get any information from MOTU. If they bother to reply to you at all it'll only be to say that they don't support Linux. The support in FFADO for MOTU interfaces was programmed without any assistance from MOTU at all. MOTU are, in general, hostile towards Linux.

It's unclear from your original post precisely what is being asked here. If you're asking for detailed instructions for your particular Linux distribution then your best bet may be to post a request to the ffado-users mailing list. This way you maximise the chances of someone with your Linux distribution seeing your question and being able to provide information from their first-hand experience. While I can provide general advice, I almost certainly don't run the same distribution as you and therefore can't give a lot of detailed information.

In the first instance though we really need to know what Linux distribution you are running and the version - eg: Fedora, Debian, Ubuntu, SUSE, Gentoo, etc etc. Some distributions will already have ffado available automatically while others will require that you install it yourself. This is part of the reason why we need to know these sorts of details about your system.

To directly address some of your questions, the program you ultimately need to start is jackd. This sets up a "server" which provides audio channels to and from hardware interfaces. FFADO is a library which allows programs (of which jackd is an example) to access firewire audio interfaces. So Jackd uses FFADO to access firewire audio interfaces such as the Traveler. In terms of getting audio in and out of the device there's no FFADO-specific program you need to run - jackd takes care of all that.

Qjackctrl is a GUI program for controlling jack. If you don't use qjackctrl you'll have to start jackd from the command line. In general qjackctrl is a much nicer way of interacting with jackd and for newcomers I think it's the recommended way.

Once jackd is running you can use the interface by starting any audio program which supports jack audio - Ardour, ecasound, jack_capture (command line only) and so forth. An incomplete list of jack software can be found on the jack project website at

As far as configuration goes there's not a great deal to set up. jackd (and ffado) automatically configure themselves according to the audio devices they discover to be available.

You asked about checking to see if your firewire device is functional. The easiest way I know of is to start with your interface turned off. Open a shell window and then turn on your device (the Traveler in your case). Wait a few seconds and then run the "mesg" command. At the bottom of this output you should see some lines mentioning "1394", GUIDs, possibly "bus reset", ConfigROM and other things. These messages were generated in response to your Traveler announcing its existance on the Firewire bus. If these messages appear you know that your firewire hardware is working as expected. From here one can proceed to work with jackd / ffado, confident that at least the hardware is in order.

There is some generalised FFADO installation information available starting at If you haven't previously had a look through that site I suggest you do so - there might be enough there to get you started. Certainly if your distribution already includes FFADO it'll make things a lot easier since you won't have to do any installation work. However, it should be noted that for operation with MOTU devices you want to ensure that you have FFADO 2.0beta2 or the FFADO 2.0.0 release. FFADO 2.0.0 was released fairly recently and many distributions haven't yet packaged it for their users. Several others still have 2.0beta1 (they never moved to beta2, planning to skip directly to 2.0.0 once it was out), but unfortunately a last minute change in a higher level component of FFADO meant that MOTU interfaces don't work very well with 2.0beta1.

That's about as much information I can give you at this stage. If you can provide the additional information about your system I mentioned above it would help me (and others) provide more targetted assistance.

motu traveler linux driver ?

I've allready bought (3 years ago) a motu traveler. Is it possible to find any linux driver for it. As I'm almost in the big jump to change for Linux system.
Cheers !

Re: motu traveler linux driver ?

The MOTU driver in FFADO works with the Traveler (the Traveler is in fact the interface I develop the driver against). Try 2.0-rc2 or later (2.0-rc1 had a bug which broke the MOTU functionality). All device functions are confirmed to work with the exception of SMTPE sync (I don't have suitable sync sources to test this mode with).

what is the known working setup?

i bought the traveler specifically because it was listed here as "supported" but it has been difficult to get going. can you help me out with a pointer to what i should read?

also. what firewire card are you using? what's the chipset on the card? what features are supported?

-- karl

Re: what is the known working setup?

There are installation documents available on the website. See the "user documentation" section of Installation should be made easier once we release version 2.0 (due "soon") since the distributions will pick it up as part of their standard package set. If you have further questions or encounter problems the best bet is to post to the ffado-users mailing list in the first instance.

As to what firewire card to use, I personally use one based on the TI (Texas Instruments) chipset. Across all operating systems these are regarded as among the most reliable. Cards/interfaces based on other chipsets do not always work well due to hardware issues in those chips. We have started to compile a list of working and non-working chipsets in the "HostControllers" document, linked in the afore-mentioned "user documentation" collection.

As far as which Traveler features are supported, the short answer is "all of them except SMTPE sync". I don't have any SMTPE sources so I can't test/debug this mode of operation.

Function supported ?

I don't know if is here who I can write that but I try :-)
I want buy Motu traveler but I want know if all functions of traveler are supported by linux driver ?
I think it's a good idea to have this details on your web site (for all interfaces) :-)

Re: Function supported ?

All functions of the Traveler are supported as far as I know, except for SMTPE sync. I don't have any SMTPE sources so I can't test or debug this mode of operation.

However, if you are contemplating the purchase of an interface for use with Linux could I strongly encourage you to purchase from one of the vendors who have actively supported the project through the provision of resources like sample devices or device documentation. As is noted in the Traveler device entry, MOTU themselves have been hostile to the Linux driver effort for their devices and as a result I could not recommend you purchase from them if use under Linux is the motivation for your purchase.

Vendors to consider would be the likes of Echo Audio, Edirol, Focusrite, ESI (certain devices), Mackie (certain devices) and TerraTec. Basically look at the supported device list ( and identify those devices listed as having "Full support".

Don't forget to write to MOTU to tell them why you didn't purchase from them, and feel free to write to your vendor of choice to let them know that their support of Linux / FFADO was a significant consideration when you made your purchase decision too.