Ardour insists I use ALSA instead of Freebob/FFADO

Ardour i686 (from Hardy Heron UBUNTU) will NOT start JACK with the parameters specified on on the Audio Setup tab. When I pick FFADO, it launches ALSA. From the command line I can do jackd -d freebob and it will startup just fine, see the FP10 device and function. But when I start Ardour 2.3, it insists on launching a NEW ardour running ALSA. What is going on? Why is it happening?

I’ve wasted a full day trying to get a working Ardour for something I need to have finished by Tuesday.

jackd version 0.109.2 tmpdir /dev/shm protocol 22

Ardour/GTK 2.3
(built using 3029 and GCC version 4.2.3 (Ubuntu 4.2.3-1ubuntu2))

Ok, new information, but still no answer, here is the output I’m getting, I bolded the key parts:

mark@render:~$ sudo ardour2
WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with ‘ulimit -l’, and it is normally controlled by /etc/security/limits.conf
Ardour/GTK 2.4.1
(built using 3343 and GCC version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2))
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.
loading default ui configuration file /usr/local/etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /root/.ardour2/ardour2_ui.conf
Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /root/.ardour2/surfaces/:/usr/local/lib/ardour2/surfaces/
ardour: [INFO]: Control surface protocol discovered: “Mackie”
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
JACK COMMAND: /usr/local/bin/jackd -p 20 -T -d freebob -n 2 -r 44100 -p 1024
no message buffer overruns
jackd 0.109.2
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 …
creating alsa driver … hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
loading bindings from /usr/local/etc/ardour2/mnemonic-us.bindings
Loading session /home/mark/WholeDemo using snapshot WholeDemo (2)
Loading history from ‘/home/mark/WholeDemo/WholeDemo.history’.

**** alsa_pcm: xrun of at least 0.095 msecs

I discovered I had a .jackdrc file that had alsa in it, so I deleted it. Then discovered that root had one, but it contains the freebob params listed above. What is going on?

Nothing about the versions of jack or ardour have changed although I did recompile ardour after making sure all other version of jack were completely gone from the machine.

I can run jackd with the command line like so:
mark@render:~$ sudo bash ~root/.jackdrc
no message buffer overruns
jackd 0.109.2
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 …
Freebob using Firewire port 0, node -1
libiec61883 warning: Established connection on channel 0.
You may need to manually set the channel on the receiving node.
libiec61883 warning: Established connection on channel 1.
You may need to manually set the channel on the transmitting node.

and it does what is expected.

Go into /etc/security/limits.conf and change these -
@audio - rtprio 50
@audio - nice -10

to this-
@audio - rtprio 99
@audio - nice -19

and add these below
@audio hard memlock unlimited
@audio soft memlock unlimited

Then save.

This will take care of this Warning you are getting and it will help jack.

“WARNING: Your system has a limit for maximum amount of locked memory!
This might cause Ardour to run out of memory before your system runs out of memory. You can view the memory limit with ’ulimit -l’, and it is normally controlled by /etc/security/limits.conf”

Alright, did that and surprisingly it helped (I don’t really understand why (I had the memlock limit at 512,000K) but what the heck.

Now I’m onto the next problem (which I solved, but am documenting here for anyone else that runs into it:

mark@render:~$ sudo ardour2 WD2
Ardour/GTK 2.4.1
(built using 3343 and GCC version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2))
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.
loading default ui configuration file /usr/local/etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /root/.ardour2/ardour2_ui.conf
Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
loading user configuration file /root/.ardour2/ardour.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /root/.ardour2/surfaces/:/usr/local/lib/ardour2/surfaces/
ardour: [INFO]: Control surface protocol discovered: “Mackie”
powermate: Opening of powermate failed - No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control protocol Tranzport not usable
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
canonical, use /home/mark/WD2
JACK COMMAND: /usr/local/bin/jackd -p 128 -R -P 60 -T -d freebob -n 2 -r 44100 -p 512
no message buffer overruns
jackd 0.109.2
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 …
Freebob using Firewire port 0, node -1
loading bindings from /usr/local/etc/ardour2/mnemonic-us.bindings
Loading session /home/mark/WD2 using snapshot WD2 (1)
Loading history from ‘/home/mark/WD2/WD2.history’.
libiec61883 warning: iec61883_cmp_create_p2p_output: Failed to set the oPCR[0] plug for node 0.
FreeBoB ERR: Could not start streaming threads
LibFreeBoB ERR: Could not do CMP for connection 0
DRIVER NT: could not start driver
cannot start driver
mark@render:~$

Doesn’t matter if I run SUDO or not, I get this error.

Turns out in this case that Jack isn’t freeing up resources correctly, and if I cycle the power on the Firepod device, it gets all happy on me.

So, maybe tomorrow, I can actually start doing the work I was trying to do 2 days ago…

Hello…
How could I change control device hw:0 for hw:1 in Ardour?
I see than Ardour run JACK COMMAND with hw:0 only
I have and Audigy SZ working OK

Thanks

In the audio settings tab is a box where you can select the hw interface. You would change it there, assuming you are having Ardour start Jack. Otherwise if you are in QJackCTL, there is a similar box in the “Setup” window.

   Seablade

To use firewire, make sure that you have access to /dev/raw1394 - I did

sudo chmod ugo+rw /dev/raw1394

This works but doesn’t seem to get saved across reboots.

Thanks,
Now I have working Ardour… I did the following:

in a terminal root .

$:/ qjackctl

In this configure hw:1 and start (icon) then in another terminal root

$:/ ardour2 &

this work fine for me.

now I have a problem with Jack and my other sound card, in my other sound card Jack only can configure playback or capture not boot (Duplex). when I put Duplex there isn’t sound. and Jack’s message windows say a lot of

**** alsa_pcm: xrun of …
**** alsa_pcm: xrun of …
**** alsa_pcm: xrun of …

who have the same problem?
any solutions?

thanks