From: FFADO <ffa...@ff...> - 2014-06-19 23:50:46
|
#360: Make echo audiofire 8 and audiofire 12 work with recent firmwares -------------------------------------+-------------------------------------- Reporter: picander | Owner: Type: bug | Status: reopened Priority: waiting for volunteer | Milestone: Indeterminant (awaiting volunteer) Component: devices/fireworks | Version: FFADO SVN (trunk) Resolution: | Keywords: fireworks, ubuntu, studio, audiofire Device_name: Echo Audiofire 12 | -------------------------------------+-------------------------------------- Comment (by jwoithe): Thanks for testing with your AF12 and the report, ruxxes. Could you please tell us the version number of the firmware you have loaded into your AF12? You mention the mixer failing to change the sample rate. Is sample rate the only parameter which doesn't work, or are all settings pretty much unusable? Can you use jackd to start audio streaming? Note that this operates completely independently of ffado-mixer. This is interesting given that Andrew Hately (see comment:25) reports his AF12 to work fine with what is stated to be the latest firmware. The apparent contradiction between his interface and yours is unexpected. One thing which is worth double-checking is that there aren't any old FFADO files (such as libffado.so*) sitting on your system somewhere. These may be picked up by some components and not others, or new binaries (reporting the new version) may be linking against an older libffado; all this leads to confusing results. In particular, a distribution will install libffado.so* in /usr/lib/ while by default a source install will go in /usr/local/lib/. If you have libffado.so* in more than one area, there are two ways to deal with it. For a quick initial test you could try using "rm" to remove the older files. Alternatively, run "scons -c install" as root in your ffado source tree (to remove the svn install), then run "scons PREFIX=/usr" to configure FFADO to install over the top of the distribution-provided files in /usr/lib/, and finally "scons install" (as root) to do the new installation. An "ldconfig" as root wouldn't go astray at this point. BTW, I'm not sure "waiting for volunteer" is completely correct here for "priority" and "milestone". If we have someone who is familiar with the AF protocol who can determine what has gone wrong here and can post a description of what needs to be done to fix it, then these settings can remain - in this case we literally will be waiting for someone with an AF12 device to implement a fix for a well defined problem. At this stage Takashi is probably the only developer who ''might'' fall into this category, but he is very busy with the in-kernel streaming work for the AF series. On the other hand, all we know at the moment is that some commands which FFADO thinks should work are rejected by the device for unknown reasons. To determine those reasons we need more information about the device, and further work on this issue cannot progress until we have it. In this case, "waiting for device info" is a far more appropriate status. I will wait a few days to gauge feedback and see if Takashi responds. If further analysis does not appear in that time I'll be resetting the priority and milestone to "waiting for device info" to accurately indicate what is required in order to make further progress with this ticket. In the meantime ruxxes, feel free to post further information if you happen to come across it. -- Ticket URL: <http://subversion.ffado.org/ticket/360#comment:27> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |