http://www.mnml.nl/phpBB2/viewtopic.php?t=49126  michael green

m: 010 4910 2282 w: http://soundcloud.com/greenbuddha

From: "pd-list-request@iem.at" pd-list-request@iem.at To: pd-list@iem.at Sent: Wednesday, 8 July, 2009 13:17:39 Subject: Pd-list Digest, Vol 52, Issue 19

Send Pd-list mailing list submissions to     pd-list@iem.at

To subscribe or unsubscribe via the World Wide Web, visit     http://lists.puredata.info/listinfo/pd-list or, via email, send a message with subject or body 'help' to     pd-list-request@iem.at

You can reach the person managing the list at     pd-list-owner@iem.at

When replying, please edit your Subject line so it is more specific than "Re: Contents of Pd-list digest..."

Today's Topics:

1. Re: Sysex out problems (linux only) (Alex)   2. Re: Sysex out problems (linux only) (Andr?s Mur?nyi)   3. Re: Sysex out problems (linux only) (Alex)   4. Re: Sysex out problems (linux only) (Andr?s Mur?nyi)   5. Re: Sysex out problems (linux only) (Martin Peach)   6. Re: workshop in Boston August 1st (ydegoyon@gmail.com)

Message: 1 Date: Tue, 7 Jul 2009 17:08:13 -0700 From: Alex x37v.alex@gmail.com Subject: Re: [PD] Sysex out problems (linux only) To: Andr?s Mur?nyi muranyia@gmail.com Cc: pd-list@iem.at Message-ID:     c5e6c7e30907071708t2737b929gcad15b983ca0b377@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1

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: http://lists.puredata.info/pipermail/pd-list/2009-01/067372.html

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 did it.

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.

-Alex

2009/7/7 Andr?s Mur?nyi muranyia@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@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Message: 2 Date: Wed, 8 Jul 2009 02:23:00 +0200 From: Andr?s Mur?nyi muranyia@gmail.com Subject: Re: [PD] Sysex out problems (linux only) To: pd-list@iem.at Message-ID:     23cdbfeb0907071723t75a155d0p824b42bf4879e13f@mail.gmail.com Content-Type: text/plain; charset="iso-8859-1"

2009/7/8 Alex x37v.alex@gmail.com

...

• 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).

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: http://lists.puredata.info/pipermail/pd-list/2009-01/067372..html

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 did it.

Thanks Alex, it's an important thing to know. My sysex is shorter than 24B it's just broken. What we shall see repeating is 240 67 16 73 8 16 19 (knobvalue) 247

Instead I'm having this grinded mess coming back on physical loopback:

print: 240 print: 67 print: 16 print: 247 print: 240 print: 67 print: 247 print: 240 print: 67 print: 16 print: 247 print: 240 print: 67 print: 16 print: 73 print: 247 print: 240 print: 67 print: 16 print: 73 print: 8 print: 247 print: 240 print: 67 print: 16 print: 73 print: 247 print: 240 print: 67 print: 16 print: 247 print: 240 print: 67 print: 16 print: 247 print: 240 print: 67 print: 16 print: 73 print: 8 print: 247 print: 240 print: 67 print: 16 print: 247 print: 240 print: 67 print: 16 print: 73 print: 247 print: 240 print: 67 print: 16 print: 73 print: 247 print: 240 print: 67 print: 16 print: 73 print: 247

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) I'm not very experienced, sorry if this traces back to something very obvious!