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.

libffado?

This release provides the libffado shared library that provides a unified programming interface to configure and use all supported devices. Currently this library is used by the 'firewire' backend of the jack audio connection kit sound server (http://jackaudio.org). This backend provides audio and midi support, and is available both in jackd and it's multiprocessor variant jackdmp (aka jack2). (note: At the moment there is no direct support for ALSA nor for pulseaudio, but these systems can use jack.)

Access to the device internal configuration (e,g, internal mixer) is exposed using the ffado-dbus-server daemon. This daemon exposes the configurable parameters of all detected devices through DBUS. The ffadomixer application in support/mixer presents a basic GUI to control these parameters (only for officially supported devices).

Features

  • 24-bit audio input/output (unlimited number of channels)
  • support for all sample rates a device supports
  • MIDI input/output (unlimited number of channels)
  • Support for S/PDIF and ADAT/SMUX I/O
  • Support for external sync (e.g. Wordclock)
  • Internal mixer and device control support for all officially supported
    devices (NOTE: no support for internal effects DSP)
  • Support for device aggregation (limited to devices on the same bus that are synced externally)

Usage feedback

This release includes an option where you can identify your device as being used on Linux with FFADO. You will be asked whether you want to submit your device information to ffado.org. The reason this feature is present is to convince the supportive vendors that their cooperation pays off, and to convince the other vendors that Linux users are a market. A secondary advantage is that we can keep track of what versions are used by how many people.

Therefore we would like to ask everyone to perform this registration. No personal data is transmitted (except for an optional email address). The IP address of the submitter is saved to help recovery in case the database is bombed with bogus data. However the address is first processed by one-way MD5 hashing it, such that it is not recoverable and privacy is secured. This usage information is of enormous importance for future device support. The aggregated statistics are available online: http://www.ffado.org/?q=usage.

Changelog

RC2 => 2.0.0

  • Fix reversed Terratec Phase88 front/back switch
  • Fix format string warnings
  • Fix config file bug
  • Free FCP listener when something goes wrong
  • Compiler warning fixes

RC1 => RC2

  • Various packaging improvements and cosmetic fixes.
  • Improved the Edirol FA101 mixer
  • While the streaming engine is running, prevent mixer changes that result in aborted streaming
  • Add status bar logging to the mixer window
  • Install a service-file if possible
  • Add command rate control for the Saffire devices to reduce the issues with mixer actions messing up audio.
  • Fix Terratec Phase88 mixer
  • Implement mixer support for the MOTU UltraLite
  • Improve mixer support for the MOTU 896HD
  • Add a minimum for the packetsize parameter for very low channel-count devices
  • Fix handling of MIDI 2x and 3x mode
  • Improve the jitter performance of the timestamping
  • Reduce CPU usage
  • Fix the bug that prevented jackd from exiting freewheeling mode
  • Introduce transmit prebuffering to increase reliability with small period sizes
  • MOTU: Fix bug related to disabled (unused) audio channels
  • Introduce support for driver parameters in the config file
  • Ensure that the order specified in the specification string when aggregating devices is honored.
  • Ensure that libffado.so is properly versioned (SONAME) and installed
  • Add a firmware version check for ECHO Fireworks based devices
  • Add a firmware version check for Terratec Phase88 devices
  • By default the library is compiled with debugging turned off

Beta7 => RC1

  • Various packaging improvements and fixes.
  • Install both the qt3 and the qt4 mixer when the needed tools are available.
  • Add ffado-diag to the installed tools
  • Disable the nickname control for devices that don't support it
  • Various QT4 mixer improvements
  • Increase efficiency while streaming
  • Fix some CTR wraparound bugs
  • Fix bebob fallback discovery
  • Fix AV/C based sync source selection
  • Fix Saffire Pro sync source selection
  • Fix Saffire Pro and Saffire (LE) samplerate selection
  • Fix jack freewheeling bug
  • Add workaround for Edirol FA-101 firmware race condition

Beta6 => Beta7

  • General code cleanup
  • Improve mixers of various devices (especially the MOTU and Edirol mixers)
  • Port mixers to QT4 for better usability (QT3 mixers still work but are deprecated)
  • Implement support for ECHO session blocks
  • Fix Focusrite Saffire Pro clock source selection
  • Implement configuration file mechanism to ease run-time configuration
  • Improve the behavior when confronted with dying iso transmit handlers
  • Reset transmit buffer rate DLL on XRUN.
  • Improve bus reset handling
  • Improve reliability of ISO streaming on various host controllers
  • Fix discovery issues with DM1x00 based devices (especially Edirol devices)
  • Remove the dependency on libavc1394 by implementing our own FCP transaction support
  • Fix float to int conversion dynamic range bug in the AMDTP StreamProcessor

Beta5 => Beta6

  • implement discovery fallback (tries generic support when encountering an unsupported device)
  • fix gcc-4.3 compilation issues
  • take CC and CXX from the environment if defined there
  • implement separate mixer for Phase X24 and Phase 24
  • fix saffire mixer
  • fix cache issues
  • fix clock source segfault
  • fix ffadomixer python 2.4 compatibility
  • use FocusRite vendor-specific clock selection for the Saffire PRO devices

Beta4 => Beta5

  • fix BeBoB flooding issues
  • numerous mixer improvements
  • fix threading issues
  • remove all unused code
  • fix clocksource selection bugs
  • fix 64bit compilation issue
  • improve library behavior in error situations
  • improve shutdown of MOTU interfaces
  • make dbus server handle busresets cleanly

Beta3 => Beta4

  • fix bugs in BeBoB caching code
  • extend Saffire PRO26 mixer
  • various mixer improvements
  • switch back to BeBoB discovery code for FA-101

Beta2 => Beta3

  • fix memory corruption bug in saffire LE mixer code
  • various debugging code improvements
  • create config save directory if not present.
  • change registration window looks.
  • various MOTU mixer improvements
  • workaround MOTU not setting a vendor/model name
  • one window for all mixers, tabbed.
  • fix CTR reconstruction bug
  • Add a generic part for each mixer controlling the nickname and the clocksource.
  • Rework/resort the initialization of mixer-widgets...
  • fix issues in timestamp usage
  • re-enable late transmission
  • switched off all extended debugging features by default

Beta1 => Beta2

  • Correct issues in the README file
  • Remove unneeded ALSA dependency
  • Several mixer improvements
  • Implement usage statistics gathering

Building and Installing

Please refer to the README document in the package. Not doing so means taking a risk ;).

Download

Source Distribution

AttachmentSize
libffado-2.0.0.tar.gz760.48 KB

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Is any movement here?

Is this developing yet? sorry can you let the focusrite pro 24/dsp working in the official one unblock
i know you did a hard work with this but the svn use something incompatible what just no works with the software and jack, and is unusable it just works to listen music or listen webpages.
sorry about that i really apreciate your job but i dont know anythig about programing i just know make music and i cant doit with that troubles this is the unic question becouse i cant make music with linux

Re: Is any movement here?

To briefly answer the questions posed:

  • Yes, this is developing. Admittedly it's been a bit slower over 2011 than all of us would have liked, but real life issues affected several key developers in that time frame. Things are, I think, picking up now.
  • Regarding the Focusrite pro 24/dsp, it is my understanding that the audio portion of this device is working with svn trunk now. The DSP component is not, mainly because Focusrite have not released the information we need in order to drive the DSP sections of the interface.
  • If you have problems with svn trunk, please let us know the details so we can try to work out what's going wrong. You can do that by either raising a ticket in our bug tracking system, or posting to one of our mailing lists (ffado-user is probably the best initial port of call). Because we really can't tell what "the svn use something incompatible what just no works with the software and jack" means we can't provide specific feedback.

We would really like to try to help you get your Focusrite working with FFADO. Please do follow up as described above.

With regard to formal releases, there are ideas to prepare for a 2.1 release later this year. We are presently tidying up a number of issues described by various users in our ticketing system and finishing off some features. A release will follow once this has been completed. I can't give an indication as to when this might be because it depends on how much time the FFADO developers are able to spend on the project in the coming months. None of us are paid to work on FFADO and do it in our spare time, which is why sometimes considerable time can elapse between bursts of visible work.

Re: Is any movement here?

well ive installed the svn following the step by step in this page and is simply not working, i have no idea to watch the wrong thing, i dont know anything about programming i just want make music using free software. i think i have the error of firmware because is a pro24dsp not a normal one but the formula to resolve that is not in any place, i know i have to modificate a part of the src but i dont know wich one.

I remember in 25-01-2011 one person in the ffado irc helped me to do that but i can remember too what the svn was giving incompatibility problems with one lib, i dont remember wich one but the result was in the imposibility to work with programs like ardour or qtractor. because they didnt detect what jack was conected.

i really like to help you to develope but i dont know how, i just know try and fail in the most cases.

Re: Is any movement here?

Could you post the URL of the instruction page you're referring to, just so I know what steps you've taken?

Is it possible to describe in more detail what "simply not working" means in your context? Did the compilation and/or installation of svn fail, or is the problem encountered when running jackd?

In any case, could you post the error messages that you're seeing which are leading you to believe that it's not working? Please also tell us the full command you're using to run jackd (or describe the options if qjackctl is being used). Without this information it's impossible to guess where the problem might lie.

I am not aware that a firmware issue can stop the pro24dsp from working with FFADO, but then again I'm not an expert with the DICE devices so there might be something that I'm not aware of. As far as I'm aware, FFADO will work with the pro24dsp in the same way as it does the pro24: the dsp portions of the interface are simply ignored.

Re: Is any movement here?

I have responsed but is stoped by spam because i think to much code, ive posted the same in the mail.list
http://sourceforge.net/mailarchive/message.php?msg_id=29174282

Re: Is any movement here?

this is the things ive followed
http://subversion.ffado.org/wiki/Dependencies/Ubuntu
and following this also
http://www.ffado.org/?q=node/1204

I edited the saffire_pro24.cpp to modify the condition so it accepts the 0x10008 firmware, and it seems to work!

I changed « if (tmp[0] != 0x00010004 ) » to « if (tmp[0] != 0x00010008 ) ».

and...

Hey, thanks for that clue. That did the trick for me.
I have the dsp version, so in order to get the ffado-mixer working I edited the saffire_dice.py and changed line:

if self.configrom.getModelName() == "SAFFIRE_PRO_24"
to
if self.configrom.getModelName() == "SAFFIRE_PRO_24DSP"

Yesterday when i did it the interface was completly detected by ffado-diag
but with no luck running jackd, telling me what is not compatible with libffado 2.999.0-2125M.
today i dont know how libffado is not working again responding ffado-diag with

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

=== CHECK ===
Base system...
kernel version............ 3.2.0-23-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
/dev/fw* permissions:
crw------- 1 root root 250, 0 abr 24 17:07 /dev/fw0
crw------- 1 root root 250, 1 abr 24 17:51 /dev/fw1
User IDs:
uid=1000(splashman) gid=1000(splashman) grupos=1000(splashman),4(adm),20(dialout),24(cdrom),29(audio),46(plugdev),105(lpadmin),119(admin),122(sambashare),1001(raw1394)
Prerequisites (dynamic at run-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 ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ 0.5.3
flags ........... -lavc1394 -lrom1394 -lraw1394
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
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 ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ 0.5.3
flags ........... -lavc1394 -lrom1394 -lraw1394
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
Hardware...
Host controllers:
01:07.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW322/323 [11c1:5811] (rev 61) (prog-if 10 [OHCI])
Subsystem: Pinnacle Systems Inc. Device [11bd:000e]
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
Hilo(s) por núcleo: 1
Núcleo(s) por zócalo:2
Socket(s): 1
Nodo(s) NUMA: 1
ID del vendedor: GenuineIntel
Familia de CPU: 6
Modelo: 15
Stepping: 13
CPU MHz: 1999.969
BogoMIPS: 3999.97
caché L1d: 32K
caché L1i: 32K
caché L2: 1024K
NUMA node0 CPU(s): 0,1
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [65, 65], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [2292, 2292], Sched None (priority None), drivers: ['i8042']
IRQ 7: PID: None, count: [2, 2], Sched None (priority None), drivers: ['parport0']
IRQ 8: PID: None, count: [1, 1], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [0, 0], Sched None (priority None), drivers: ['acpi']
IRQ 12: PID: None, count: [197210, 197210], Sched None (priority None), drivers: ['i8042']
IRQ 14: PID: None, count: [30194, 30194], Sched None (priority None), drivers: ['pata_amd']
IRQ 15: PID: None, count: [0, 0], Sched None (priority None), drivers: ['pata_amd']
IRQ 19: PID: None, count: [168, 168], Sched None (priority None), drivers: ['firewire_ohci']
IRQ 21: PID: None, count: [4463, 4463], Sched None (priority None), drivers: ['ahci']
IRQ 22: PID: None, count: [935719, 935719], Sched None (priority None), drivers: ['ehci_hcd:usb1']
IRQ 23: PID: None, count: [228736, 228736], Sched None (priority None), drivers: ['ohci_hcd:usb2', 'nvidia']
IRQ 43: PID: None, count: [0, 0], Sched None (priority None), drivers: ['eth0']

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).

Re: Is any movement here?

This is the post what ive followed
http://subversion.ffado.org/wiki/Dependencies/Ubuntu
and following
http://www.ffado.org/?q=node/1204
I edited the saffire_pro24.cpp to modify the condition so it accepts the 0x10008 firmware, and it seems to work!

I changed « if (tmp[0] != 0x00010004 ) » to « if (tmp[0] != 0x00010008 ) ».

and..
Hey, thanks for that clue. That did the trick for me.
I have the dsp version, so in order to get the ffado-mixer working I edited the saffire_dice.py and changed line:

if self.configrom.getModelName() == "SAFFIRE_PRO_24"
to
if self.configrom.getModelName() == "SAFFIRE_PRO_24DSP"
Yesterday when i did it the interface was completly detected by ffado-diag
but with no luck running jackd, telling me what is not compatible with libffado 2.999.0-2125M.
today i dont know how libffado is not working again responding ffado-diag with

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

=== CHECK ===
Base system...
kernel version............ 3.2.0-23-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
/dev/fw* permissions:
crw------- 1 root root 250, 0 abr 24 17:07 /dev/fw0
crw------- 1 root root 250, 1 abr 24 17:51 /dev/fw1
User IDs:
uid=1000(splashman) gid=1000(splashman) grupos=1000(splashman),4(adm),20(dialout),24(cdrom),29(audio),46(plugdev),105(lpadmin),119(admin),122(sambashare),1001(raw1394)
Prerequisites (dynamic at run-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 ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ 0.5.3
flags ........... -lavc1394 -lrom1394 -lraw1394
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
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 ........... -ljack
libraw1394 ........ 2.0.7
flags ........... -lraw1394
libavc1394 ........ 0.5.3
flags ........... -lavc1394 -lrom1394 -lraw1394
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
Hardware...
Host controllers:
01:07.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW322/323 [11c1:5811] (rev 61) (prog-if 10 [OHCI])
Subsystem: Pinnacle Systems Inc. Device [11bd:000e]
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
Hilo(s) por núcleo: 1
Núcleo(s) por zócalo:2
Socket(s): 1
Nodo(s) NUMA: 1
ID del vendedor: GenuineIntel
Familia de CPU: 6
Modelo: 15
Stepping: 13
CPU MHz: 1999.969
BogoMIPS: 3999.97
caché L1d: 32K
caché L1i: 32K
caché L2: 1024K
NUMA node0 CPU(s): 0,1
Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [65, 65], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [2292, 2292], Sched None (priority None), drivers: ['i8042']
IRQ 7: PID: None, count: [2, 2], Sched None (priority None), drivers: ['parport0']
IRQ 8: PID: None, count: [1, 1], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [0, 0], Sched None (priority None), drivers: ['acpi']
IRQ 12: PID: None, count: [197210, 197210], Sched None (priority None), drivers: ['i8042']
IRQ 14: PID: None, count: [30194, 30194], Sched None (priority None), drivers: ['pata_amd']
IRQ 15: PID: None, count: [0, 0], Sched None (priority None), drivers: ['pata_amd']
IRQ 19: PID: None, count: [168, 168], Sched None (priority None), drivers: ['firewire_ohci']
IRQ 21: PID: None, count: [4463, 4463], Sched None (priority None), drivers: ['ahci']
IRQ 22: PID: None, count: [935719, 935719], Sched None (priority None), drivers: ['ehci_hcd:usb1']
IRQ 23: PID: None, count: [228736, 228736], Sched None (priority None), drivers: ['ohci_hcd:usb2', 'nvidia']
IRQ 43: PID: None, count: [0, 0], Sched None (priority None), drivers: ['eth0']

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).

Re: Is any movement here?

Discussion continued on ffado-users mailing list.

Unusual XRUNs

Hello everybody.

I am a new user of FFADO. Right now I am experimenting with AudioFire 2, FFADO and JACK. I experience some unusual XRUNs: they are comparably rare (about one XRUN in five minutes) but very long (every one is about 790 milliseconds). Their length is quite stable.

I am using Gentoo Linux. Some of my setup follows:

  • uname -r = "2.6.33.5-rt23" (rt-sources from pro-audio);
  • jackd --version = "jackd version 0.118.0 tmpdir /dev/shm protocol 24";
  • ~/.jackdrc = "/usr/bin/jackd -R -P48 -dfirewire -r44100 -p256 -n4";
  • libffado version = 2.0.0 (no 2.0.1 appeared in pro-audio overlay yet, so I decided to wait a bit);
  • rtirq installed and running; RTIRQ_NAME_LIST="rtc ohci1394 snd usb i8042";
  • computer: Lenovo ThinkPad T400 laptop, ACPI is enabled;
  • desktop environment: KDE 4.3.5.

Some time before I tried 2.6.33.3-rt19 kernel, also from pro-audio. Then it was even more strange: an XRUN of a very precise length (about 785 ms with accuracy of 0.5 ms) occured every 128 seconds.

XRUNs seem to occure no matter what user does and what software uses JACK; it happens even if JACK is running alone!

I have almost no idea what generally happens. Could anybody please give a hint?

2.1 beta/release dates?

I was just wondering when 2.1 is going to be released. I've looked for a roadmap or release info but can't find anything.

Re: 2.1 beta/release dates?

I am not sure about when we might start to consider starting a 2.1 beta cycle leading up to a 2.1 release. Although it's been mentioned in passing on the devel mailing list I don't recall any firm timetable being discussed. Perhaps if Pieter sees this thread he can respond with his views at this point.

Which specific features are you looking for in the 2.1 release? Or are you just curious?

A quick check of the bug tracker still shows a large number of open issues earmarked for fixes in FFADO 2.1. If this is an accurate picture of where we're at then it would seem that a 2.1 release is a little way off yet.

From a personal point of view I would like to complete support for 2 new MOTU interfaces before 2.1 is released (they being the 8pre and the 828mk3). I would also love to get at least preliminary support for the RME Fireface-400 (and maybe the 800 too) working. Whether any or all of this happens depends very much on how long it will be before 2.1 is released and how much time I get to work on ffado over the next few weeks/months.

motu traveler Mk3

If I can assist in any way to enable support for the MOTU traveler Mk3 I will try to assist,
I have a traveler Mk3 and a laptop dual bootable with Vista and AVLinux.
http://www.bandshed.net/AVLinux.html

If you can provide instructions on what can be done to find out any specifics about the traveler,
I am an old unix system administrator and a resonably competent windows user.

motu traveler Mk3

I accept your help and any other help that anyone of you could give me.

I've got a Motu Traveller, and I spent all my afternoon to try to configure it.

I'd like to record vinyl by firewire. I install ffado-mixer, jack, gramofile and audacity... Nothing

It seems everything all right, but i cannot choose my analogic firewire source... May be that everything is not all right

Thank you

Re: motu traveler Mk3

There are a lot of variables to tie down here. Most importantly, which MOTU Traveler do you have - the original "Traveler" or the more recent "Traveler Mk3" (which is what this thread originally was referring to)? This is important because at present only the original Traveler will work with ffado. The "Traveler Mk3" will work eventually but I can't give a timeline on that.

Next up, could you let us know how you went about installing ffado and jack? That is, which versions did you download and what commands did you use? It would also help to know which Linux distribution you were trying this on.

Finally (for now), how were you starting jackd? If using a command line, what was it? Does jackd exit with an error message - if so, what was that message?

To give some brief background, ffado provides a library which jackd can use to communicate with a firewire audio interface which exposes the audio input/output channels to jack-enabled applications. ffado-mixer uses the same library to provide access to the on-board mixer capabilities of the interface. jackd/ffado and ffado-mixer are independent: you don't need to start one before the other will run.

For MOTU interfaces which are known to work with ffado, jackd/ffado and ffado-mixer generally work out of the box - that is, once compiled/installed things just work. So as you say, maybe something isn't quite right on your system.

Once we've nailed some of these details me might be in a position to work out what might be going wrong in your case.

Re: motu traveler Mk3

Thanks for the offer.

Ideally in order to easily support the Traveler Mk3 I really need physical access to the device for at least some time. This allows me to capture control information from it which in turn enables development of protocol knowledge. However, this is usually not feasible since I'm in Australia and most others in the world are not. An alternative approach is therefore needed. A couple of months ago I was fortunate to be loaned an 828mk3 which has enabled to to work out the basic idea behind MOTU's "mark 3" protocol (it differs considerably from the protocols used with earlier interfaces, which is why ffado as it stands doesn't work with the mk3 devices). Given that all mk3 devices are likely to be very similar in structure this gives us a pretty good base to build on. There's also a possibility that I can borrow the 828mk3 again at some point, which will help verify the still-to-be-written mixer interface.

So with all that in mind it might be possible to get the traveler mk3 working with ffado with some educated guesswork and some experimentation. Since doing so will require a lot of followups it is probably a good idea to take the discussion off the forum and onto email. You can pick my address up from posts in the ffado-dev mailing list (search for jwoithe). If you have difficulties finding it pop a followup onto the forum and I'll work out some other way for you to get my email address. Unfortunately posting it directly here will just add to my spam torrent. :-(

The most fundamental thing I need to know is how to identify a Traveler mk3. There are two possibilities here. Firstly there's a fairly old program called gscanbus. If you can get this working under Linux, run it with the traveler attached, right-click on the node which represents the traveler and let me know all the information which appears in the resulting window. Another alternative is to grab "motuprobe" (google motuprobe.c for the URL. Compile it as described at the top of the file and run it with the traveler mk3 attached. Send me the output.

The above is the brief outline of the process required to find what uniquely identifies the traveler mk3. It's almost certain that things won't go smoothly, so if that happens please email me and we'll work through the issues.

The other preparatory thing you can do for me is to provide me with a definitive list of which channels are available at the 1x, 2x and 4x sample rates. Finally it would be good to know what cuemix controls are provided by the traveler for each of the input/output types (eg: analog ins might have trim gain, pad switches, EQ, compressor, limiter while ADAT inputs might have only EQ, compressor and limiter).

Thanks again for your offer to help with the traveler mk3. Let's see how far we can get.

Thanks for the info. I have

Thanks for the info. I have a TC Konnekt 6 and if I understand it right it will be supported in 2.1. I've seen that some people have it working with the trunk so I'll probably do that.

Re: 2.1 beta/release dates?

I don't have time for FFADO at present, so I'm not very likely to initiate a 2.1 release any time soon. As Jonathan indicated there seem to be some issues that are to be resolved before 2.1 can be considered.

One thing that might happen is a 2.0.1 release that introduces some small changes that make it easier for the PulseAudio developers to write a backend for FFADO. If I have some time for FFADO that's probably the first thing I'll do.