Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, Robert Krueger <robert.krueger@...> wrote:
> Can you elaborate what you mean here? What method would be the best?
> 
>     I don't think it would be worthwhile having BC Manager's SysEx model
>     definition file format support the MKS-50. The number of
parameters on
>     the MKS isn't that big, and the MKS format luckily doesn't even
>     include a checksum!

I was arguing that BC Manager's SysEx model definition file format
currently doesn't support the MKS, but that this isn't a serious
problem: in my (very limited) understanding of the MKS, it should be
easy to define a list of fixed "custom output" (".tx") messages for
every MKS parameter:

If I'm not mistaken, a SysEx message for a single parameter on the MKS is:

Tone parameter:
$F0 $41 $36 <Unit> $23 $20 $01 <Parameter address> <Value> $F7

Patch parameter:
$F0 $41 $36 <Unit> $23 $30 $01 <Parameter address> <Value> $F7

Obviously, on the BCF/BCR, you want e.g. the encoder's position to
translate to the parameter value on the MKS. So you have to use "val"
in the custom output definition for <Value>; and presumably $0n can be
set to $00 for most people. That then leaves only $pp to be replaced
with an actual number for every parameter - it should be easy to set
up a BCF/BCR preset that simply "lists" all the parameters.

So e.g. the parameter at address 0 in the tone area would require the
following custom output line in BC Manager:

$F0 $41 $36 $00 $23 $20 $01 $00 val $F7

Didn't you or (someone else) mention that there already exist BCF/BCR
presets for the MKS - so don't these work in the same way?

Mark.