<br><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;">
<div><div>> - sysex gets fragmented (also when nothing is sent out meanwhile by other<br>
> objects). It is always properly terminated with '247' but the content is<br>
> often truncated. Is this a bug/feature...? What is your best recommendation<br>
> knowing that my patch is full of sysex outs (+envelopes on some of them!)<br>
> - sysex just magically does not work on the target machine ;o) I have no<br>
> clue why except for this thing with being truncated but it *never* works<br>
> even if the message seems to go out intact. Even more interesting that the<br>
> machine shows me that it is recieving sysex! Tried with the mpu-401 of an<br>
> Audigy and with a MOTU 828 mkII through Jack and a2jmidid (jack-alsa midi<br>
> bridge). <br></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <br></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I haven't actually tested sysex out limits, but sysex in is limited to<br>
something like 24 byte messages..<br>
<br>
here is a thread where i talk about it:<br>
<a href="http://lists.puredata.info/pipermail/pd-list/2009-01/067372.html" target="_blank">http://lists.puredata.info/pipermail/pd-list/2009-01/067372.html</a><br>
<br>
It is hard coded into the source. You can modify the source to change<br>
the hard coded limit.. i have a diff on that thread which shows how i<br>
did it.<br></blockquote></div><br>Thanks Alex, it's an important thing to know.<br>My sysex is shorter than 24B it's just broken.<br>What we shall see repeating is 240 67 16 73 8 16 19 (knobvalue) 247<br><br>Instead I'm having this grinded mess coming back on physical loopback:<br>
<br clear="all">print: 240<br>
print: 67<br>
print: 16<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 8<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 8<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 247<br>
print: 240<br>
print: 67<br>
print: 16<br>
print: 73<br>
print: 247<br><br>This makes me think I'm trying to send too much data in too short intervals...? Is there a handy way to limit the density of my output? (i think its not not [drip] as it has to stay realtime)<br>I'm not very experienced, sorry if this traces back to something very obvious!<br>
<br>-- <br>Muranyi Andras<br>