[ardour-users] [LAU] MIDI connections (BCF2000 <--> ardour)

Kevin Cosgrove kevinc at doink.com
Thu May 24 19:24:46 PDT 2007


On 24 May 2007 at 21:23, "Jesse Chappell" <jesse at essej.net> wrote:

> If you have the line in your ardour.rc where it uses the rawmidi
> device ("/dev/snd/midiC3D0") there's a good chance you will not also
> get it to work with the alsa seq device.  Therefore, you want one or
> the other lines in there, not both.  If ardour always puts in the seq
> line, even when you already have a port with the same name, that is a
> bug in ardour.

When running 2rc1 this is in my ardour.rc (grep'ing for "MIDI-port")

<MIDI-port tag="control" device="ardour" type="alsa/sequencer" mode="duplex"/>
<MIDI-port tag="mcu" device="/dev/snd/midiC3D0" type="alsa/raw" mode="duplex"/>
<MIDI-port tag="seq" device="ardour" type="alsa/sequencer" mode="duplex"/>

Then I start 2.0.2 and subsequently quit 2.0.2 which leaves this in 
my ardour.rc file, again grep'ing for "MIDI-port":

<MIDI-port tag="control" device="ardour" type="alsa/sequencer" mode="duplex"/>
<MIDI-port tag="mcu" device="ardour" type="alsa/sequencer" mode="duplex"/>
<MIDI-port tag="seq" device="ardour" type="alsa/sequencer" mode="duplex"/>

Whenever I try to put the mcu line specifying /dev/snd/midiC3D0 into 
my ardour.rc file, then ardour 2.0.2 will remove it.

I'll go back to 2rc1 again, for now anyway.  If this is a bug, and 
not just me, then I'm happy to test something.  I can build from 
tarballs but don't have svn set up (yet anyway).

Thanks....

--
Kevin





More information about the Ardour-Users mailing list