They're called list2sysex and sysex2list btw. -Alex
On Wed, Feb 3, 2010 at 4:21 PM, Alex <[email protected]> wrote: > I wrote a little abstraction that does list -> sysex and another one > that does sysex input -> list > They're in the list archives... > > -Alex > > On Wed, Feb 3, 2010 at 1:52 PM, cyrille henry <[email protected]> wrote: >> >> >> [email protected] a écrit : >>> >>> On linux with alsa midi, sysex output works this way: >>> >>> bang >>> | >>> [t b b b b] >>> | | | | [247( [123( [88( [240( >>> |_____|_____|____| >>> | | >>> [midiout] >> >> this is the same than : >> [240, 88, 123, 247( >> (with coma) >> >> c >> >>> >>> That is, banging all the values separately into [midiout] during one >>> message time slot. >>> (Note the message is written backwards since the first byte to transmit is >>> the sysex status byte, 240) >>> Banging them in one at a time manually only sends one byte, banging them >>> in as a list stops [midiout] from working until you reopen the patch. >>> >>> Martin >>> >>> >>> _______________________________________________ >>> Pd-dev mailing list >>> [email protected] >>> http://lists.puredata.info/listinfo/pd-dev >>> >> > _______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
