[ardour-dev] Mackie protocol

[John Anderson]

On Wed, 2007-01-03 at 15:48 -0500, Paul Davis wrote:
> On Wed, 2007-01-03 at 22:42 +0200, John Anderson wrote:
> > I imagine ardour.rc would have to have something like
> > 
> > <MIDI-port tag="mcu" device="/dev/snd/midiC2D0" type="alsa/raw" mode="duplex"/>
> > <MIDI-port tag="mcu_xt_1" device="/dev/snd/midiC3D0" type="alsa/raw" mode="duplex"/>
> > <MIDI-port tag="mcu_xt_2" device="/dev/snd/midiC4D0" type="alsa/raw" mode="duplex"/>
> > 
> > .
> > .
> > .
> > 
> > <Protocol name="Mackie" active="yes">
> > 	<Port master="yes" tag="mcu"/>
> > 	<Port extender="1" tag="mcu_xt_1"/>
> > 	<Port extender="2" tag="mcu_xt_2"/>
> > </Protocol>
> > 
> > or something like that. But more elegant.
> 
> how about just this:
> 
> <MIDI-port tag="mcu" device="ardour" type="alsa/sequencer"
> mode="duplex"/>
> 
> then just connect all 3 physical MIDI ports to the ardour MCU port using
> qjackctl or aconnect or whatever. the ALSA sequencer sucks eggs in some
> respects, but certainly not all :)

I don't know enough about ALSA to know whether it provides data that
would disambiguate *which* midi port a particular message came from.
Which would be critical given the lack of device id in the protocol.

And from a purely personal point of view, I really like the fact that I
can start up ardour and everything's ready to go, with no need for
fiddling with qjackctl. I tend to start and stop ardour for each session
rather than using the File/Open menu.

bye
John