Revision 1888, 10.2 kB (checked in by arnonym, 11 years ago)

Drop the libs in external/ and use the system-libs for that. Easier on administration, easier on compilation time, easier for packagers.

This is basically the patches provided by packagers in #290.

  • 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.6.13)
95 These libraries here should be at least the version listed:
97 libraw1394  (>= 1.3.0),
98 libiec61883 (>= 1.1.0),
99 dbus-1      (>= 1.0),
100 dbus-c++    (>= 0),
101 libconfig   (>= 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  >= 4.0,  
114 SIP >= 4.7.0,
115 PyQt (note below),
116 dbus-python >= 0.82.0,
118 The mixer applets are available for both QT3 and QT4. However, the QT3 versions
119 are no longer actively developed. The build script will automatically fallback
120 to the QT3 version if you don't have QT4 installed.
122 The version of PyQt must be chosen to exactly match the version of Qt in use.
123 For Qt 4.x use PyQt 4.x.
125 SIP is only required to compile PyQt.  If using a binary package of PyQt
126 SIP should not be needed.
128 How to build
129 ------------
131 If you want to build the release version you can simply do following:
133 $ scons
134 $ scons install
136 If you want some debug information (because something seems not
137 to work correctly) you can try to do following:
139 $ scons DEBUG=yes
140 $ scons install
142 More extended instructions can be found here:
145 NOTE: In order to build jackd with ffado support, you have
146 to install libffado before you build jackd. The backend to use in jackd is
147 firewire.
149 NOTE: the beta versions are distributed with debugging enabled by default.
151 DISTRIBUTION PACKAGERS NOTE: Please do not enable support for devices
152 if it is not on by default. If device support for a specific device
153 is not turned on by default by the developers, it means that it is not
154 ready yet. Most of the time it is placeholder code for future devices.
156 Running jackd
157 -------------
159 The easiest way to run this is using qjackctl. There are only minor
160 differences with the other backends, however you should change some
161 of the default values:
162 - It is recommended to change the 'periods/buffer' field to 3, especially
163   if you use low period sizes (=< 128)
164 - It is recommended to raise the RT priority to 70.
166 In order to get it running from the command line, you need to provide some
167 arguments to jackd.
169 Run
171 $ jackd -d firewire --help
173 to see the backend options. You can easily figure out how to set them using
174 the remarks given above (for qjackctl).
176 For the other aspects of jackd usage, consult the jackd documentation.
178 Here is a sample session (without realtime support enabled):
180     $ jackd -d firewire
181     no message buffer overruns
182     jackd 0.111.0
183     Copyright 2001-2005 Paul Davis and others.
184     jackd comes with ABSOLUTELY NO WARRANTY
185     This is free software, and you are welcome to redistribute it
186     under certain conditions; see the file COPYING for details
188     JACK compiled with System V SHM support.
189     loading driver ..
190     3106528665:  (ffado.cpp)[  99] ffado_streaming_init: libffado 1.999.20 built Apr 26 2008 20:26:32
191     libiec61883 warning: Established connection on channel 0.
192     You may need to manually set the channel on the receiving node.
193     libiec61883 warning: Established connection on channel 1.
194     You may need to manually set the channel on the transmitting node.
196 (Note: you can safely ignore the libiec61883 warnings, they are normal.)
198 An important remark is that for good performance, one should always run jack
199 with the -R flag to enable realtime scheduling for critical threads:
200     $ jackd -R -d firewire
202 In case of problems
203 -------------------
205 First of all, check whether your problem is in fact a problem, and
206 whether it is a FFADO problem. The magic tool for this is google.
208 User support is a rather annoying occupation, especially since it sucks
209 time from developers that are not paid for developing, let alone for doing
210 user support. Please make sure that you have checked the following places:
214       (the terms "ffado-devel" "ffado-user" or "freebob-user" work great)
215 Some might consider this a bit arrogant or "newbie-unfriendly", but personally
216 I (Pieter Palmers) consider this a matter of politeness towards the developers.
218 If you have tried to find a solution to your problem, but you couldn't find
219 one or are confused, don't hesitate to ask for help. The preferred way is by
220 signing up to the mailing list as described on
222 Writing a bug report
223 --------------------
225 Note that the more effort you put in your bug report, the more effort we
226 will put into helping you.
228 Make sure you have compiled a DEBUG=yes version of
229 libffado. If not there is no way we can trace the problem.
231 When reporting a problem, please run jackd with the --verbose option,
232 and add the -v6 option to the firewire backend:
233     $ jackd --verbose [...] -d firewire -v6 [...]
235     ( [...] = other options )
237 This will generate an increadible amount of debug output that should
238 contain what we need to track down the problem. If you have troubles
239 saving the output, try redirecting it to a file:
241     $ jackd --verbose -d firewire -v6 2> ffado-jack.log
243 this will create a ffado.log file containing the output. Use CTRL-C
244 to exit jack if necessary.
246 The distribution contains a tool to gather some information about your
247 system. you can run it as follows:
249     $ cd support/tools
250     $ python > ffado-diag.log
252 It will check your system for basic problems and gather some information
253 regarding your hardware configuration. This will allow us to diagnose
254 your problem faster.
256 Once the logs have been created you can create a support ticket at
259 Be sure to include the following information:
260 * the log file(s) (zipped/tar.gz'ed and attached)
261 * the device you're trying to use
262 * a description of what went wrong and how to reproduce it. You
263   preferrably try to figure out a sequence of steps that can reliably
264   reproduce the issue on your system. A one-time failure is very difficult
265   to diagnose and/or fix.
266 * the distribution and its version
Note: See TracBrowser for help on using the browser.