Bc2000 (for the BCF2000 & BCR2000)

Thanks for the responses, I'll just sum up my response to the three I 
say here:

> 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.

Yes, I'm not on that computer at the moment, however I downloaded all 
of the available PDFs I could.  Perhaps I couldn't wrap my head around 
what I was reading at the time.  A CC message will not work in this 
instance, read on...



> 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.
> 


Yes, for whatever reason, and it's most likely my fault, I couldn't get 
the TX editor to spit out sysex that I could upload to the BCR.  The 
other issue was that the functions I am looking at will not respond to 
CC messages, hence the reason I was stuck trying to parse the .easypar 
syntax.

I want the buttons to cycle through the available waveform choices 
since you can only choose one at a time, and there aren't many 
choices.  So, to be more explicit, I want to create SAW WAVE, PULSE 
WAVE, and SUB OSC WAVE buttons to select the waveform for each type.

I'll take a look at the material again to see what I may have missed.  
In the meantime the solution I have works, I just think it could be a 
little more efficient.  I'm actually going to upload the sysex and 
overlay here shortly and when I get a chance see if I can refine it 
further.

Regards,
Rich