alex@dhcppc10:~$ ardour2
Ardour/GTK 2.8.2
(built using 5396 and GCC version 4.4.1)
Copyright (C) 1999-2008 Paul Davis
Some portions Copyright (C) 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.
theme_init() called from internal clearlooks engine
loading default ui configuration file /etc/ardour2/ardour2_ui_default.conf
loading user ui configuration file /home/alex/.ardour2/ardour2_ui.conf
Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /etc/ardour2/ardour_system.rc
loading user configuration file /home/alex/.ardour2/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
ardour: [INFO]: looking for control protocols in /home/alex/.ardour2/surfaces/:/usr/lib/ardour2/surfaces/
ardour: [INFO]: Control protocol Tranzport not usable
powermate: Opening of powermate failed – No such file or directory
ardour: [INFO]: Control protocol powermate not usable
ardour: [INFO]: Control surface protocol discovered: “Generic MIDI”
ardour: [INFO]: Control surface protocol discovered: “Mackie”
JACK COMMAND: /usr/bin/jackd -p 128 -T -d alsa -n 2 -r 48000 -p 1024 -d hw:0,0
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 ..
apparent rate = 48000
creating alsa driver … hw:0,0|hw:0,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: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
loading bindings from /etc/ardour2/mnemonic-us.bindings
Loading session /home/alex/test2 using snapshot test2 (1)
Loading history from ‘/home/alex/test2/test2.history’.

Here is the output for qjackctl. It just says:

alex@dhcppc10:~$ qjackctl
Suspending PulseAudio

thats all.

When I plug the guitar into the firewire solo the sound isn’t displayed in ardour (no level meters move when I play even though the clip light comes on on the device) but the device is shown on gscanbus and I think it’s shown in jack.

Here is a screen shot of the jack connections box:
http://tinypic.com/r/1zmingw/6

Note: I had to reboot so things may have changed from my earlier posts.

Jake Strickland

The file that gscanbus is looking for appears to be located at /usr/lib/gtk-2.0/modules/ – but it’s not clear to me where the link should be.

In re-reading your initial post it only seems to throw up the error for gsanbus, but allows it to function anyway.

(As an aside, we did some research on canberra – it’s designed to trigger event sounds in gnome. Irritatingly, it automatically hooks into virtually anything which produces a sound – ie it doesn’t just work with programs designed to work with it; rather it just takes over those sound duties. And it’s become a gnome dependency, so I’m not sure it would be easy to remove it – it’ll probably want to remove all sorts of other things like ubuntu-desktop, etc. It seems like the kind of nonsense garbage microsoft bloats their software with).

When you say, “I am unable to get Ardour to see any sound from the Firewire Solo.” what, exactly, do you mean? Do you mean that qjackctl’s Connections box doesn’t show any Ardour connections? Can you try running Ardour from the command line (ie: #ardour2) and post the terminal’s output? Also, try starting JACK/Ardour and then post a screenshot of the Connections box of qjackctl.

I’m wondering if canberra tries to hook into JACK and thereby blocks the connection between Ardour and JACK. Can you open qjackctl in a terminal and post the terminal’s output?

After doing the search for libcanberra files I came up with 37 files. Here are 3 screen shots of all the files:

http://tinypic.com/view.php?pic=s4yphx&s=6
http://tinypic.com/view.php?pic=23vay38&s=6
http://tinypic.com/r/2is8r9v/6

I am running this on a 1GHz i386 (kinda like the Kyle Wellwood of PC’s)

Here are some links:

https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/407660

(note that Alessio Igor Bogani calls it a “significant bug in Ubuntu” – Alessio is a key developer of the real time kernel)

http://ubuntuforums.org/showthread.php?t=1310225

http://ubuntuforums.org/showthread.php?t=1322074

It seems some of the problems were related to the proprietary NVidia driver and NVidia appears to have addressed this in subsequent driver releases.

For our systems, we are not comfortable enough with the status of the real-time kernel post-8.04 to even begin to consider “upgrading”.

Can you search your system for libcanberra-gtk-module.so? In case you’re unfamiliar how to do this, click “Places” on your panel, select “Search for Files…”, put “libcanberra” in the “Name contains” field, select “File system” from the “Look in folder” drop down and make sure the options include “Show hidden and backup files” and “Include other file systems” (just hit the “+Add” button and select from the drop down). Then hit “Find”. Let’s see if it’s on your system elsewhere, which we can then create a link to, which I’m hoping will solve the problem.

I have no idea why canberra should be required by JACK – it’s not required on our system, as we don’t have it installed and it’s not available in the 8.04 repositories without being specifically added. It does seem there’s some sort of bug in canberra, as there are plenty of reports of other programs having dependency issues with canberra.

As for 9.10 vs 8.04, I haven’t looked into the real-time issue for a while – as far as I know from prior research, there remains no way to enable real-time scheduling in anything beyond 8.04. We’ll check it out and advise.

You should still be able to set up your FireWire Solo on a post-8.04 version, you just won’t get the latencies you would with a real-time kernel/scheduling. Depending on what you’re doing, the latencies you get may work for you, or may not.

If I recall, it’s said that humans can’t pick up latencies below 16ms, but our opinion is that _any_ latency affects the “feel” of the song.

For example, when recording a guitar solo, the player is responding to the music and intending to place a note at a very particular location in time, which contributes to the “feel” of the song.

Ardour can compensate somewhat for latency, and there are other things you can do, such as simply move back the recorded track by an amount equal to the one-way latency.

What’s also important is how the guitar player in the example is listening to his/her guitar as he/she plays. If the sound of the guitar is being monitored at the track, there will be a gap in time between striking a note and hearing it struck. If monitoring the guitar “live” against the track, the note will sound “on” when played, but may sound “off” on the track, because the point in time when the guitarist struck the note is not the same point in time as when Ardour recorded the note being struck, vs the other tracks.

If, instead, you’re doing a lot of editing or recording digital instruments or samples or such, or splicing together bits and pieces here and there, you’ll never get that “real-time” feel anyway (tho you can approximate it). For example, notes which are “spot-on” the beat, every time, do not sound remotely natural. A human playing an instrument is much more nuanced.

Hope that makes some sort of sense!

When I started this, I simply downloaded the latest version of Ubuntu; did not see your reference to Hardy Heron (8.04) until wading into the weeds of all the replies on this site. I’d like to get the Solo working with Ubuntu Studio 9.10 if possible, but if you think I am heading for a brick wall, please go ahead and make the call for me to load 8.04.

Below is the output of:
#ls -l /etc/X11/Xsession.d/
total 56
-rw-r–r– 1 root root 1878 2008-06-24 19:05 20×11-common_process-args
-rw-r–r– 1 root root 102 2009-10-12 14:55 25ubuntustudio-menu
-rw-r–r– 1 root root 899 2008-06-24 19:05 30×11-common_xresources
-rw-r–r– 1 root root 187 2008-06-24 19:05 40×11-common_xsessionrc
-rw-r–r– 1 root root 1561 2008-06-24 19:05 50×11-common_determine-startup
-rw-r–r– 1 root root 197 2009-10-07 16:01 52libcanberra-gtk-module_add-to-gtk-modules
-rw-r–r– 1 root root 656 2009-10-23 03:49 55gnome-session_gnomerc
-rw-r–r– 1 root root 80 2009-10-15 05:16 60xdg-user-dirs-update
-rw-r–r– 1 root root 329 2009-10-26 02:42 70pulseaudio
-rw-r–r– 1 root root 381 2009-10-23 20:28 75dbus_dbus-launch
-rw-r–r– 1 root root 2307 2008-01-08 02:41 80im-switch
-rw-r–r– 1 root root 274 2009-08-23 22:17 90consolekit
-rw-r–r– 1 root root 642 2008-08-05 16:37 90×11-common_ssh-agent
-rw-r–r– 1 root root 166 2008-06-24 19:05 99×11-common_start

Below is a link to a screenshot with the results of searching Synaptic for “libcanberra” :

http://tinypic.com/r/9zn8qs/6

Thanks
Al

That’s interesting – we haven’t come across that error before.

Can you please post the output of:

#ls -l /etc/X11/Xsession.d/

Also, can you search Synaptic for “libcanberra” and report which files are installed (ie version number; full file name)?

I am a Linux newbie. Using Ubuntu Studio 9.10
I am unable to get Ardour to see any sound from the Firewire Solo.

gscanbus gives this message:
Gtk-WARNING **: Failed to load module “libcanberra-gtk-module.so”: libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Than shows the Solo connected. I am able to force bus reset but no joy.

I am in Vancouver Canada. If more convenient, please email me graham2128@gmail.com

Thanks!
Al