<div class="gmail_quote">2009/7/8 Alex <span dir="ltr"><<a href="mailto:x37v.alex@gmail.com">x37v.alex@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It looks like you may experiencing another thing that i've complained<br>
about... pd's alsa midi connects to all MIDI inputs and outputs that<br>
it can.. this includes alsa's MIDI through.. so everything that you<br>
send out gets echoed back into the input.. SUPER annoying.<br>
<br>
run aconnect [or easier, though not great, aconnectgui] and see if<br>
that is the case for you.. disconnect pd from the alsa through port.<br>
<div></div></blockquote><div><br>I've checked and it's ok. Right now have the output looped back with a cable but it only comes back once.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="h5">> This makes me think I'm trying to send too much data in too short<br>
> intervals...? Is there a handy way to limit the density of my output? (i<br>
> think its not not [drip] as it has to stay realtime)<br>
</div></blockquote></div><br>What about dropping some data before making up / sending out the sysex? My best guess was storing into [float] and firing it with [metro] or [pulse] at a constant, decent rate.<br clear="all">
<br>-- <br>Muranyi Andras<br>