More RME news

Thanks to RME, their Australian distributor and project donations, we now have a Fireface UFX. This will be used to extend the RME driver to support the newest generation of RME's interfaces (the UFX and UCX). As always there's no ETA but it's hoped that basic streaming will be brought up fairly quickly. At this stage the UFX will be more easily supported because we don't currently have a UCX. This may of course change in the future.

Development wiki was down

17 December 2012: The web interface on, which hosts our development wiki, is down at present. Investigations are continuing but it appears that a system update by the hosting provider may have inadvertently broken our trac installation. There is no ETA on a restoration at present.

26 December 2012: for those assisting with the debugging of the problem, I have attached the text of the python errors we have been seeing (ffado_python_errors.html).

FFADO version 2.1.0 released

The FFADO project is pleased to announce the long-awaited release of version 2.1.0. With improved stability, many bugfixes and a large number of newly supported devices this version represents 2 years work by the small but dedicated FFADO team. All users of FFADO are encouraged to upgrade.

This is a source-only release: libffado-2.1.0.tgz.

RME Fireface-800 update

Here's a quick update on the Fireface-800. The short story is that it mostly works as of svn revision 2062. Ffado-mixer includes all device controls and the matrix mixer is complete. Audio streaming works to and from the device, although startup can still be a little rough (that's next on my list to look at). It's probably ready for an initial round of testing by others to confirm that success can be achieved on systems other than my own. Please use the ffado-devel mailing list to report bugs and provide feedback.

RME Fireface 400 mostly usable (I think)

Implementation of the remaining mixer and device controls for the Fireface-400 is now complete, although some combinations of settings are yet to be tested (particularly those associated with clock sources). This means that the Fireface-400 is getting close to being usable with FFADO now (at least on my system). Wider testing of svn head is encouraged so we can identify any remaining rough edges and see how it performs on a variety of computers. Please use the ffado-devel mailing list to report bugs and other problems.

RME driver gains a mixer

The matrix mixer capability of the RME Fireface 400 is now available through ffado-mixer. There is still some functionality remaining to be done, including:

RME driver progress

After far too many delays (both technical and logistical,for which I apologise), practical progress has finally been made on the FFADO RME driver.

In short, the driver is now ready for wider testing, although there are some important limitations and cautions to keep in mind before proceeding. Read more for the details.

FFADO 2.0.1 'Summertime' released

Without further ado, we hereby give you the 2.0.1 release of ffado.

The changelog to the previous 2.0.0 is rather simple:

Make it work on the new firewire-stack.

Of course some more fixes went into the package. But its mostly intended for distributors so they can finally deprecate/disable the old firewire stack in kernels.

For more changelog and instructions please look back at the 2.0.0 release announcement.

Rumors about FFADO and the new firewire stack [Updated May 11th, 2010]

The last weeks have seen a few rumors and lots of questions: Is ffado running with the new firewire stack?

The answer is kind of yes.

What you need is libraw1394 in version 2.0.5 or higher. And kernel 2.6.32 or higher. Then ffado (both the 2.0 branch and development trunk) should be usable on the new juju stack. Thanks to the team of the kernel-stack and some distributions for stepping up and (mostly) fix the kernel and libraw1394 for this. The changes to ffado where quite minimal.

The other answer is still no.

Because ffado still uses libraw1394 as layer between the kernel and its own streaming-/configuration-stuff. Which adds some latency and a lot of uncertainties for the low-latency. There is work going on to implement in-kernel streaming but this is all to early for testing or announcement. And time is sparse...

FFADO 2.0.0 Released!

FFADO 2.0.0 Released!

The FFADO team is proud and happy to announce the release of FFADO 2.0.0. As the release candidates have been around for almost one year now without a significant amount of bug reports we feel confident that the current code-base has matured. Around the end of november the 1000-th device was registered as being used with FFADO, which seemed to be a nice number to triggered the release (aside from the fact that no major bugs have been reported over the last 6 months).

Furthermore on December 2 the Linux kernel version 2.6.32 has been released. This version fixes the new kernel FireWire drivers such that they are compatible with FFADO. So once the distributions pick up this kernel the old/new kernel stack confusion should be history.

Thanks go out to the vendors that provided us with gear to support for the 2.0 release: Echo Digital Audio, Edirol, Ego Systems Inc, Focusrite, Mackie and Terratec. Kudos for their early-bird support!

Special thanks also go to BridgeCo and TC Applied for providing us with their development platforms and for helping with vendor contacts. Their support makes that FFADO covers the most widely used platforms for FireWire audio and that we can quickly implement support for new devices.

Looking ahead to the 2.1 release we can announce that we have implemented (basic) support for additional devices from Focusrite, Behringer, Stanton and TC Electronic. We plan to move to beta-testing 2.1 fairly soon as development on it has been ongoing for more than a year now. Additionally, work is being done on the RME devices, but its not yet known when that will be finished. Support for some other vendors is in the pipeline, so stay tuned for more announcements.

A second major development is the move of the streaming infrastructure to kernel space. A kernel-space implementation will bring significant improvements with respect to reliability and efficiency. Furthermore it will allow to expose an ALSA interface, meaning that the scope of FireWire audio on Linux is extended significantly. Thanks to the Google Summer of Code and the Linux Foundation, work on this has been done during the summer. The code is not yet ready for use, but things are moving.