Bc2000 (for the BCF2000 & BCR2000)

Wow, thanks for the great responses, I'll keep you guys updated if I can get it to work,

thanks again!

--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
>
> Hi ,
> I have just been writing a BCR2000 preset for the K3 so when it is completely working I'll put it in the files section and it might be a good start for you BCN preset.
> 
> All the best
> Royce
> 
> --- In bc2000@yahoogroups.com, "markwinvdb" <markwinvdb@> wrote:
> >
> > --- In bc2000@yahoogroups.com, "justino30" <justin-macri@> wrote:
> > > I was overjoyed when I found a bcn44 editor
> > > from Mountain Utilities on this group, however I'm confused with how
> > > to use it.
> > > The program came with no manual, and
> > > I'm confused about how to use it, if anyone has any tips, please let
> > > me know! Thanks!
> > 
> > Sorry about there being no manual, but writing a good manual is always a lot of work.
> > Since Behringer states that the BCN44 is "Discontinued" on their web site (http://www.behringer.com/EN/Products/BCN44.aspx), BCN44 Manager (let alone writing a manual for it) isn't very high on my long wish list.
> > I can only repeat what I wrote on my web site: for information on BCN44 Manager's general setup, please refer to the manual for BC Manager, since much is the same.
> > 
> > > It says on thier website "contains support for 'custom'
> > > MIDI messages (up to 11 bytes), in particular System Exclusive
> > > messages" so I'm hoping I can use it to control filter and lfo
> > > parameters on my K3 synthesizer.
> > > some users from the k3 group decoded the sysex messages
> > 
> > I've looked a bit at the K3 manual (http://www.kawaius-tsd.com/OM/K_SYNTH/K3.PDF):
> > It should indeed be possible for those messages that consist of 11 bytes or less.
> > 
> > > I don't know how to input them into the editor...
> > 
> > In an Encoders window, click on the "E" button: this opens the Encoder dialog box.
> > 
> > There you do the following:
> > 
> > - Set Type to Custom
> > 
> > - In the Bytes editbox you type the SysEx message's bytes in bare hexadecimal format, separated by spaces.
> > So in your case this should look like:
> > F0 40 ... F7
> > 
> > - The tricky part: set "Index of button/encoder value" to the position of the byte in the message that corresponds with the value of the button/encoder. (So in fact this byte becomes variable.)
> > 
> > Note that the OK button is disabled when "Index ..." isn't pointing to a data byte (00-7F), i.e. to a status byte (F0 or F7 for SysEx messages) or to a position beyond the current message length.
> > 
> > In fact, there is a slight (but annoying) bug in the dialog box concerning this:
> > Once the OK button has become disabled, it stays that way if you clear the Bytes editbox or select a different Type than Custom, whereas in both cases it should actually get re-enabled.
> > I'll release a version of BCN44 Manager that fixes this as soon as possible, hopefully this weekend.
> > 
> > Mark van den Berg.
> >
>