Thanks very much, I'm sure I can figure it out with that (I'm using an RME into a behringer ddx3216, so I'll just have to adapt the names I guess<br><br>Andy<br><br><div><span class="gmail_quote">On 1/14/07, <b class="gmail_sendername">
John Anderson</b> <<a href="mailto:ardour@semiosix.com">ardour@semiosix.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, 2007-01-14 at 11:14 +1030, Andrew Johnston wrote:<br>> I was wondering if anybody could help me write a bash script that I<br>> could call say 'ardour2mmc' that would launch ardour and then run<br>> aconnect to connect the midi ports to my hardware, and then once
<br>> ardour quit, disconnect the ports.<br><br>Alternatively you can add to your ardour.rc:<br><br><MIDI-port tag="bcf" device="/dev/snd/midiC2D0" type="alsa/raw" mode="duplex"/>
<br><br>(or whatever you device is)<br><br>and make sure that<br><br> <Option name="mmc-port-name" value="bcf"/><br> <Option name="midi-port-name" value="bcf"/><br>
<br>have value the same as tag in the MIDI-port line.<br><br>That way the device is automatically connected when ardour starts. The<br>downside is that you can't access the port from any other programs while<br>ardour is running.
<br><br>bye<br>John<br><br><br>_______________________________________________<br>ardour-users mailing list<br><a href="mailto:ardour-users@lists.ardour.org">ardour-users@lists.ardour.org</a><br><a href="http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org">
http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org</a><br></blockquote></div><br>