Re: [seq24-users] seq24-0.7.0

[federico <xa...@in...>]

 >> hey everyone!
 >>
 >> new release.
 >> lots of new features.
 >> check it out and let me know if it breaks anything.
 >>
 >> cheers!
 >> rob
 >
 >wonderful ! ! !  i was waiting for this for a long... :)
 >
 >i was wondering if it is possible to implement System Exclusive MIDI 
messages(?).
 >
 >i am a C programmer (but im pretty busy, keep in mind), but if you 
could give me some >guidelines i could try to write a patch or so.
 >
 >think that a SysEx message it is like a midi controller message, example:
 >CC:   0xB# 0xPP 0xVV
 >SysEx:  0xF0 0x32 0x2# 0xPP 0xVV 0xF7
 >
 ># is the channel number, PP is the parameter number, VV is the value 
number.
 >
 >i gave a quick look at event.cpp but not sure where midi message are 
transmitted and >if are needed other mods in other src-files

sorry, i was remembering something wrong...
i see in event.cpp support for system exclusive, and i see something in 
midibus.cpp too, but sysex are transmitted only by 
perform::input_func(), so i guess it is only for passing sysex 'thru'.

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?

if the answer is yes, i guess we only miss the 'View' part (thinking 
with the mvc pattern in mind...uhm..what about saving sysex?).
so, if i can suggest, i think a great improvement is to give the ability 
to insert sysex data (see above the comparision with a CC message), 
since on most hardware synthesizers this is the only way to control 
parameters :-|

what do you think about?

ciao
Federico