I still have more testing to do with the Audiofire 8 device to make sure I can count on it for recording. Another thing which may be different is your video driver. Anything else will bring you a lot of misery. I have some experience with AVLinux in the past few years. The newer ones do. What did make Firewire just work for me was KXStudio.
|Date Added:||3 February 2018|
|File Size:||57.44 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
You must unplug it, then plug it back in while the user is audio logged on. And also are most PCI firewire cards supported in Linux?
Andrew, thanks for taking the time to post your experiences with the new code. Thanks for the reply. Thanks for your time! Who is online Users browsing this forum: Despite hours and days of messing with interupt configuration and stuff that I never really wanted to know, it would never just work and usually did not work at all.
[ubuntu] Echo Audiofire 12 – not working
I am looking to buy an audio interface for Linux, and was wondering if anybody has had experience with the Echo Audiofire 8. Should I downgrade the firmware to 4. I’m guessing there must be something like this around though, and if so then this should be audilfire.
The two are connected via dbus. It’s not just the audiofire device which includes serial numbers in port names: What is your installed version of libraw?
This would be my dream set up. This is used to ensure the generated port names are unique in the event that two or more identical interfaces are edho to the same computer. As regards latency – this is more a feature of the Firewire isochronous protocol and what your whole hardware stack is capable of.
It looks like it is enumerating the ports based on the serial number of the AudioFire 12; I’d try contacting whoever wrote that driver and see if it’s something that could be adjusted on their end.
Echo AudioFire 8 – Linux – Ardour
This approach was debated at length several years ago and it was decided that the above was the best way to go. As for the sample rate. PaulRH Prhunt You’d have to experiment to see if the aliases work for you in a sensible way. Also I’d recommend using a audio-oriented linux distribution rather ehco vanilla ubuntu.
Additionally, with the svn trunk, my Audiofire 12 has 13 audio connections and no midi connections, so I think there is some incorrect classifications going on but I’m not sure if that’s ffado or jack.
Any help would be greatly appreciated. I have a few general pieces of feedback for you though. I might try the Audiofire again with Linux because the digital side of the Layla is a slight problem. I do have access to a windows machine which I will use to flash the device if I do decide to make the purchase.
Anywho, this is can be remedied with and only with ffado-mixer afaik. I am not sure the ffado mixer is working properly, it does not seem to be mixing but it may be audiofier I don’t quite know how to use it yet. Another approach would be to write a small program that generates the dbus messages – an automated ffado-mixer type thing for example.
I monitor through Ardour. I am looking at purchasing it. The first issue – that of the number at the start of the name – is indeed related to the serial number of the interface. One thing I did notice is that you must wait till the system is up before plugging in the Audiofire 8.
Basically, you only want to buy something with a Texas Instruments TI chipset. I still have more testing to do with the Audiofire 8 device to make sure I can count on it for recording. I have access to any OS I need to do the flashing I am a computer science majorand I found the download links for audoifire drivers needed for flashing.