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)
> What'd be
>really slick is if there were some sort of file converter (I'm a
>programmer by profession, so I could write one if it doesn't exist
>yet) that would take a Midi Ox "snapshot" file and translate it into a
>.tx format file. I believe that I can also output those snapshots as
>raw MIDI, so maybe a converter isn't needed.
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.
> ...Adding, the BCR can generate snapshots itself. Could these be
> assigned to the BCR's buttons which, when pressed, would cause the
> BCR's rotary controllers to assume the values in the snapshot assigned
> to the button? Combining the BCR assignments and the KSP assignments
> in a single "preset" would be beyond cool...
The feedback in the BC's doesn't respond to sysex. Midi CC (continuous
controllers) are normally used for feedback (I have tried others but not
all, so I can't say for sure that there aren't other message types that
would work) and only if the .easypar command is used in the script.
For feedback you will need to have a BC preset with CC and use a CC to
sysex converter to send it out and a sysex to CC to feed back to the BC
. There are a few about. Max/MSP should do it although I haven't tried
You could make a preset that could control the K2000 with the rotary
controls as well and set it up so that the defaults are the values you
need - this can be automatically sent when you change to that preset on
the BC. Then you can tweek away at the value on the BC during
performance. If you need to change to another preset the BC remembers
the values that you had before you changed presets and will send them
again when you reselect that preset rather than the defaults. The
defaults are reset when you power off/on
If you change a parameter using the KSP you can resend all the
parameters from the BC by holding 'Edit' and pressing '<' preset key
Hope that helps.
Royce
