Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "toorglick" <toorglick@...> wrote:
toorglick wrote:
> I want to have all tone-level programming parameters 
> available with group one, and then have group two contain the 
> extras.  There are only THREE (3) parameters from the tone-level that 
> I have to put in group 3 and if I could figure out how to make 
> buttons increment I could move those out of group 3 and into group 1.
> 
> The only way to do this is via EASYPAR.  However, I haven't yet found 
> a breakdown of EASYPAR that at least makes sense - the syntax, 
> variables, etc.
> 
> I believe the syntax is EASYPAR {mode} {MIDI ch} {para #} {range low} 
> {range high} {variable} - yes?

Have you looked at the syntactic descriptions for .easypar in "BC MIDI
Implementation.pdf"? There's also a lot on various "increment" modes
(e.g. for ".easypar CC"), which might work if your device recognizes
Control Change messages.

> I can't get this to work as outlined in the Secrets PDF when using it 
> on the MKS.  There are no MIDI-relative parameter numbers for tone-
> editing.  Like, for example, to cycle through the wave shapes.
> 
> Did I miss a memo on EASYPAR, or am I pushing the BCR a little to far 
> trying to make buttons increment in a sysex-only device?

If your device only listens to SysEx messages (as opposed to channel
messages like CC), you can't use ".easypar"; instead you should use
".tx" ("custom output" in BC Manager).
But I can't quite fathom yet what you're exactly trying to do. Could
you specify what MIDI messages you exactly want to send to your MKS?
My guess is that the BCR can indeed do what you want.

Mark.