[ardour-dev] Ardour2 won't start without sn-seq-midi

[Paul Davis]

On Sat, 2007-01-20 at 12:07 +0100, Christophe Combelles wrote:
> Hello
> 
> I'm starting with an empty .ardour2 config.
> Ardour2 doesn't start at all :
> 
> 
> ~$ ardour2
> Ardour/GTK 2.0beta11.1
>     (built using 1345 and GCC version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))
> Copyright (C) 1999-2006 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.
> Loading ui configuration file /usr/local/etc/ardour2/ardour2_ui.rc
> theme_init() called from internal clearlooks engine!
> /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:59: error: unexpected identifier 
> `animation', expected character `}'
> theme_init() called from internal clearlooks engine!
> loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
> loading user configuration file /usr/local/etc/ardour2/ardour.rc
> ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file 
> or directory
> ardour-2.0beta11.1: seq.c:2199: snd_seq_create_port: Assertion `seq && port' failed.
> Aborted
> -------------------
> 
> Now if I modprobe snd-seq-midi, it starts.  But should it absolutely depend on 
> this module ? If yes, shouldn't the use be warned about what to do?

its a good point. this happens because the system default configuration
file contains references to the ALSA sequencer. whether this is a good
idea or not is debatable, but it is clear that ardour should not abort
in this way. i will fix it. thanks for the information.

--p