As regards latency – this is more a feature of the Firewire isochronous protocol and what your whole hardware stack is capable of. The first issue – that of the number at the start of the name – is indeed related to the serial number of the interface. Grama Lambo Luver I still have more testing to do with the Audiofire 8 device to make sure I can count on it for recording. I believe that the onboard DSP relates to the digital channel mixing available within the device, and you can play with that via the FFADO audiofire console application. Hopefully the above is useful. Another approach would be to write a small program that generates the dbus messages – an automated ffado-mixer type thing for example.
|Date Added:||7 June 2012|
|File Size:||38.30 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
My soundcard, by default – will send each input port to it’s corresponding output port. The ffado-mixer GUI is just a graphical front end to the ffado-dbus-server program which is responsible for sending mixer commands to the AudioFire.
Audiofie audio in out end of the Audiofire is all working fine straight out the box with ffada 2.
Well I got my audio interface today, and so far, so good! This is thanks to Takashi Sakamoto. You can download v 4. You should perform the flash update on an XP machine, since the only driver available for Wudiofire 7 is v 5. Hi there, I am new to this forum, I was linked to this topic from linuxmusicians and it is very interesting to see you got it running.
I hope to get some help here I have an AF12 as well but so far I have not gotten it to work. There are two issues at play with the names: I am looking to buy an audio interface for Linux, and was wondering if anybody has had experience with the Echo Audiofire 8.
For more info see http: I don’t have that ieee cord problem.
I am not sure the ffado mixer is working properly, it does not seem to be mixing but it may be that I don’t quite know how to use it yet. You could just power it down then back up instead of unplugging then plugging it back in. The trouble is that high end multi converters cost a fortune.
Since the only thing that really changed was the new FW stack, I’m assuming aydiofire is the cause Another approach would be to write a small program that generates the dbus messages – an automated scho type thing for example. I have a similar problem: Perhaps the older Ubuntu didn’t install the proprietary driver on your hardware, or maybe it shipped a different driver altogether.
It was just the firewire thing. I have installed the version of ffado in the debian experimental repository and it did not fix the sample rate issue. I don’t know what drives Ubuntu ships, but it’s not unheard of for video drivers to adversely affect ffado.
It looks like it is enumerating the ports based on the serial number of audiofiee AudioFire 12; I’d try contacting whoever wrote that driver and see if it’s something that could be adjusted on their end. Grama ffado is fully supported on the the new stack with Kernel 2. Should I downgrade the firmware to 4. I think I installed the XP driver version 4. Finally, with recent eccho and anything from 2. If your system is running such a driver and it’s feasible to temporarily switch to another this might be a good thing to test.
I’m guessing there must be something like this around though, and if so then this should be feasible.
At the current moment i am looking to build a home studio based on Linux to record full aaudiofire. It is not currently known why this rate is no longer supported.
I can see how the input ports are routed to each out and turn that off. My understanding is that the use of port aliases varies between different jack applications though – some use them while others ignore them. Basically, you audiofird want to buy something with a Texas Instruments TI chipset.
There is a bug in the firmware which affects working at high sample rates