Bc2000 (for the BCF2000 & BCR2000)

Let's see, if I understand everything correctly then this:

B00B7F B00100 B04746... (the "raw midi" data as logged by Midi Ox for
a "patch")

should be converted so it looks like this:

$B0 $0B $7F
$B0 $01 $00
$B0 $47 $46
etc.

And I could put a few statements on each line. The full output looks
like this:

B00B7F B00100 B04746 B0486B B04900 B04A01 B01562 B01600 B0177F B0187F
B0037F 
B00907 B00C7F B00D00 B00E5A B00F07 B01400 B01900 B01A7F B01B00 B01C0F
B01D00 
B01E00 B01F7F B0467F B04B3D B04C00 B04D00 B04E00 B04F21 B05400 B05500
B05600 
B05700 B05800

Counting bytes (where one byte = one hexidecimal value), I come up
with 105. If I could divide it up among 10 lines or less then I think
that'd be o.k., correct? If so, I could throw together a quick little
program that converts the "raw" midi data to hex.

   -Andrew-

--- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote:
>
> Welcome
> 
> >I use an m-audio Keystation Pro 88 to control my Kurzweil K2000. The
> >KSP 88 will send "snapshots" of current controller settings that I can
> >capture and store via Midi Ox. These can be transmitted back to the
> >K2000 and act as a sort of "patch" recall for my "synth" programs that
> >I'm making for the K2000. What I'd like to do is assign a snapshot to
> >a button on the BCR so that I can use it to store these "patches"
> >outside of the computer.
> 
> >I'm pretty sure the "snapshots" will fit into the 125 byte limit for a
> >.tx message -- there are around 50 controllers on the KSP 88, so if I
> >put one per line then I should only have 50 or so lines.
> 
> If you mean one button to send all the sysex messages, then you are in
> strife.
> As you pointed out there is a message limit on a single control.
> 125 / 50 is not even 3 bytes per message so this won't be possible.
> 
> But if you want to split the sysex over a few buttons, the BCR/BCF has 4
> x 8 buttons on the rotary controls top row, 2 x 8 buttons below this,
> and 4 buttons on the bottom right = 52 so are a few you could use (there
> are others if you need them)
> 
<snip...>
> 
> There are a couple of editors here. Mark's new graphic one can do just
> about everything (but it doesn't make a cup of tea! Mark you should do
> something about that)
> 
> I mainly use my script editor because that is what I am used to. Mark's
> has a page were you can edit the script as well, but I think you can
> just cut and paste the sysex messages from MidiOx into the .tx space in
> the graphic part of the editor.
> BCs use $ for the hex prefix so you will need to add that to each byte
> as MidiOx displays in Hex unless you capture it using the sysex page and
> convert it to decimal.
<snip...>
> 
> Royce
>