Revision 1336, 10.0 kB (checked in by ppalmers, 14 years ago)

Bring trunk up to date with branches/libffado-2.0:

svn merge -r 1254:1299 svn+ssh://
svn merge -r 1301:1320 svn+ssh://
svn merge -r 1322:1323 svn+ssh://
svn merge -r 1329:HEAD svn+ssh://

Add getSupportedSamplingFrequencies() to DICE, RME and Metric Halo AvDevices?

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
1 FFADO v2.x
2 ==========
4 The FFADO project aims to provide a free driver implemenation for FireWire
5 (IEEE1394, iLink) based (semi-) professional audio interfaces. The focus of
6 the project are on audio/music production rather than consumer audio. This
7 means that, although we intend to supported all features at some point,
8 consumer features are considered less important. The most obvious example of
9 a consumer feature is AC3/DTS passthrough support, which is unsupported at
10 the moment.
12 This package provides the libffado shared library that provides a unified
13 programming interface to configure and use all supported devices. Currently
14 this library is used by the 'firewire' backends of the jack audio connection
15 kit sound server ( This backend provides audio and midi support,
16 and is available both in jackd and it's multiprocessor variant jackdmp.
17 (note: At the moment there is no support for ALSA nor for pulseaudio.)
19 Access to the device internal configuration (e,g, internal mixer) is exposed
20 using the ffado-dbus-server daemon. This daemon exposes the configurable
21 parameters of all detected devices through DBUS. The ffadomixer application in
22 support/mixer presents a GUI to control these parameters (only for officially
23 supported devices).
25 Features
26 --------
27 * 24-bit audio input/output (unlimited number of channels)
28 * supports for all samplerates a device supports
29 * MIDI input/output (unlimited number of channels)
30 * Support for S/PDIF and ADAT/SMUX I/O
31 * Internal mixer and device control support for all officially supported
32   devices (NOTE: no support for internal DSP)
33 * Support for device aggregation (limited to devices on the same bus)
35 Device Support
36 --------------
38 The devices officially supported are:
39 * ESI Quatafire 610
40 * Terratec Producer Phase 88
41 * Focusrite Saffire (original/white)
42 * Focusrite Saffire PRO10
43 * Focusrite Saffire PRO26
44 * ECHO AudioFire2, AudioFire4, AudioFire8, AudioFire12
45 * Mackie Onyx Mixer FireWire expansion
47 The 'officially supported' label is only given to devices that fullfil the
48 following:
49 * at least one of the developers has the device
50 * the vendor provides development support (access to information)
51 * the device works
53 Through reverse-engineering the following devices will also work:
54 * MOTU traveller
55 * MOTU 828mkII
56 Note: the support for these devices is based on a significant reverse
57 engineering effort. This means that the developers had no support from the
58 device vendor, and this of course limits the extent to which problems can
59 be solved. You have been warned. Please do not buy devices for which support
60 is based upon reverse engineering, nor from vendors that are Linux-hostile
61 (e.g. MOTU). Value the support that some vendors provide and buy their
62 stuff. Check for details. It can't be said enough: currently it is
63 extremely unwise to buy a MOTU device if you intend to use Linux.
65 The driver is written to provide generic support for all devices it might be
66 able to handle. This means that most devices based on the BridgeCo BeBoB or
67 the ECHO FireWorks platform will work, at least to a certain extent.
69 Devices that have been reported to (partially) work with the generic support:
70 * Presonus FireBox
71 * Presonus FirePod / FP10
72 * Alesis io14
73 * TC Konnekt 8, Konnekt 24D, Konnekt Live
75 Usupported devices:
76 * Presonus FireStation
77 * Presonus FireStudio (all variants)
78 * Other TC Konnekt devices
79 * Other Alesis devices
80 * Metric Halo devices
81 * RME Firewire devices
83 We constantly try to persuade vendors to help us extend our device support.
85 Dependencies
86 ------------
88 To build libffado you need several libraries. For all libraries a
89 version is provided which is a 'known good' version.  The first few
90 libraries it seems it is not necessary that the version must
91 match. The chances that it works also with an older versions are good:
93 libxml++2   (>= 2.13.0)
95 These libraries here should be at least the version listed:
97 libraw1394  (>= 1.3.0),
98 libiec61883 (>= 1.1.0),
99 libavc1394  (>= 0.5.3),
100 dbus-1      (>= 1.0),
102 Currently only the jackd audio server is supported.
104 jackd (>= 0.109.12),
105 [NOTE: at the time of writing, this is the development (SVN) version.]
107 Optionally, but recommended is that you install qjackctl:
109 qjackctl (>=,
111 To build the optional ffado device mixer control utility you also require:
113 Qt          (>= 3.0),
114 SIP         (>= 4.7.0),
115 PyQt        (note below),
116 dbus-python (>= 0.82.0),
118 The version of PyQt must be chosen to match the version of Qt in use.  For
119 Qt 4.x use PyQt 4.x, while PyQt 3.x is applicable for all other Qt versions
120 from 1.43.
122 SIP is only required to compile PyQt.  If using a binary package of PyQt
123 SIP should not be needed.
125 How to build
126 ------------
128 If you want to build the release version you can simply do following:
130 $ scons
131 $ scons install
133 If you want some debug information (because something seems not
134 to work correctly) you can try to do following:
136 $ scons DEBUG=yes
137 $ scons install
139 More extended instructions can be found here:
142 NOTE: In order to build jackd with ffado support, you have
143 to install libffado before you build jackd. The backend to use in jackd is
144 firewire.
146 NOTE: the beta versions are distributed with debugging enabled by default.
148 DISTRIBUTION PACKAGERS NOTE: Please do not enable support for devices
149 if it is not on by default. If device support for a specific device
150 is not turned on by default by the developers, it means that it is not
151 ready yet. Most of the time it is placeholder code for future devices.
153 Running jackd
154 -------------
156 The easiest way to run this is using qjackctl. There are only minor
157 differences with the other backends, however you should change some
158 of the default values:
159 - It is recommended to change the 'periods/buffer' field to 3, especially
160   if you use low period sizes (=< 128)
161 - It is recommended to raise the RT priority to 70.
163 In order to get it running from the command line, you need to provide some
164 arguments to jackd.
166 Run
168 $ jackd -d firewire --help
170 to see the backend options. You can easily figure out how to set them using
171 the remarks given above (for qjackctl).
173 For the other aspects of jackd usage, consult the jackd documentation.
175 Here is a sample session (without realtime support enabled):
177     $ jackd -d firewire
178     no message buffer overruns
179     jackd 0.111.0
180     Copyright 2001-2005 Paul Davis and others.
181     jackd comes with ABSOLUTELY NO WARRANTY
182     This is free software, and you are welcome to redistribute it
183     under certain conditions; see the file COPYING for details
185     JACK compiled with System V SHM support.
186     loading driver ..
187     3106528665:  (ffado.cpp)[  99] ffado_streaming_init: libffado 1.999.20 built Apr 26 2008 20:26:32
188     libiec61883 warning: Established connection on channel 0.
189     You may need to manually set the channel on the receiving node.
190     libiec61883 warning: Established connection on channel 1.
191     You may need to manually set the channel on the transmitting node.
193 (Note: you can safely ignore the libiec61883 warnings, they are normal.)
195 An important remark is that for good performance, one should always run jack
196 with the -R flag to enable realtime scheduling for critical threads:
197     $ jackd -R -d firewire
199 In case of problems
200 -------------------
202 First of all, check whether your problem is in fact a problem, and
203 whether it is a FFADO problem. The magic tool for this is google.
205 User support is a rather annoying occupation, especially since it sucks
206 time from developers that are not paid for developing, let alone for doing
207 user support. Please make sure that you have checked the following places:
211       (the terms "ffado-devel" "ffado-user" or "freebob-user" work great)
212 Some might consider this a bit arrogant or "newbie-unfriendly", but personally
213 I (Pieter Palmers) consider this a matter of politeness towards the developers.
215 If you have tried to find a solution to your problem, but you couldn't find
216 one or are confused, don't hesitate to ask for help. The preferred way is by
217 signing up to the mailing list as described on
219 Writing a bug report
220 --------------------
222 Note that the more effort you put in your bug report, the more effort we
223 will put into helping you.
225 Make sure you have compiled a DEBUG=yes version of
226 libffado. If not there is no way we can trace the problem.
228 When reporting a problem, please run jackd with the --verbose option,
229 and add the -v6 option to the firewire backend:
230     $ jackd --verbose [...] -d firewire -v6 [...]
232     ( [...] = other options )
234 This will generate an increadible amount of debug output that should
235 contain what we need to track down the problem. If you have troubles
236 saving the output, try redirecting it to a file:
238     $ jackd --verbose -d firewire -v6 2> ffado-jack.log
240 this will create a ffado.log file containing the output. Use CTRL-C
241 to exit jack if necessary.
243 The distribution contains a tool to gather some information about your
244 system. you can run it as follows:
246     $ cd support/tools
247     $ python > ffado-diag.log
249 It will check your system for basic problems and gather some information
250 regarding your hardware configuration. This will allow us to diagnose
251 your problem faster.
253 Once the logs have been created you can create a support ticket at
256 Be sure to include the following information:
257 * the log file(s) (zipped/tar.gz'ed and attached)
258 * the device you're trying to use
259 * a description of what went wrong and how to reproduce it. You
260   preferrably try to figure out a sequence of steps that can reliably
261   reproduce the issue on your system. A one-time failure is very difficult
262   to diagnose and/or fix.
263 * the distribution and its version
Note: See TracBrowser for help on using the browser.