Bc2000 (for the BCF2000 & BCR2000)

Hello,

i've verified that the expected midi messages are sent as can be seen in
the image

http://oi39.tinypic.com/zlwxzt.jpg

also i have connected the mks directly to the bcr2000, without the midi
interface. bcr2000 midi out A to mks50 midi in and i have noticed
something weird.

when i go to cubase and add a midi track and route the out to the
bcr2000 port, the only port where i can play the mks is the bcr2000 port
2, but in the BC manager the only where the bcr firmware is recognized
is the bcr2000 port 1 (in and out)

http://oi41.tinypic.com/9asabc.jpg

http://oi44.tinypic.com/2he9ezs.jpg

any idea about this? maybe it is related to the mks and bcr comm problem

@yatlabatla, i guess you are using a mks50 software editor and the bcr,
and you have midi learnt every parameter of the editor to map to the
bcr, thats a solution but its not what im looking for, thanks :)

Regards,

J


--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "peterobrian@" peterobrian@ wrote:
> > yes, it seems that the enconders work in the right way, i.e. the
first encoder in the upper row has a value of 0 to 3, the second 0 to 3,
the fourth 0 to 5 the fifth 0-127.... and when i move them i can see the
leds and the value change in the bcr display, definitely it seems that
is working ok but the mks doesnt do anything... (i.e. the first encoder
is the dco range so i should hear a change in the sound)
>
> OK, then it's probably a totally different problem.
>
> Maybe you can verify that the BCR actually sends the intended MIDI
messages:
> E.g. in BC Manager, from the main window, open the "MIDI input
messages" window (3rd icon on the toolbar); press "Record" there and
start moving encoders.
> If the expected messages appear in the window, the problem is
definitely not with the BCR's setup (in particular the preset), but with
the connection to the MKS or the setup of the MKS itself (maybe the
wrong MIDI channel?).
>
> Mark.
>