FA-66

Support Status: 
Full Support
Manufacturer: 
Edirol
Platform: 

Comments

Mine is working perfectly on my asus (A6KmQ007H) with the 64Studio 1.4.0 (http://64studio.com/) installed.
Nothing to configure (ffado/freebob already included), JACK runs with no XRuns with Ardour2.
Just one thing to work on is the bus powered feature

Please note that bus power is not a software feature. There is nothing we can do about it. Either your FireWire port provides power or it doesn't.

Laptop FireWire ports don't supply power, not even if they are 6-pin connectors on a cardbus or expresscard card. Both cardbus and expresscard don't have access to pins that can supply the required power.

The only exception on this are the Apple laptops that have a 6-pin FireWire plug built in. These plugs can supply a limited, but sufficient amount of power.

So to summarize: it's not a FFADO thing, it's a hardware issue.

hello
i have this audio device. my question maybe is not ffado related because is about the firewire cable (sorry if this does not fit here): anyone managed to succesfuly connect with a 6pin or 9 pin cable? im only able to use this device with the 4pin cable (in both windows and linux)
thanks

I am a little confused about what the question refers to, so I will answer generally. If this does not answer your question please provide further information so we might help you.

For firewire-400 (the most common type) there are two plug options: 6 pin and 4 pin. The 6 pin variety are usually found on desktop computers while the 4-pin alternative is normally used only on laptops (the argument being one of size, although it's debatable whether it's truly valid). Anyway, both plugs carry the full firewire-400 bus, so in terms of connection there is no difference between the two.

The two extra pins in the 6-pin plug are used to carry "bus power" to the device. That is, they are used to connect power from the computer to the device. While some devices require too much power to be powered this way, there are many small devices for which this is very convenient. On devices which can run on bus power, the use of a 6-pin cable means you don't need a separate power supply for the device.

If a 4-pin cable is used instead (or more specifically, any cable where at least one end is fitted with a 4-pin plug), there is no provision in the cable for bus power. In this case the device must be powered with a separate power supply. Otherwise the device will remain off since it is not receiving any power.

Given this I am puzzled as to why your device only works with a 4-pin firewire cable. As above, there is no difference from the bus's point of view between a 4-pin and 6-pin cable. If your device works with a 4-pin cable then it must have an external power supply and I would expect it to work just as well with the 6-pin cable (the device would just ignore bus power in this case, since it's getting power from elsewhere).

The 9-pin firewire plug is only used by devices and cards which support the firewire-800 standard, a later version of firewire which doubled the potential throughput of the firewire-400 interface. A firewire-800 cable will not fit into a firewire-400 socket; to connect a firewire-400 device (such as the FA-66) to a firewire-800 socket you would need a 6-pin to 9-pin cable. Since Firewire-800 is backwards compatible with firewire-400 I believe such a cable is technically feasible; I haven't personally seen any but then again I haven't gone out of my way to look for them either. In any case, if a device works with a 6-pin cable into a firewire-400 interface it should be fine when run into a firewire-800 via a suitable cable.

Returning to your original question, it is my understanding that many people have successfully used the FA-66 with a 6-pin cable. As explained above, given the information to hand I can't understand why yours doesn't, while a 4-pin cable is fine.

hi.
thanks for your description. i noticed that the 4 pin cable is from another brand. seems to be better quality cable, with gold connections. the cables that just does not work are generic cables, that came included with the box.
so, i can conclude that the issue is caused by bad cables.

now i have the doubt about latency: the lowest i can get is 128 samples buffer (48k Hz sample rate) using the the 4 pin cable that connects with a fw speed of 400. does a full speed of 800 reaches lower latencies?

thanks in advance.
best regards.

Cables can be inconsistent, and appearances are only part of the story. Furthermore, some cables which come with devices are in fact very high quality (for example, those which ship with RME interfaces). However, it's not unreasonable that bundled cables could be sub-optimal. If things continue to work with the 4-pin cable then that would tend to prove the point.

Latency generally has nothing to do with the cable: if the cable is good then the firewire link will work. The latency you can achieve is dependent on a whole bunch of things, including but not limited to: the speed of your computer, the firewire controller you are using, other programs running on your computer, the presence of binary kernel modules (eg: for Nvidia hardware) the way hardware interrupts are routed within your computer and of course the interface itself (some are better than others). Tuning for low latency is a whole separate topic within itself, but basically it boils down to trying things and seeing if they work.

Depending on what is limiting your latency, the possibility of running the firewire bus at a higher speed may or may not help. However, with the FA-66 that is not an option. The FA-66 is a Firewire-400 device, so no matter what you do it will not run any faster than that. There aren't too many Firewire-800 devices around (and even fewer Firewire-800 controllers) - the RME Fireface-800 is the only one I'm aware of off the top of my head. But anyway, regardless of that the FA-66 won't run faster than 400 Mbps so to improve your latency you have to look elsewhere.

You mention that you could run with 128 samples per buffer; how many buffers were you running with (normally this is given with the "-n" option on the jackd command line)? 2 or 3 are numbers which seem fairly common, so this gives a latency of somewhere between 256 and 384 samples at 48000 Hz - or around 6 ms. That's actually not too bad - most people would struggle to detect that. But if you want to pursue even lower latency, the first thing you'll have to do is work out what is limiting your system to 128 samples per buffer. So, run jackd with 64 samples per buffer and let us know what happens (that is, how does the device behave and what error message - if any - are displayed. To get anything meaningful you may need to add a "-v X" parameter to the jackd command line after the "-d firewire" (where X is a number between 1 and 6, with 1 being the most terse messages and 6 displaying a *lot* of debug output).

The command ffado-diag can also be run to list the important details about your machine. The most important sections for the purposes of this exercise would be the description of your firewire card, the interrupt details and the kernel version. Ideally you would find your firewire card being the only one to use a particular interrupt, you'd have a recent kernel (say 2.6.39 or later), libraw1394 version 2.0.6 or later and no proprietory closed-source kernel modules loaded. Also, a firewire card based on a TI (Texas Instruments) chipset is generally regarded as ideal although there are others which work well enough (eg: very recent VIAs, some Ricohs, etc).

I had exactly the same issue and after hours of tweaking, realised it was a bad cable...

Richard Rutter

FA-66 is working fine on Ubuntu Studio 7.10. Had problems until I obtained a SIIG PC bus card (TI Chipset) FireWire card for my laptop [previous/older "ALi" chipset based card I'd had onhand wouldn't even work with Windoze].

My first recording test w/ 2 microphones worked well (live family music event).

Problem: Digital I/O: Using Ardour (2.05 / 2234) I'm trying to record output from a DAT (Sony DTC-A6) to FA-66 and if I use the S/PDIF digital I/O, I get noise on the recording [but good levels]. If I use the Analog I/O (RCA on DAT to RCA on FA-66], I get lower levels but good clean sound. I think I saw a post related to this somewhere -- that the Digital I/O was problematic with freebob and/or ffado.

Any thoughts?

--Jed--

To record from an S/PDIF signal source you should make sure that the clock source and samplerate are set correctly. If that ok, then there should be no issue with digital input. Does the device's external sync led indicate correct sync? Make sure you power off the device after switching these settings (as indicated in the manual).

Regarding the non-working FireWire card: If you don't have a use for it, you might want to consider donating it to us. That way we can try and make it work. If it is an external card of course. Since you mention ALi I suspect it is built in though.

hi there
I've switched from windows to ubuntu some days ago for reasons we all know. fortunately most devices work properly. the only thing i have problems with is my fa-66 firewire audio device. i have read that it works with jack and freebob. aktually, applications that can access jack directly like audacity work. but i would like to route alsa to freebob so that every application like mp3 players can also use the fa-66.
mario.wav
JACK tmpdir identified as [/dev/shm]cd.
Wiedergabe Wave 'mario.wav' : Signed 16 bit Little Endian, Samplingrate: 44100 Hz, Stereo
cannot connect alsa-jack.jackP.25595.0: out_000 to freebob_pcm:dev1p_LineOut
aplay: pcm_write:1265: Schreibfehler: Input/output error

Edit: Removed the spam-link

Does anyone know if the new Roland/Edirol FA-66 which is now called the "Cakewalk FA-66" is still a fully supported device in FFADO? I see that the Edirol FA-66 is supported, but now that the name has changed, has the hardware/firmware/support changed?

Thanks,

Hiya chaps...

Been trying to get this to work with linux since i bought it... I bought it solely on the principle that it worked through this as it was fully supported and generally all round awesome...

anyway... I can't for the life of me work out how to install it... I managed a while a go in the past but can't remember now... does it need compiling from source?

also... scons / SConstruct... the readme says to run scons to install but there isn't such a file... I have SConstruct but when i try to run that it doesn't do anything... are the docs up to date?

I really really want this working... as then windows will be removed from my life forever... and I really want that to happen!!!

can anyone point me in the direction of a walkthrough / guide / FAQ on how to do this for fedora... as everything is ubuntu and it's derivatives... many thanks peeps!!

Click the menu-item called "Documentation", find the documentation about installation, find the link to http://subversion.ffado.org/wiki/InstallingFfadoFromSource and do what it says there...

"scons" is an application, not something we ship. Its told what to do via SConstruct/SConscript files which we ship...

But the FA-66 should really work with FFADO-2.0.X shipped from your distribution...

(BTW: I edited out your link, has to much of that spam-smell to have links below posts.)

Had major issues with very frequent XRUNs on Ubuntu 11.04. The XRUNs would typically happen whenever there was a lot of activity on the screen, e.g. playing video, etc. After a lot of testing, I found a working setup which doesn't exhibit this problem.

1. A preemptive kernel was needed. I had success with 2.6.39.1 (CONFIG_PREEMPT=y).
2. Secondly, I had to use a sample rate of 96000. Not sure exactly why, but neither 44100 or 48000 worked and resulted in very frequent XRUNs.

See also: http://subversion.ffado.org/ticket/271#comment:17

Cheers \o/

Hello, I'ved tried installing Edirol Fa-66 in Linux Mint 12 without succes. I fallowed this tutorial:
http://www.audiorecording.me/focusrite-saffire-pro-40-in-ubuntu-11-10-in...

No luck whatsoever, this is what I get when typing:

ffado-dbus-server

-----------------------------------------------
FFADO Control DBUS service
Part of the FFADO project -- www.ffado.org
Version: 2.999.0-
(C) 2008, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
-----------------------------------------------

Discovering devices...
01521840424: Warning (ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min requested (1000000)
01521840495: Warning (ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested (1000000) did not succeed
DBUS service running
press ctrl-c to stop it & exit

Also when I type:

ffado-diag

FFADO diagnostic utility 2.999.0-
============================
(C) 2008 Pieter Palmers
2009-2010 Arnold Krille

=== CHECK ===
Base system...
kernel version............ 3.0.0-12-generic
old 1394 stack present.... False
old 1394 stack loaded..... False
old 1394 stack active..... False
new 1394 stack present.... True
new 1394 stack loaded..... True
new 1394 stack active..... True
/dev/raw1394 node present. False
Prerequisites (dynamic at run-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
g++ ............... sh: g++: not found
PyQt4 (by pyuic4) . sh: pyuic4: not found
jackd ............. jackd version 0.121.0 tmpdir /dev/shm protocol 24
path ............ /usr/bin/jackd
flags ........... Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
flags ........... Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
flags ........... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
dbus-1 ............ Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
flags ........... Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
g++ ............... g++ (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
PyQt4 (by pyuic4) . Python User Interface Compiler 4.8.5 for Qt version 4.7.3
jackd ............. sh: jackd: not found
path ............
flags ........... Package jack was not found in the pkg-config search path.
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
flags ........... Package libavc1394 was not found in the pkg-config search path.
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.34.1
flags ........... -pthread -I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0
dbus-1 ............ 1.4.14
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include -ldbus-1 -lpthread -lrt
Hardware...
Host controllers:
03:05.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

CPU info:
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
CPU socket(s): 1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 5
Stepping: 3
CPU MHz: 800.000
BogoMIPS: 6227.80
Virtualization: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [42, 42, 42, 42], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['i8042']
IRQ 7: PID: None, count: [1, 1, 1, 1], Sched None (priority None), drivers: ['parport0']
IRQ 8: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['acpi']
IRQ 12: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['i8042']
IRQ 14: PID: None, count: [5075, 5075, 5075, 5075], Sched None (priority None), drivers: ['pata_atiixp']
IRQ 15: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['pata_atiixp']
IRQ 16: PID: None, count: [975, 975, 975, 975], Sched None (priority None), drivers: ['ohci_hcd:usb3', 'ohci_hcd:usb4']
IRQ 17: PID: None, count: [7, 7, 7, 7], Sched None (priority None), drivers: ['ehci_hcd:usb1']
IRQ 18: PID: None, count: [160059, 160059, 160059, 160059], Sched None (priority None), drivers: ['ohci_hcd:usb5', 'ohci_hcd:usb6', 'ohci_hcd:usb7', 'nvidia']
IRQ 19: PID: None, count: [35536, 35536, 35536, 35536], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'hda_intel']
IRQ 20: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['firewire_ohci']
IRQ 22: PID: None, count: [9851, 9851, 9851, 9851], Sched None (priority None), drivers: ['ahci']
IRQ 42: PID: None, count: [0, 0, 0, 0], Sched None (priority None), drivers: ['eth0']

Software Interrupts:
--------------------

=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded.
This is still kind of experimental. If you encounter problems, please also check
with the old stack.

ANY help is very much appreciated, thanx!

When running "ffado-dbus-server" you reported the following output:

Discovering devices...
01521840424: Warning (ieee1394service.cpp)[ 375] initialize: Could not set SPLIT_TIMEOUT to min requested (1000000)
01521840495: Warning (ieee1394service.cpp)[ 379] initialize: Set SPLIT_TIMEOUT to min requested (1000000) did not succeed DBUS service running
press ctrl-c to stop it & exit

The two warnings can be ignored in your case: you are running a sufficiently new kernel that there's no need for SPLIT_TIMEOUT to be set by ffado (the attempt is included because for older kernels and a small number of devices it's necessary). Aside from the warnings I don't see anything that indicates that ffado-dbus-server isn't working correctly. While ffado-dbus-server was running, did you try running ffado-mixer? Ffado-mixer uses the dbus interface provided by ffado-dbus-server to provide a mixer/control interface to the device.

Note that audio data is handled by jackd and is independent of ffado-mixer and ffado-dbus-server. You don't need jackd running in order to use ffado-mixer/ffado-dbus-server, or vice versa.

It seems to me that ffado-dbus-server is running correctly for you. What other things have you observed which indicate that things are not working as they should?

Hi, I'm new here, and new to firewire audio on linux. My distrib is Arch Linux.
If I understand right, ffado-dbus-server has to be launched first, then jackd makes the audio interface between applications and the firewire interface?
I'm able to launch the ffado-dbus-server without error, but everything I do afterwards fails, like launching ffado-mixer or jackd. I don't have a real-time kernel, and I honestly don't care, I just want to play music with my computer, not record or make complicated musical things.
Also, the ffado-diag seems to be seriously old and unmaintained since it says it does not support the new FireWire stack, but I've seen on other forums that it's just an irrelevant message...

Jackd2 errors on launch (I also had errors with jackd1):
Tue Jun 5 22:06:30 2012: [1m[31mERROR: firewire MSG: Starting FFADO backend (libffado 2.0.1)[0m
Tue Jun 5 22:06:30 2012: [1m[31mERROR: firewire ERR: Could not start streaming threads[0m
Tue Jun 5 22:06:30 2012: [1m[31mERROR: Cannot start driver[0m
Tue Jun 5 22:06:30 2012: [1m[31mERROR: JackServer::Start() failed with -1[0m
Tue Jun 5 22:06:30 2012: [1m[31mERROR: Failed to start server[0m

ffado-mixer errors:
ERROR:dbus:Failed to get Continuous /org/ffado/Control/DeviceManager/0040ab0000c399c7/Mixer/Feature_Volume_3 on server org.ffado.Control (and so on with other channels)

ffado-dbus-server errors on ffado-mixer launch:
05934151781: Error (avc_avdevice.cpp)[ 289] supportsSamplingFrequency: sample rate not supported by input plug

ffado-test-streaming errors:
libffado 2.0.1 built Apr 30 2012 05:14:11
05974952244: Warning (ffado.cpp)[ 121] ffado_streaming_init: Realtime scheduling is not enabled. This will cause significant reliability issues.
libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] plug for node 0.
05975738095: Error (ieee1394service.cpp)[1210] allocateIsoChannelCMP: Could not do CMP from FFC0:00 to FFC1:-1
05975739105: Error (avc_avdevice.cpp)[ 804] startStreamByIndex: Could not allocate ISO channel for SP 0
05975740164: Warning (devicemanager.cpp)[ 850] startStreamingOnDevice: Could not start stream 0 of device 0x17d6c50
05975741149: Warning (devicemanager.cpp)[ 887] startStreaming: Could not start streaming on device 0x17d6c50!
05975741939: Fatal (ffado.cpp)[ 211] ffado_streaming_start: Could not start the streaming system

Anyone has an idea if the FA-66 is still supported by new versions, or what I missed in the configuration? I don't find a clear HOWTO about how to get firewire audio working.

Hi Vinvin

Based on what's been provided here it's hard to determine what the problem might be. However, I do note that you're using ffado 2.0.1. While that's our last released version, it's also quite old; it's coming up to 2 years old I think. While we're in the process of preparing for the release of version 2.1 that is a while off yet. It may however be worth your while to check out the subversion trunk and see if that might work any better with your device. Compared to 2.0.1 there have been many changes.

Having said that though, it was my understanding the 2.0.1 did work with the FA-66 so it's hard to be sure of what's going on. It might be best to obtain the output from ffado-diag and post that to the ffado-devel mailing list for comments. The other thing you might like to do is to run ffado at an elevated debug level when using jackd. For example: "jackd ... -d firewire -v 3". The "3" could range from 1 up to 7 (although you definitely don't want to go beyond 6). You may get some useful information from that which could point to the source of the problem. Again, this output could be posted to the mailing list for others to look at.

Oh yes, the debug output mentioned above will only be accessible if you've compiled your ffado with "ENABLE_DEBUG=yes" on the scons command line.

One thing I do know about the FA-101 (and I expect the FA-66 is the same) is that the sample rate is selected by a front panel knob. As far as I know there's no software control of the rate, and any attempt to change it will result in an error. What this means is that when starting jackd you need to ensure that the rate requested matches the current setting of the front panel switch.

Hopefully we can get to the bottom of the problem.

I have used my FA-66 in Tango Studio (10:04) without any problems. With a latency of about 2.5 ms. Since TS is a bit boring and old (do not know if it is still alive), I wanted to try a newer distro based on 12.04 or 12.10. I have tried both Ubuntu Studio and Dream Studio, both 32 bit and 64 bit without success. The computer freezes after about a minute when I plug in my FA-66. Or if I start jackd with the sound card connected. It does not help to disconnect the card only a hard reset will start the computer again. One difference I know between Tango Studio and Dream Studio / Ubuntu Studio is that Tango does not use Pulse Audio. But if I uninstall Pulse Audio problem is still there.
OK, my computer is not the latest, but I have no problem using 12.10 64bit when I have my M-Audio Delta 1010 internal card installed.
Has anyone experienced the same problem or have a solution to it?

This is rather interesting. As I understand things from the initial post, it seems that the computer is freezing if the FA-66 is simply plugged into your firewire port even if jackd/ffado is not run. At face value this sounds like it's a bug in the way the kernel is interacting with the firewire host controller. If ffado isn't running then it can't be implicated in the system freeze.

Debugging a problem like this via comment posts here is likely to be rather awkward. There are also only a limited number of people watching these comments. I suggest that you join the ffado-devel or ffado-users mailing list (see the "contact" link on the left of the website) and re-post your issue there. Besides other ffado users, there are some kernel developers who watch that list and they may have helpful suggestions.

When you do this, could you also include the output of "ffado-diag" as produced by your system. This will allow us to know exactly how the system is configured and what hardware is present, which in turn can make debugging easier.

Sorry but I have limited trust in mailing lists so I try here...

This is the ffado-diag of my 12.04 64bit DreamStudio:

studion@studion:~$ ffado diag
ffado: kommandot hittades inte
studion@studion:~$ ffado-diag

FFADO diagnostic utility 2.1.0-
============================
(C) 2008 Pieter Palmers
2009-2010 Arnold Krille

=== CHECK ===
Base system...
kernel version............ 3.2.0-39-lowlatency
Preempt (low latency)... True
RT patched.............. False
old 1394 stack present.... False
old 1394 stack loaded..... False
old 1394 stack active..... False
new 1394 stack present.... True
new 1394 stack loaded..... True
new 1394 stack active..... True
/dev/raw1394 node present. False
/dev/fw* permissions:
crw------- 1 root root 250, 0 apr 5 23:08 /dev/fw0
User IDs:
uid=1000(studion) gid=1000(studion) grupper=1000(studion),4(adm),20(dialout),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),109(lpadmin),126(sambashare)
Prerequisites (dynamic at run-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
g++ ............... sh: 1: g++: not found
PyQt4 (by pyuic4) . sh: 1: pyuic4: not found
jackd ............. no message buffer overruns
path ............ /usr/bin/jackd
flags ........... Package jack was not found in the pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
libraw1394 ........ Package libraw1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libraw1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libraw1394' found
flags ........... Package libraw1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libraw1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libraw1394' found
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
flags ........... Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
libiec61883 ....... Package libiec61883 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libiec61883.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libiec61883' found
flags ........... Package libiec61883 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libiec61883.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libiec61883' found
libxml++-2.6 ...... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
flags ........... Package libxml++-2.6 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml++-2.6.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libxml++-2.6' found
dbus-1 ............ Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
flags ........... Package dbus-1 was not found in the pkg-config search path.
Perhaps you should add the directory containing `dbus-1.pc'
to the PKG_CONFIG_PATH environment variable
No package 'dbus-1' found
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
g++ ............... g++ (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
PyQt4 (by pyuic4) . Python User Interface Compiler 4.9.1 for Qt version 4.8.1
jackd ............. sh: 1: jackd: not found
path ............
flags ........... Package jack was not found in the pkg-config search path.
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
flags ........... Package libavc1394 was not found in the pkg-config search path.
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.34.1
flags ........... -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lglib-2.0
dbus-1 ............ 1.4.18
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -ldbus-1 -lpthread -lrt
uname -a...
Linux studion 3.2.0-39-lowlatency #41-Ubuntu SMP PREEMPT Fri Mar 1 16:18:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Hardware...
Host controllers:
05:05.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

CPU info:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Tråd(ar) per kärna: 1
Core(s) per socket: 2
Socket(s): 1
NUMA-nod(er): 1
Tillverkar-id: AuthenticAMD
Processorfamilj: 15
Modell: 107
Stepping: 1
Processorns MHz: 2099.982
BogoMIPS: 4199.06
Virtualisering: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
NUMA node0 CPU(s): 0,1
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [123, 0], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [38, 23], Sched None (priority None), drivers: ['i8042']
IRQ 6: PID: None, count: [0, 2], Sched None (priority None), drivers: ['floppy']
IRQ 7: PID: None, count: [1, 0], Sched None (priority None), drivers: ['parport0']
IRQ 8: PID: None, count: [0, 0], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [0, 0], Sched None (priority None), drivers: ['acpi']
IRQ 14: PID: None, count: [0, 0], Sched None (priority None), drivers: ['pata_via']
IRQ 15: PID: None, count: [28, 180], Sched None (priority None), drivers: ['pata_via']
IRQ 17: PID: None, count: [0, 642], Sched None (priority None), drivers: ['snd_hda_intel']
IRQ 18: PID: None, count: [0, 4], Sched None (priority None), drivers: ['firewire_ohci']
IRQ 20: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb2']
IRQ 21: PID: None, count: [9528, 7914], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb4', 'sata_via']
IRQ 22: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb3']
IRQ 23: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb5', 'eth0']
IRQ 24: PID: None, count: [827, 198], Sched None (priority None), drivers: ['snd_hda_intel', 'nvidia']

Software Interrupts:
--------------------

=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded.
If running a kernel earlier than 2.6.37 and problems are experienced, either
try with the old Firewire kernel stack or upgrade to a newer kernel
(preferrably 2.6.37 or later).
_________________________________________________________________________________-

This is the ffado-diag from my 10.04 TangoStudio:

studion@studion:~$ ffado diag
ffado: kommandot hittades inte
studion@studion:~$ ffado-diag

FFADO diagnostic utility 2.999.0-
============================
(C) 2008 Pieter Palmers
2009-2010 Arnold Krille

=== CHECK ===
Base system...
kernel version............ 2.6.32-41-lowlatency
old 1394 stack present.... True
old 1394 stack loaded..... True
old 1394 stack active..... True
new 1394 stack present.... True
new 1394 stack loaded..... False
new 1394 stack active..... False
/dev/raw1394 node present. True
/dev/raw1394 permissions.. True
Prerequisites (dynamic at run-time)...
gcc ............... gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
g++ ............... g++ (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
PyQt4 (by pyuic4) . sh: pyuic4: not found
jackd ............. no message buffer overruns
path ............ /usr/bin/jackd
flags ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
flags ........... Package libavc1394 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libavc1394.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libavc1394' found
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.30.0
flags ........... -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0
dbus-1 ............ 1.4.0
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -L/lib -ldbus-1 -lpthread -lrt
Prerequisites (static at compile-time)...
gcc ............... gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
g++ ............... g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3
PyQt4 (by pyuic4) . Python User Interface Compiler 4.7.2 for Qt version 4.6.2
jackd ............. sh: jackd: not found
path ............
flags ........... Package jack was not found in the pkg-config search path.
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ Package libavc1394 was not found in the pkg-config search path.
flags ........... Package libavc1394 was not found in the pkg-config search path.
libiec61883 ....... 1.2.0
flags ........... -liec61883 -lraw1394
libxml++-2.6 ...... 2.30.0
flags ........... -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0
dbus-1 ............ 1.4.0
flags ........... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -L/lib -ldbus-1 -lpthread -lrt
Hardware...
Host controllers:
05:05.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev 80) (prog-if 10)
Subsystem: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
Kernel driver in use: ohci1394
Kernel modules: firewire-ohci, ohci1394

CPU info:
Architecture: i686
CPU op-mode(s): 64-bit
CPU(s): 2
Tr?d(ar) per k?rna: 1
Core(s) per socket: 2
CPU socket(s): 1
Tillverkar-id: AuthenticAMD
Processorfamilj: 15
Modell: 107
Stepping: 1
Processorns MHz: 2100.020
Virtualisering: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [131, 131], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [56, 56], Sched None (priority None), drivers: ['i8042']
IRQ 3: PID: None, count: [0, 0], Sched None (priority None), drivers: ['']
IRQ 4: PID: None, count: [0, 0], Sched None (priority None), drivers: ['']
IRQ 6: PID: None, count: [0, 0], Sched None (priority None), drivers: ['floppy']
IRQ 7: PID: None, count: [1, 1], Sched None (priority None), drivers: ['parport0']
IRQ 8: PID: None, count: [0, 0], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [0, 0], Sched None (priority None), drivers: ['acpi']
IRQ 14: PID: None, count: [0, 0], Sched None (priority None), drivers: ['pata_via']
IRQ 15: PID: None, count: [0, 0], Sched None (priority None), drivers: ['pata_via']
IRQ 17: PID: None, count: [0, 0], Sched None (priority None), drivers: ['HDA Intel']
IRQ 18: PID: None, count: [0, 0], Sched None (priority None), drivers: ['ohci1394']
IRQ 20: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb2']
IRQ 21: PID: None, count: [2423, 2423], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb4', 'sata_via']
IRQ 22: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb3']
IRQ 23: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb5', 'eth0']
IRQ 24: PID: None, count: [2, 2], Sched None (priority None), drivers: ['HDA Intel', 'nvidia']

Software Interrupts:
--------------------

Thanks for posting the ffado-diag output. This is a brief note to let you know that it'll be about 4 days before I'll have a chance to have a look at this in detail. Apologies, but it's due to circumstances beyond my control.

I understand your reluctance to deal with mailing lists, but in this specific case it really is the best way to maximise the exposure of your problem to people who might be able to lend assistance (they may have even used your chosen distribution themselves). For one reason or another a comparatively small number of people regularly read comment posts on the website, so the number of potential respondents is small.

Are we talking about the same physical hardware when running the two different distributions? The CPUs certainly appear to be the same.

The most obvious difference between the two systems (as I think you've mentioned) is that the older one uses the old kernel firewire stack while the newer distribution makes use of the new stack. There may be an issue with the new stack on your hardware, with which FFADO has only a passing involvement. If this is the case then it would be good to see what Stefan (the kernel firewire maintainer) has to say. While he doesn't read these comments, he does frequent the ffado-devel mailing list. He may have some additional tests for you to run which may shed light on the subject. Looking through the ffado-diag output quickly I can't see anything which looks particularly bad or out of place.

I must keep moving; I'll have to leave it there until these busy few days are over.

Hi. I was wondering if anyone knows anything about the digital fiber optic out on the FA-66. I've had mine working pretty well for most applications, especially when using headphones for monitoring (great sound!) but I've got a soundbar with subwoofer that I'd like to use as a monitor using the digital fiber optic out and I'm not getting any sound. Is that a software/configuration problem? I haven't found any documentation on that particular output, so I'm hoping someone knows what needs to be done with that or can at least tell me that FFADO can't make it work so I can move on with my life.

I'm not overly familiar with the FA-66 or soundbar systems. The optical port is an SPDIF port and I assume that your soundbar system expects SPDIF. Does the soundbar expect so-called PCM audio input, or is it instead expecting an encoded surround signal which it will then decode? The FA-66 produces a stereo PCM signal on its optical outputs, so if the soundbar is not expecting this then silence will follow.

Beyond that, what sample rates does the soundbar accept? The FA-66 can do from 44.1 kHz all the way up to 192 kHz from memory. If you're sending audio at a rate the soundbar can't accept, again you'll get silence.

As far as I know the FA-66's optical outputs do work with FFADO, so it would be worth checking these simple things first.

I assume that when you run jackd/ffado you get jack ports corresponding to the optical ports, and that you're directing audio into these ports.