Ardour 2.8.14 starts JACK with driver incorrectly specified

To date, I have not been able to have Ardour successfully start JACK. Which has not been an issue because I simply use qjackctl start JACK prior to launching Ardour. I use an Echo Audiofire 8, a firewire device, running with FFADO.

I finally decided to look more closely at why this may be the case. I started Ardour (2.8.14 ardour.org build) from the console without a running JACK instance. I selected FFADO from the start menu JACK options and attempted to start JACK.

As I watched the console output, I realized that Ardour attempts to start JACK with the driver incorrectly specified in the JACK command line. So, instead of

jackd -d firewire

Ardour attempts to start JACK with

jackd -d ffado

which fails. Mixbus 2.2.0 also fails in a similar fashion, using “-d freebob” when FFADO is specified.

Can this be corrected (eg some setting) without a recompile of Ardour?

For reference, I include the console output below:

Ardour 2.8.14
(built using 13065 and GCC version 4.4.6)
Copyright © 1999-2008 Paul Davis
Some portions Copyright © Steve Harris, Ari Johnson, Brett Viren, Joel Baker

Ardour comes with ABSOLUTELY NO WARRANTY
not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This is free software, and you are welcome to redistribute it
under certain conditions; see the source for copying conditions.
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:85: error: unexpected identifier hint', expected character}’
loading default ui configuration file /opt/Ardour-2.8.14_13065/etc/ardour2_ui_default.conf
loading user ui configuration file /home/paul/.ardour2//ardour2_ui.conf
Loading ui configuration file /opt/Ardour-2.8.14_13065/etc/ardour2_ui_dark.rc
ardour: [INFO]: Ardour will be limited to 4096 open files
loading system configuration file /opt/Ardour-2.8.14_13065/etc/ardour_system.rc
loading user configuration file /home/paul/.ardour2//ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /opt/Ardour-2.8.14_13065/lib/surfaces
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: “Mackie”
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
NSD response -5 folder =
JACK COMMAND: /usr/local/bin/jackd -p 128 -R -P 60 -T -d ffado -n 2 -r 48000 -p 1024
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jackdmp 1.9.9.4
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
Unknown driver “ffado”

Thanks! Paul H

Thank you Paul. I wasn’t sure if it was just me not being sufficiently observant with available settings.

This has already been fixed in SVN and will show up in the next release (which may appear soon to also make available some important improvements in MIDI control interaction, among other things).