Jack only connects at 96kHz

Hey everyone,

Recently picked up an Edirol FA101, and I have it connected through FFADO. It connects, and works great, as long as it’s set to 96kHz. Any other setting and it fails to connect, with the following output:

08:28:31.579 Startup script... 08:28:31.580 artsshell -q terminate sh: artsshell: not found 08:28:31.984 Startup script terminated with exit status=32512. 08:28:31.984 JACK is starting... 08:28:31.984 /usr/bin/jackd -P 70 -R -P70 -dfirewire -dplughw:0 -r48000 -p1024 -n3 08:28:31.987 JACK was started with PID=2057. no message buffer overruns jackd 0.116.1 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. 00625827186: (ffado.cpp)[ 92] ffado_streaming_init: libffado 1.999.43 built Sep 17 2009 20:03:51 firewire ERR: Error creating FFADO streaming device cannot load driver module firewire no message buffer overruns 08:28:32.082 JACK was stopped successfully. 08:28:32.083 Post-shutdown script... 08:28:32.084 killall jackd jackd: no process found 08:28:32.504 Post-shutdown script terminated with exit status=256. 08:28:34.035 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Any thoughts on what I might be doing wrong?

Thanks,

Herb

Check in with the FFADO folks on this. There are some cards that have separate control of the sampling rate that must be switched independently in ALSA, it wouldn’t surprise me if that was the case with specific cards and FFADO as well, particularly those they don’t have documentation. In which case the card would only operate at whatever the last set sample rate is until it is reset. However keep in mind this is a complete guess and could be absolutely worthless. The FFADO folks would be your best resource on this.

  Seablade

Thanks for the suggestion. Going to have a look around the ffado list for clues.

I’ve been messing around with settings, this morning, and found that jackd starts just fine at the command line:

/usr/bin/jackd -R -P70 -dfirewire -r48000
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver …
06100846456: (ffado.cpp)[ 92] ffado_streaming_init: libffado 1.999.43 built Sep 17 2009 20:03:51

So it might just be how qjackctl is communicating to it. Just for fun, I might try compiling the latest ffado version. I’m running Puredyne, which is based on Karmic, so things are getting a bit old.