[PlanetCCRMA] Qjack problem
nando at ccrma.Stanford.EDU
Tue Mar 16 18:56:43 PDT 2010
On Wed, 2010-03-17 at 00:42 +0000, clifffiedler at comcast.net wrote:
> I think I have an incompatibility. My copy of QjackCtl will not
> communicate with jackd properly.
> I have:
> =====> uname -a
> Linux firewire.ccc.hsd1.comcast.net
> 2.6.33-1.rt7.1.fc12.ccrma.x86_64.rt #1 SMP PREEMPT RT Fri Mar 12
> 16:53:00 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
> =====> rpm -qa | grep jack
> =====> rpm -qa | grep ffado
> =====> rpm -qa | grep 1394
> The problem is that Qjack tries to start jackd (unsuccessfully) with:
> # jackd -R -dfirewire -dhw:0 -r48000 -p1024 -n3
> jackdmp 1.9.4 ...
> Unknownage with option 'd'
> Options for driver 'firewire': ...
> but jackd does not like the -d in front of hw:0 . If I type on a
> command line (omitting the -d):
> jackd -R -dfirewire hw:0 -r48000 -p1024 -n3
What happens if you ommit hw:0?
jackd -R -dfirewire -r48000 -p1024 -n3
I don't think there is a -d option for the firewire driver in jackd.
Try setting "Interface" to "(default)" when you have selected "firewire"
for the "Driver". It seems to work here in fc11 (with no firewire card
attached but at least the command line does not include a -d hw:0).
> then jackd starts normally. If I then tell Qjack to start jackd, it
> finds jackd already running and controls it just fine from then on. I
> can start japa and ardour and patch them to my Edirol FA-101 in the
> Qjack connect window (it all works great!). Qjack will also stop
> jackd correctly.
> Have I got the wrong version of something? Did jackd forget his
> interface options?
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
More information about the PlanetCCRMA