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

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

>good! i also think those messages can be put in a new submenu called
>sysex (where the midi controllers are).
>the user should be able to put its own messages (even by adding some
>quoted strings and bytes to a C file) with a simple template, ie.:

well, I think it would be much better for the users to define it in the
.seq24rc file or something like that.  I definatly don't want to
hardcode these things.

>#define SYSEX_MAX 10
>
>struct sysex_message {
> char name[20];
> unsigned char message[SYSEX_MAX];
> int  offset_channel;
> int offset_param;
> int offset_value;
>};
>
>example[] =3D
>{
>  { "cutoff", {0xf0, 0x32, 0x31, 0x32, 0x00, 0xf7}, 2, 3, 4 },
>  { "resonance", {0xf0, 0x32, 0x31, 0x33, 0x00, 0xf7}, 2, 3, 4 },
>  { "lfo3 deep", {0xf0, 0x32, 0x31, 0x34, 0x00, 0xf7}, 2, 3, 4 }
>}
>
>we can collect and share all these parameters, so users can find their
>synth's parameters already in.

I think sharing .seq24rc files would be much better.  I would hate to
have the sysex menu pop up 600 different synths with 200 parameters each!

>ouch! i think when defining sysex messages, there should be a
>"reverse-resolution" of the sysex type, so that seq24 could recognize
>that those sysex string is my bass cutoff.

yea, that would be the only way to do that.  It will be able to handle
all known and unknown midi.  I'll have to put in a simple hex editor.

All this is definatly going into the todo queue.  I'll be working on it.

thanks
rob