Hi,
I compiled Ardour 2.1 on the current Gutsy Beta. When I launched Ardour and opted to create a new session test001, it did start, but the menu option to add a track was greyed out, as were most of the other options. In addition, when I chose “Add existing audio”, Ardour crashed. What can be wrong here?
Regards,
Artem Vakhitov
Oh, forgot to mention: I have Intel onboard soundcard (i915). I know, I know, kinda lame, but this card did work with the earlier versions of Ardour. Also, while I have Ubuntu’s stock “rt” kernel installed, I didn’t set Jack to run in realtime, since Ardour couldn’t connect to Jack with the realtime option set.
Here’s the not-so-interesting console log just in case:
temcat@eden:~$ 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.1
(built using 2496 and GCC version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2))
Copyright © 1999-2007 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 /etc/ardour2/ardour2_ui_default.conf
Configuration::pack_canvasvars () called, canvas_colors.size() = 82
ardour: [INFO]: Loading ui configuration file /etc/ardour2/ardour2_ui_dark.rc
theme_init() called from internal clearlooks engine
loading system configuration file /etc/ardour2/ardour_system.rc
ardour: [INFO]: Using SSE optimized routines
ardour: [INFO]: looking for control protocols in /home/temcat/.ardour2/surfaces/:/usr/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 surface protocol discovered: “Generic MIDI”
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
jackd 0.103.0
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|256|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 256 frames, 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: 32bit little-endian
ALSA: use 2 periods for playback
loading bindings from /etc/ardour2/ardour.bindings
Loading session . using snapshot test001 (1)
glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: basic_string::_S_construct NULL not valid
aborting…
Aborted (core dumped)
temcat@eden:~$ subgraph starting at ardour timed out (subgraph_wait_fd=14, status = 0, state = Triggered)
we need a backtrace as described here: http://ardour.org/debugging_ardour
what compile options did you use?
OK, I will prepare a backtrace a bit later.
The only compile option I used was to set /usr prefix.
Nevermind, the problem went away after a recompile with no changes whatsoever. Weird.