Re: [seq24-users] seq24-0.7.0 (sysex)

[Rob B. <rc...@fi...>]

> >i was wondering if it is possible to implement System Exclusive MIDI
>messages(?).

currently the only thing that seq24 does is act as a thru for incoming
sysex.

> >think that a SysEx message it is like a midi controller message, example:
> >CC:   0xB# 0xPP 0xVV
> >SysEx:  0xF0 0x32 0x2# 0xPP 0xVV 0xF7

Well, each device has such a different sysex format, I can not think of
an easy way to support it.  Where should it go in the midi stream?  How
should seq24 represent each block of sysex visually?  Does seq24 play
the sysex each time though the loop?  I really can't think of any way
to implement a sysex editor other than just a hex editor style.

Maybe if the user specifies the sysex pattern ahead of time, and then the
data editor will modify one byte out of that stream?

Such as
<Filter Cutoff> 0xf0 0x32 0x31 0x32 VAL 0xF7
<Filter Res> 0xf0 0x32 0x31 0x33 VAL 0xF7
<Envelope Attack> 0xf0 0x32 0x31 0x34  VAL 0xF7

Then the editor can display those in the event menu under a sysex
submenu.  And the VAL's can be edited with the mouse?


>what would happen if i load a midi file with sysex data in it? (ps. does
>seq24 follows some standard for its format?)
>will seq24 play the sysex strings?

seq24 uses the midi file standard. It will currently  just throw away
sysex if found in the file.

rob