[PD] Sysex out problems (linux only)
x37v.alex at gmail.com
Wed Jul 8 02:08:13 CEST 2009
I haven't actually tested sysex out limits, but sysex in is limited to
something like 24 byte messages..
here is a thread where i talk about it:
It is hard coded into the source. You can modify the source to change
the hard coded limit.. i have a diff on that thread which shows how i
It would be nice if this limit was either totally removed or
dynamically growable.. as it would be really nice to be able to write
real sysex editors in PD.
I have been creating my own physical devices with sysex and I use pd
to edit the sysex data but i have to make my sysex packets short
because of PD's limitations.
2009/7/7 András Murányi <muranyia at gmail.com>:
> Dear Sirs,
> I just have never been successful with sysex in Pd and I'm asking for your
> kind advice.
> Attached is an example for a long sysex message which goes out on [midiout]
> (linux only, afaik).
> The problems I have:
> - sysex gets fragmented (also when nothing is sent out meanwhile by other
> objects). It is always properly terminated with '247' but the content is
> often truncated. Is this a bug/feature...? What is your best recommendation
> knowing that my patch is full of sysex outs (+envelopes on some of them!)
> - sysex just magically does not work on the target machine ;o) I have no
> clue why except for this thing with being truncated but it *never* works
> even if the message seems to go out intact. Even more interesting that the
> machine shows me that it is recieving sysex! Tried with the mpu-401 of an
> Audigy and with a MOTU 828 mkII through Jack and a2jmidid (jack-alsa midi
> bridge). Sysex is
> Thanks a Lot!
> Muranyi Andras
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
More information about the Pd-list