mkl, while many of those were very very good and important feature requests, they kind of strayed a little bit from the specificity of the function being added.
multitimbrality is a major question here. currently, external control changes when you select different tracks w/ different active programs. this would be the case as well w/ midi cc control over note on and realtime slider functions. i think multitimbrality (or maybe just some sort of midi channel routing) would be a terrific addition. i don't know if we'll see it before cc=>qlink.
HOWEVER, when we do, you are dead on with this:
4>>we schould have two different midi kind of actions :
-multitimbral (with channels)
-or actual on screen track
your list of "to-be assignable parameters per channel" looks good, though i don't think REVERSE exists currently. i'd love a REVERSE parameter, as well as a PLAYRATE parameter. but again, first things first.
the fx parameters (change fx by sysex for example)
yeah that'd be cool. i'll include this, but as i understand it, fx are heavy on the CPU. i've heard several reports of negative effects on timing due to effects use. the programmer will know whether or not this is a feasible addition.
mpc schould be able to send/record sysex data
unfortunately, sysex data was before my time. reading borg's site here
http://www.borg.com/~jglatt/tech/midispec/sysex.htm doesn't help much. again, i'll pass this on, but could you please embellish.
7>>an analog style sequencing schould be cool to (16 knob one per 16th notes)
this one might be a little out there in terms of the current feature being discussed...it's still cool though!
8>>ability to have the same midi message for multiple parameters at once
yeah i like that.
9>>midi soft take over or "analog" emulation
could you explain further?
sorry about my french
it's not nearly as good as your english.
