|
From: Jonathan W. <jw...@ju...> - 2020-04-29 11:36:37
|
Hi Morgan On Wed, Apr 29, 2020 at 12:24:11PM +0100, Morgan Read via FFADO-user wrote: > I wonder if someone could confirm my worst nightmare... > > After seemingly going round in circles with qjackctl I decided to resort > to the command line to see what I could see - as if life was never > thus... Does this output from jackd indicate ffado/ firewire support is > not compiled in to my installed version...: > $ jackd --help > jackdmp 1.9.12 > ... > Available backends: > net (master) > alsa (master) > proxy (master) > netone (master) > loopback (slave) > alsarawmidi (slave) > dummy (master) If that's all the backends that are listed, then I agree that it seems the jackd binary presently on your system does not include the "firewire" backend. This is a little unusual in this day and age, but clearly it still happens. I don't have jackdmp (aka jack2) on my system so I can't confirm this directly. If your system included support for the "firewire" backend, I would expect to see a line reading "firewire (master)" based on the entries reported above. I'm not sure it's your worst nightmare, but it's certainly more than a little annoying. Which Linux distribution (and version) are you using? This will determine the best approach to use when resolving this issue. For example, on many distributions, uninstalling jackd in the normal way (notionally to make ready for a self-compiled version) needs to be avoided because a side effect will be to remove most of your multimedia software as well (since these packages depend on the jackd package that you're removing). Not having a jackd with the "firewire" backend available does explain why (as you mentioned in a previous post) selecting "firewire" in qjackctl didn't do anything useful. Regards jonathan |