F-Control Audio FCA202

Support Status: 
Full Support


I can't wait anymore!
when will this be coming out to work?

Latest SVN versions make the device play audio, recording isn't very good (yet).
Requires a bit of hacking to make it work though.

Hey i been waiting for some time for someone to say "hey it works"
Can you give me some more info?

I'm using mine on an AMD system with 2.6.32 kernel (64bit) on a Debian unstable installation
There isn't really a "one size fits all" solution for this. If you want to try it you need to compile your own version since it isn't in the stable release (yet). manuals on how to compile your own can be found on the development part on this website.

I've tested my FCA202 with FFADO built from the SVN trunk, using Ubuntu Studio 9.10, and it works ok, for playback and recording. But only when I select a sample rate of 96 KHz.

At 48 KHz, I can playback and record also, but the input gain for recording is very, very high. I need to use a very low input signal to avoid clipping, and then the background noise becomes unacceptable. o this mode is not usable for recording.

But at 96 KHz the quality in recordings is very good :-)

I cannot chose the bit sample format (16 bit or 24 bit). It appears blocked in qjackctl. Ardour converts it to 32 bit floating point, and I don't know exactly which format is the FCA202 delivering...

I have just tested my FCA202 with FFADO compiled from SVN, on a standard Ubuntu Studio 9.10 install, and it works OK for playback and recording. But only when I select a sample rate of 96 kHz

In 48 kHz mode, playback also works, but for recording the input gain is very, very high. So I need to use a very low input signal level to avoid clipping. And then, the noise level is too high, the recording is not usable in this mode.

But at 96 kHz the quality of recording is very good, I'm very happy with it ;-)

I been trying to do it on a ubuntu box-it's a no go :(
cant seem to get it to work right...

Well, I have followed the tutorial from:


but with some minor changes to fit what is already installed on Ubuntu Studio 9.10 (I have not tried the same on plain Ubuntu 9.10)

1 - in first place, as ffado 2.0 RC2 is already installed, you can use:

sudo apt-get build-dep libffado

and this installs almost everything needed to build ffado.

2 - After that, with Synaptic I have checked what more is still needed, according to the tutorial. So I have manually installed, with Synaptic, the following packages: "libavc1394-dev" , "python-qt4-dev" , "subversion" and "libtool".

3 - Download fonts from SVN and compile FFADO and Jack as explained in the tutorial. Be careful to add "PREFIX=/usr" as explained ("Avoid multiple installations .."), when you use SCONS to build FFADO, and also when launching ./autogen.sh or ./configure for building JACK

4 - Check the required modules and permissons, as explained in the tutorial. Then I have found that the normal user has no permissions by default in Ubuntu Studio to load the module "raw1394", owned by root and assigned only to the users group "root".

5 - to solve this, I've created a file (using "sudo gedit") on /etc/udev/rules.d , with the name "60-raw1394.rules" and containing the line:
KERNEL=="raw1394", GROUP="audio"

6 - reboot the system and test FFADO entering in a console:

7 - If it still can't open the firewire port, try entering the following:
sudo modprobe raw1394
sudo chmod o+rw /dev/raw1394

and try again with ffado-dbus-server

The last step I don't now if is really necessary. I've seen a post on a forum recommending it, to setup firewire video devices in linux with KINO. Theorically, the udev rule should allow you to use the module raw1394 , but the above commands have helped me to start the device working ...

When ffado-dbus-server succesfully loads without errors, you can try to open ffado-mixer, or starting jackd using qjackctl (JACK control in Ubuntu Studio's menu) and then open Ardour or Audacity.

I can't compile on Ubuntu "Vanilla" 9.10. I get this error:

..... (many "yes" and some deprecations)
Checking for the python module 'dbus.mainloop.qt' (cached) no
Checking whether 'xdg-desktop-menu --help' executes (cached) yes

I couldn't find all the prerequisites ('pyuic4' and the python-modules 'dbus'
and 'PyQt4', the packages could be named like dbus-python and PyQt) to build the
Therefor the qt4 mixer will not get installed.

But that packages are installed, along with every -dev related to dbus or python and qt (except python-kde-dev).

I have updated the wiki with info about dependencies for building FFADO from SVN (http://subversion.ffado.org/wiki/Dependencies/Ubuntu), in Ubuntu Studio 9.10 and also "vanilla" Ubuntu 9.10.

In both cases the procedure has worked for me.

I'm glad I'm not alone, I also having the same problem like DjLK. Any solution trying to be made since this guy arises it? Looking forward to hear it soon because I have few projects that are behind the schedule. Thanks you so much.

Pat Petrillo from MMA Pound for Pound Team

I've tested deeper my FCA202 now, with last FFADO SVN, and it works very well at 96000 and 44100 Hz.

The only issues now are with 48000 Hz recording, as I already explained.

I am quite new to linux, and i am stuck with my fca 202 which obviously does not work to well right now. I have been at this for about five hours now, but still cant get anything to do as i wish. Could anyone supply me with a detailed step by step guide on how to get the softwares installed properly and how to configure everything. Right now i am just looking for simple functions, such as listening to music from my hard drive, and from the internet. I primarily use the fca202 through my mixerboard to be able to play along on my electric bass, so nothing fancy is required.
I am currently running ubunto 9.10 karmic koala. I have managed to download most of the prerequired items, but i can't get the python qt4 module to cache properly, But if i can, will it be possible to run the fca202 as an all round soundcard simply by installing it? or are there other things that need to be done first?
Thank you.

Here is my procedure for ubuntu 9.10 Karmic Koala: http://subversion.ffado.org/wiki/Dependencies/Ubuntu.

Ther is no a Python-qt4 pachage in the repository, but several python qt4 modules are already installed. I've only added python-qt4-dev with synaptic, as explained in the link, and it works, I can successfully build ffado and jack.

Anyway, the FCA202, as any other firewire audiodevice, is supported through FFADO, and FFADO itself only works through JACK.
So you can use only the FCA202 with JACK compliant audio applications. This means that the FCA202 will not work as a default all round soundcard (using pulseadio, etc)

To play songs in your hardrive, or record your electric bass, a relatively simple application that can use JACK and FADO is Audacity.

I have updated the info on ffado's development wiki, adding the complete step-by-step commands needed to build FFADO and JACK on a fresh install of Ubuntu Studio 10.04.

Here is the link:


My device is no longer working under Maverick.

Works out of the box with a fresh install of Ubuntu Studio 12.04 (Precise Pangolin), without changing anything in the setup.

So no need to compile the SVN version anymore. That's great.

So I think the status for this device should be uptdated to "Supported", or at least "Reported to work".

libffado2 version in Ubunbtu Studio 12.04 is 2.099+svn2019-1ubuntu1
and jack is jackd2 version 1.9.8

My Behringer FCA202 works now very well for all sample rates: 96 KHz, 48 KHz and 44,1 KHz

This updates my older posts (two years older) reporting problems with recordings at 48 KHz. This sample rate works correctly now.

Thanks for the confirmation. I've updated the status as you have suggested. "Reported to work" is the appropriate level; refer to the FAQ entry for the available support levels and what they mean.

Thanks for the update.

I've read the FAQ entry again, and it explains that a device status of "Reported to work" implies that no developer has direct access to the device. But according to this post http://www.ffado.org/?q=node/863 (last line) it seems that Behringer has tried to cooperate, at least donating a device to the developers.

That's why I asked if a higher level of support status could be more appropiate here.

> But according to this post http://www.ffado.org/?q=node/863 (last line) it seems that Behringer has tried to cooperate, at least donating a device to the developers.

To be honest I had forgotten that this had occurred. There is more to it than just donating a device though: if the device uses non-standard extensions for example, then we really need to have some indication how to work with those extensions I'm not saying that this sort of issue affects the FCA202 though - in fact I have no personal experience with this particular interface or its protocol.

While I'm happy to bump the status to "Reported to work", the elevation to "Full support" is really something I'd rather leave to the developer who has contact with the vendor and who has done work on the respective driver: only they are in a position to tell whether the support received from the vendor justifies the "full support" tag. I'll contact them and see what they say.

I see the device status has been already bumped to "Full support". That's good, many thanks to the developers.

Behringer sells now more featured USB/Firewire interfaces: the FCA610 and FCA1616. I do not own any of them. But I hope Behringer's positive attitude towards FFADO will continue, so we can see this devices supported soon.

Yes, it seems Pieter did this a few days ago (thanks Pieter!). He's the developer I was referring to in my earlier email.

There aren't any mixer controls in ffado-mixer ("This panel is merely a placeholder ... ") or that I can see available via dbus. I tried to set the volume using `test-volume` but it segfaults. I've added the relevant info here http://subversion.ffado.org/wiki/AvcModels/BehringerFCA202 . The input gain seems to be way too low so I can't use it. The output is fine. Perhaps I have misunderstood something and there isn't a need to adjust the level? Does anyone else have this problem? It certainly works fine apart from this.

I read the manual, and checked with some reviews. There is no way to adjust the input level. I have my preamp turned up full, but it's still very quiet. I'm not sure what's wrong.

I can't really add anything since I don't have one of these devices. I've tweaked the subject a little so there's a chance of capturing the attention of someone who has had the FCA202 operating correctly. I'm assuming from your "No mixer controls..." comment that you're getting a very low level signal coming in via FFADO even though your preamp is maximised. Is this correct?

Could you detail your signal flow (including make/model of anything used)?

The device has no way to adjust input level, and needs a "pro" audio line level (+4 dBU). And that's considerably higher than typical consumer audio line signals (-10 dBU).

But there is nothing wrong with it. You can achieve the correct input level with an analog mixer to handle FCA202's inputs and outputs. Very basic and relatively inexpensive analog mixers are enough. I use a small Behringer Xenix 1002 (aprox. 66 euros, models Xenix 502 and 802 are even cheaper).

These mixers offer a max. output level of +22 dBu. A separate mic preamp usually delivers lower levels.

For recording I adjust the Xenix mixer until I have a main mix output level of 0 dB in the VU meter (all green LEDs lit on signal peaks), and that's the good signal to feed FCA202's inputs.

I'm trying to get this to become recognized but I get nothing. I've tried UbuntuStudio-12.10, LinuxMint-14 with KXstudio, and now AVLinux-6.0 and none of these OS will recognize my FCA202. It keeps failing with'giving up on config rom for node id ffc0'. Any ideas anyone?

I think the discussion about this was moved to the ffado-devel mailing list (the username here as a striking similarity to that used on the list). The outcome of the discussion on the mailing list was that the FCA202 had an internal fault which prevented it working correctly on the firewire bus. A replacement FCA202 solved the problem. A failure to read the configrom more or less says that the device can't be accessed by the computer. In almost every case the primary suspicion in this case would be a faulty device, as it was in this case.

If I am wrong and this is a different user to the one who posted in the mailing list, I suggest in the first instance that you take a look at the mailing list posts in the archive (look for the thread with a subject "Behringer FCA202 help" in the ffado-user list) and see if the symptoms match. Perhaps then post in the list yourself, since it tends to be much easier to troubleshoot these problems on the list than here in the article comments.