Hello,
in the abstraction i just compose the message (like martin and cyrille
described in the thread) which then gets a bang.
what is exactly the problem? you can use it like any other abstraction.
put it in the pd path. create [sysexout] in a patch. the left inlet
takes the byte values
hi,
i made an abstraction [sysexout] ;) - but i dont have hardware here to
test it. so please do.
g.
Martin Peach:
Yes, why not just send a list though?
It seems that in WinXP [midiout] sends 247(start sysex) followed by
240(end sysex), the intervening message doesn't get transmitted.
Alex a écrit :
I just tried this myself on a friend's windows machine running a
relatively recent version of pd extended, though I'm not exactly sure
which one..
it gave me an error
MidiOut Error 1
whenever I tried to send a sysex message out.
And there was an error about [sysexin] not being
martin.pe...@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this way:
bang
|
[tb bbb]
| | ||
[247( [123( [88( [240(
|_|_||
|
|
[midiout]
this is the same than :
[240, 88, 123, 247(
(with coma)
c
That is, banging all the
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 c...@chnry.net wrote:
martin.pe...@sympatico.ca a écrit :
On linux with alsa midi, sysex output works this
They're called list2sysex and sysex2list btw.
-Alex
On Wed, Feb 3, 2010 at 4:21 PM, Alex x37v.a...@gmail.com 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,
Yes, why not just send a list though?
It seems that in WinXP [midiout] sends 247(start sysex) followed by
240(end sysex), the intervening message doesn't get transmitted. Also if
the message contains numbers 127 then more bytes get transmitted, not
good.
Also as lists seem to be easier to
