<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jun 15, 2013 at 10:55 AM, David Santamauro <span dir="ltr"><<a href="mailto:david.santamauro@gmail.com" target="_blank">david.santamauro@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 06/15/2013 10:49 AM, Paul Davis wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Sat, Jun 15, 2013 at 10:16 AM, David Santamauro<br></div><div class="im">
<<a href="mailto:david.santamauro@gmail.com" target="_blank">david.santamauro@gmail.com</a> <mailto:<a href="mailto:david.santamauro@gmail.com" target="_blank">david.santamauro@<u></u>gmail.com</a>>> wrote:<br>
<br>
<br>
but anyway, you don't have to keep reconnecting. there is a MIDI<br>
input-enable button in every MIDI mixer strip. if you turn it<br>
off, that<br>
track will receive no MIDI at all, no matter what it is<br>
connected to.<br>
<br>
<br>
fair enough, but my concerns are (were) with outputs<br>
<br>
<br>
mute is fairly powerful :)<br>
<br>
</div></blockquote>
<br>
indeed ...<br>
<br>
For this slight of hand (|| for &&) and a crash I fixed (in my working git) ... what is the patch submission process?<br></blockquote><div><br></div><div>simplest/best is to use github to set up a pull request. <br>
</div><div> </div></div><br></div></div>