Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
> 
> Since the MKS-50 is a Roland device, I assume that it maps its
> parameters via Roland's standard DT1 SysEx protocol. If this is the
> case, it might indeed be a good idea to write a "SysEx model
> definition file" for BC Manager.
> 
> Of course you could do without this by "simply" writing each and every
> encoder's "custom output" SysEx message manually, but the SysEx model
> definition file will simplify things greatly for you during preset
> creation:
> 
> Basically, you just have to copy the list of parameter names plus
> their addresses and ranges from the MKS's SysEx implementation manual
> to the definition file. (You may take a look at GS-10.ini for the
> general idea; you should use Roland.ini as a template.)
> BC Manager will then construct the FULL message whenever you want to
> assign a parameter to a knob: you just select the parameter by NAME,
> and bingo!
> So whereas the creation of the SysEx model definition file is a bit of
> extra work, once you have it you don't ever have to worry about SysEx
> parameter details any more.
> 
> See the section on "SysEx model definition files" in BC Manager's
> manual for further details.
> 
> Good luck!
> (And if you succeed, please put the ini fine in the Yahoo group's file
> section!)
> 
> Mark.
>

After a lot of confusion, It doesn't look like the MKS-50 SysEx maps
to the Roland standard :(  the bytes certainly don't match up from the
MKS-50 implementation and the other Roland examples I've seen around
the place, and I can't force the ini to create the sequence I need.  
Oh well.