From: FFADO <ffa...@ff...> - 2010-01-04 00:48:20
|
#247: 896HD only successfully connects in jackd at 192000 -------------------------------------+-------------------------------------- Reporter: sireasoning | Owner: jwoithe Type: bug | Status: assigned Priority: major | Milestone: FFADO 2.1 Version: FFADO 2.0-rc2 (1.999.42) | Resolution: Keywords: | Device_name: Motu 896HD -------------------------------------+-------------------------------------- Comment (by jwoithe): Replying to [comment:13 jwoithe]: > You shouldn't need to recompile jackd or anything else at this stage - only ffado itself. To be consistent with the rest of your system you probably want to install the new ffado in the same general places as the existing one is in. So do {{{ scons PREFIX=/usr }}} > when configuring/compiling. When you do "scons install" this should overwrite the existing ffado things with the new version. However, to make sure the libffado libraries have done the right thing you might want to look in /usr/lib/ (as you did before), remove any of the old libffado files and make sure the symlinks are pointing to sensible targets. As pointed out by Arnold in an email to the user/devel lists on 31 Dec 2009, the above is not quite right when upgrading a system from a 2.0-rc release to the 2.0.0 release (or trunk). The problem is that on systems which ship a pre-2.0 FFADO release candidate, jackd links to libffado.so.1. FFADO 2.0.0 (and trunk) instead create libffado.so.2, so installing these won't install anything that will be used by jackd and jackd will continue to use the old libffado. A short-term solution, as suggested by Arnold, is remove libffado.so.1 and create a symlink of this name to libffado.so.2 ("rm libffado.so.1 ; ln -s libffado.so.2 libffado.so.1"). A more permanent solution on these systems might be to recompile jackd against the new libffado. Of course once distributions pick up the new FFADO release none of this trickery will be required. In relation to the system presently being discussed, this library version issue is probably going to be an issue. Double check /usr/lib/, and if libffado.so.1 does not eventually refer to the new libffado provided by the 2.0.0 compilation the symlink trick noted above would be the way to go. -- Ticket URL: <http://subversion.ffado.org/ticket/247#comment:24> FFADO <http://subversion.ffado.org/index.fcgi> Free Firewire Audio Drivers |