Bc2000 (for the BCF2000 & BCR2000)

Hi there,

Just wondering if anyone's had this problem before:

In Propellerheads Reason, everything works fine with my BCR2000 when
it's plugged in via USB. However when I plug it in via MIDI (through
my M-Audio Fasttrack Pro), I can't assign any of the buttons, only the
encoders. The buttons seem completely dead to the world. Which makes
me sad :(

When Reason dumps to the BCR2000 over midi, it's showing Er22 on the
screen...which is...I gather...some kind of error I don't understand!
The error doesn't show when it's working over USB so I presume it must
be what's causing the problem with the buttons.

To fix it, i've tried flashing both 1.07 and 1.10 firmware, various
combinations of midi connection, including the recommeded S-3 mode
with midi in / midi-thru connected, and screaming at it repeatedly ;)
...none of which has worked!

Any help from anyone would be greatly appreciated!

atb,
Kane

I think this is actually a problem with my MIDI interface by the looks
of it! Tried dumping sysex from Reason with the interface on my
Novation SL and everything works ok. Just the ports on my M-Audio Fast
Track Pro that seem to be problematic.

Very strange!
When I figure out what's going on there I'll post again :-)

Cheers to Mark on this forum for a post about Er20 messages that led
me to this conclusion :)

--- In bc2000@yahoogroups.com, "baron.vonkanehoffen"
<baron.vonkanehoffen@...> wrote:

>
> Hi there,
> 
> Just wondering if anyone's had this problem before:
> 
> In Propellerheads Reason, everything works fine with my BCR2000 when
> it's plugged in via USB. However when I plug it in via MIDI (through
> my M-Audio Fasttrack Pro), I can't assign any of the buttons, only the
> encoders. The buttons seem completely dead to the world. Which makes
> me sad :(
> 
> When Reason dumps to the BCR2000 over midi, it's showing Er22 on the
> screen...which is...I gather...some kind of error I don't understand!
> The error doesn't show when it's working over USB so I presume it must
> be what's causing the problem with the buttons.
> 
> To fix it, i've tried flashing both 1.07 and 1.10 firmware, various
> combinations of midi connection, including the recommeded S-3 mode
> with midi in / midi-thru connected, and screaming at it repeatedly ;)
> ...none of which has worked!
> 
> Any help from anyone would be greatly appreciated!
> 
> atb,
> Kane
>

--- In bc2000@yahoogroups.com, "baron.vonkanehoffen"
<baron.vonkanehoffen@...> wrote:
> I think this is actually a problem with my MIDI interface by the looks
> of it! Tried dumping sysex from Reason with the interface on my
> Novation SL and everything works ok. Just the ports on my M-Audio Fast
> Track Pro that seem to be problematic.
> 
> Very strange!
> When I figure out what's going on there I'll post again :-)
> 
> Cheers to Mark on this forum for a post about Er20 messages that led
> me to this conclusion :)

Eh... "Er20"? I don't know how many Marks there are in this forum, but
I did write something about "Er22"...

Anyway, I don't have a clear-cut answer to your problem, but here are
some thoughts:

First of all: I have never encountered any difference between USB and
standard MIDI for Reason-to-BCF/R communication, so I think you can
exclude Reason, or indeed your BCR: don't waste any more time flashing
firmware versions (just use 1.10).

You're probably on the right track that the problem is with your MIDI
interface. As I explained in the earlier post you're referring to,
Er22 can be caused by unwanted duplication of MIDI messages: this
completely ruins the BCR's reaction to a preset setup sent by e.g.
Reason. This happens because each SysEx message for the BCR contains a
message index, and the BCF/R expects a CORRECTLY indexed sequence of
messages, so a sequence of messages indexed "0, 1, 2, 3" etc. However,
when the BCR receives a sequence of indexes "0, 0, 1, 1, 2, 2", it
starts returning error message Er22 (and, crucially, doesn't update
its preset settings).

So my guess is that your MIDI interface indeed duplicates the messages
that Reason sends, via some feedback loop or whatever.

To confirm this, you might try connecting your MIDI interface's output
directly to a MIDI input on the computer, then send some data (from
any MIDI software program) to the MIDI interface's output, and  see
which data arrives back at the connected input (monitoring it by BC
Manager, MIDI-OX or whatever).

Mark.