FFADO 2.0.1 'Summertime' released

  • warning: Illegal string offset 'data' in /home/ffado/ffado.org/includes/tablesort.inc on line 110.
  • warning: Illegal string offset 'data' in /home/ffado/ffado.org/includes/tablesort.inc on line 110.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.
  • warning: Creating default object from empty value in /home/ffado/ffado.org/modules/spam/spam.module on line 488.

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.

AttachmentSize
libffado-2.0.1.tar.gz758.95 KB

Comment viewing options

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

Recommended firewire interfaces

I allready have a stationary home studio, but now I would like to have a more mobile studio - meaning a laptop and a FW sound card.

A list of laptops with FW ports that will work - and a list of interface cards with FW ports that has proved to be reliable would be most helpful.

Best regards,

Jens.

Re: Recommended firewire interfaces

Hi Jens

We don't recommend specific laptops because there are just too many to keep track of; instead we concentrate on the chipset used in the firewire controller - something you should be able to track down in a laptop's specification. Generally speaking, any firewire interface which utilises a chipset from Texas Instruments ("TI") should be good to go. Most manufacturers of audio interfaces publish their own recommended list of chipsets and TI will be found on all of them. My experience has been exclusively with TI chipsets and they have never given me any trouble.

Having said that, there are other chipsets out there which work. We have a list of good/bad chipsets on our wiki, but unfortunately due to circumstances beyond our control this is currently unavailable (our hosting provider changed something which broke our wiki and we're still trying to work out the fix). Going from memory, recent Agere/LSI chipsets seem to be a reasonable alternative. Very recent VIAs may work (older ones are no good). O2-micro are generally troublesome.

A snapshot of our host controller information page from July 2011 can be found on the wayback machine:
http://web.archive.org/web/20110703081913/http://subversion.ffado.org/wi.... This should give you a good idea of what's good. Let us know if you have further questions.

Thanks a lot -

your link was very useful.

Jens

Re: Thanks a lot -

You're more than welcome. For what it's worth, the issues with our wiki have now been resolved so the master copy of the host controllers page is now available via subversion.ffado.org.

Hello! Thank devs for your

Hello! Thank devs for your work!
Have a little question: I want to buy Infrasonic WINDY6 and I don't know will it run on Linux. Can someone tell something about WINDY6 devices running on GNU/Linux systems?

Infrasonic windy 6 and FFADO

HI! A have a infrasonic windy 6! It's perfectly works with FFADO in linux! I even can says that windows drivers have a bugs that not appears in linux.

ffado-mixed not supports volume level regulation for this card currently, but IMHO it's not important when u use it in studio environment, like jack, audacity, ardour, etc.

It's a perfect card and It's a one card with 192KHz IN and OUT on SPDIF that i can found with price < $1000!

No daisychaining devices, and name change for rtirq

As per the ieee1394 wiki, daisychaining devices is not yet supported on the new stack:
https://ieee1394.wiki.kernel.org/index.php/Juju_Migration#New_stack_not_...
I tested this, they're right, only one device at a time works on the new stack.

Also, when using the new firewire stack, a realtime kernel, and the rtirq script, it is necessary to change the firewire device name in the script's config file (/etc/default/rtirq) from ohci1394 to firewire ,otherwise the script will not find your firewire card.

Other than not being able to daisychain, the new stack is working well here. (PreSonus Firepod). CPU usage is observably lower.

And daisy-chaining is being

And daisy-chaining is being worked on. Next kernel (and libraw releases) will have this working...

It works now

Using kernel 2.6.36 and libraw1394 v2.0.6, daisy-chaining now works on the new stack. Good work everyone!

PD and JACK stop and error after minutes with Echo Audiofire 4

Hi,

I dont know to use my echo audiofire 4 in linux.
I have libffado,etc, but jack and music-puredata stop after a few minutes....

Please to help me how to use/install on puredyne(based on ubuntu) 9.11.

Thanks

Thank you for having

Thank you for having clarifying !

FFADO 2.0.1

Thank you to all for this new version !
The raw1394 module seems still necessary for this new version.
Isn't it?

Kind regards,

CedricR

No raw1394-module

The exact meaning of "runs on the new stack" is "no more raw1394, ohci1394 and ieee1394 modules needed"...

No raw1394-module

I am agree with you, but when I launch ffado-diag the old firewire stack (raw1394) seems required:

FFADO diagnostic utility 0.1
============================
(C) 2008 Pieter Palmers

=== CHECK ===
Base system...
kernel version............ 2.6.34-ARCH
FIXME: implement test for RT kernel
RT patched............... False
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
Prerequisites (dynamic at run-time)...
gcc................ gcc (GCC) 4.5.0 20100610 (prerelease)
g++................ g++ (GCC) 4.5.0 20100610 (prerelease)
PyQt............... sh: pyuic : commande introuvable
jackd.............. no message buffer overruns
path............. /usr/bin/jackd
flags............ -ljack
libraw1394......... 2.0.5
flags............ -lraw1394
libavc1394......... 0.5.3
flags............ -lavc1394 -lrom1394 -lraw1394
libiec61883........ 1.2.0
flags............ -liec61883 -lraw1394
libxml++-2.6....... 2.30.1
flags............ -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0
dbus-1............. 1.2.24
flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 -lpthread -lrt
Prerequisites (static at compile-time)...
gcc................ gcc (GCC) 4.5.0 20100610 (prerelease)
g++................ g++ (GCC) 4.5.0 20100610 (prerelease)
PyQt............... sh: pyuic : commande introuvable
jackd.............. sh: jackd : commande introuvable
path............. which: no jackd in (/bin:/usr/bin:/sbin:/usr/sbin:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core)
flags............ Package jack was not found in the pkg-config search path.
libraw1394......... 2.0.5
flags............ -lraw1394
libavc1394......... 0.5.3
flags............ -lavc1394 -lrom1394 -lraw1394
libiec61883........ 1.2.0
flags............ -liec61883 -lraw1394
libxml++-2.6....... 2.30.1
flags............ -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0
dbus-1............. 1.2.24
flags............ -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -ldbus-1 -lpthread -lrt
Hardware...
Host controllers:
09:03.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a] (prog-if 10 [OHCI])
Subsystem: Sony Corporation Device [104d:9005]
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:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 1995.083
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida tpr_shadow vnmi flexpriority
bogomips : 3991.42
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
stepping : 13
cpu MHz : 1995.083
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida tpr_shadow vnmi flexpriority
bogomips : 3991.24
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

Configuration...
IRQ information
Hardware Interrupts:
--------------------
IRQ 0: PID: None, count: [240629, 240629], Sched None (priority None), drivers: ['timer']
IRQ 1: PID: None, count: [2453, 2453], Sched None (priority None), drivers: ['i8042']
IRQ 8: PID: None, count: [0, 0], Sched None (priority None), drivers: ['rtc0']
IRQ 9: PID: None, count: [2689, 2689], Sched None (priority None), drivers: ['acpi']
IRQ 12: PID: None, count: [64, 64], Sched None (priority None), drivers: ['i8042']
IRQ 14: PID: None, count: [10843, 10843], Sched None (priority None), drivers: ['ata_piix']
IRQ 15: PID: None, count: [0, 0], Sched None (priority None), drivers: ['ata_piix']
IRQ 16: PID: None, count: [65337, 65337], Sched None (priority None), drivers: ['uhci_hcd:usb3', 'yenta', 'nvidia']
IRQ 17: PID: None, count: [68, 68], Sched None (priority None), drivers: ['firewire_ohci']
IRQ 18: PID: None, count: [7, 7], Sched None (priority None), drivers: ['ehci_hcd:usb1', 'uhci_hcd:usb7', 'tifm_7xx1']
IRQ 19: PID: None, count: [25893, 25893], Sched None (priority None), drivers: ['uhci_hcd:usb6']
IRQ 21: PID: None, count: [0, 0], Sched None (priority None), drivers: ['uhci_hcd:usb4']
IRQ 23: PID: None, count: [1, 1], Sched None (priority None), drivers: ['ehci_hcd:usb2', 'uhci_hcd:usb5']
IRQ 29: PID: None, count: [38675, 38675], Sched None (priority None), drivers: ['ahci']
IRQ 30: PID: None, count: [6022, 6022], Sched None (priority None), drivers: ['sky2']
IRQ 31: PID: None, count: [0, 0], Sched None (priority None), drivers: ['iwlagn']
IRQ 32: PID: None, count: [298, 298], Sched None (priority None), drivers: ['hda_intel']

Software Interrupts:
--------------------

=== REPORT ===
FireWire kernel drivers:

The new FireWire kernel stack is loaded.
This stack is not supported by FFADO. Please use the old stack.

Could you help me, please ?

CedricR

FFADO 2.0.1 really works on

FFADO 2.0.1 really works on the new stack!

Sorry that I missed that part in the ffado-diag script. But actually trying to run ffado on the new stack will tell you that I am not lying to you...

I do not doubt of what you said

I do not doubt of what you said but could help me to find where is problem in my config, please ?

Sincerely,

CedricR

FFADO 2.01 breaks compatibility with MOTU896HD

Hi all, after installing the new libffado (2.0.1+svn1856-1) on Debian Testing or Sid, ffado-mixer stop working complaining about the object Motu ( I think it mistakes the old 896HD with the mk3's traveller or 828. Also, if i try to launch qjackctl with the firewire driver, it really never works anymore, and i can't even turn on the timer. Please check it because i fear that when trying to add new cards to the driver you broke compatibility with older ones.

I can provide more information about the debug messages if you need.

Your sincerely.

Re: FFADO 2.01 breaks compatibility with MOTU896HD

In order to progress this further I really need to see the error messages generated by ffado-mixer. Could you try running ffado-mixer from a command line window and let me see the last 20 or so lines of output please?

I also need to know exactly which version of ffado you are running. You say you put the "new libffado" onto Debian and qualified this by saying "2.0.1+svn1856-1". This confuses me since svn 1856 applies only to the "trunk" branch in svn, not the 2.0.1 branch. Have you instead grabbed svn 1856 from "trunk"? In short, how exactly did you go about installing ffado and what was it that you actually installed?
In addition, did you have another version of ffado installed before you installed this new libffado onto your system and what did you do with it (leave it, install over the top, remove it, etc)?

You mention a "timer" - what exactly are you referring to here? Which timer are you trying to turn on?

> I think it mistakes the old 896HD with the mk3's traveller or 828

I doubt it. There's really no architectural way that this could occur and if it did the symptoms would be different.

> because i fear that when trying to add new cards to the driver you broke compatibility with older ones

The last change to the MOTU code in the 2.0 branch was 6 months ago, and this was a fix to allow the 896HD to operate correctly. Correct operation of an 896HD with this change was confirmed at the time by another 896HD user. Since the release of 2.0 the 2.0 branch has not had any support added for new cards, so the above statement is clearly not true. There's something else going on which is a lot more subtle.

It sounds to me like there is a strange interaction going on between two different versions of ffado installed at the same time. Hopefully the answers to the above questions might go some way towards resolving things one way or another.