Bc2000 (for the BCF2000 & BCR2000)

No, it's not too indirect, just would be nice if I could take the
process one step further. I just now tried to do it Behringer's way
(sent a "snapshot" of the Keystation 88's controllers to the Behringer
and tried to record it via "Learn") and it didn't work -- the screen
flashed "bad" then "good", and sure enough it recorded one line of the
 message (right around the middle of the message, too)... problem is
the message is around 100 lines long. I've been using Midi Ox for
doing the snapshot thing and it works very well, but ultimately I'd
like to freely share my "toys" and I think having full-featured K2000
presets (to go along with the synth models I'm working on) for the
Behringer that include "patches" would be more fun (and less hassle)
for other users. So thanks again for the great utility; it works
perfectly for my needs.

From a wonky programmer point-of-view, if the MIDI recording
funcionality were modular you could "plug it in" anywhere in the
program. As I've thought about this, having "record" functionality
right on the parameter page would work out best for what I do. Of
course, those needs shouldn't dictate what you do with your program. I
will use it and enjoy it either way.

And, why don't other manufacturers get on board with assigning
arbitrary sysex to controls? I really like the Novation controllers
with the LCD screens to remind you about what knob does what (very
useful when dealing with the internals of hardware synths), but the
dang things won't do arbitrary sysex longer than (I think) 8 bytes. As
bad a rap as Behringer gets in the pro audio world for their
mixers/premaps/etc, they're beating the pants off of other controller
makers IMHO.

    -Andrew-

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "poser_p" <poserp@> wrote:
...
> I think that on the BCF/BCR themselves this is already possible
> (although I haven't tried it myself), as explained in par. 4.3.1 of
> the B-Control manual (vs. 1.1, Oct. 2004).
> 
> However, if you want to do this from BC Manager... If I understand you
> correctly, this is conceptually not too different from the method via
> the "MIDI input messages" window I've just implemented, unless you
> find that too indirect.
> 
> In fact, after first reading about your problem, I racked my brains
> for several days about the best way to implement this kind of learn
> function. I considered adding "Record" and "Stop" buttons to the
> button/encoder/fader dialog's "custom output" tab for direct input,
> but finally I chose the more modular approach via the MIDI input
> message window: one advantage of that window is that it already has
> facilities for filtering out unwanted types of messages and selecting
> recorded messages.
> 
> Mark.
>