Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, Dave Watkinson <dave422x@...> wrote:
> MIDI coming in to the unit appears to be OK, because doing anything inside
> the software causes the LEDs to flash on the BCR. I should probably also
> mention that I can't get the thing to install in USB mode any more. It used
> to be OK but or some reason it's seemingly stopped being able to use USB.
> The Behringer installer times out at the "please connect your device" step,
> and Windows just says the device failed to start / wasn't recognized.
> BCManager can't detect it either :(

This does sound as if the USB controller on your BCR is defective, although you should make absolutely sure that it's not a software problem.
This issue has come up before in this group - search the message archive.
You might also want to look at the BC Manager Manual, section 24, question 42.

Maybe a stupid question: are you sure your USB cable is OK?

Hope this helps,
Mark.

--- In bc2000@yahoogroups.com, dave watkinson <dave422x@...> wrote:
> I reconnected the BCR to my MIDI interface and put it into S3 mode. BC Manager can't detect it.

In mode S-3 anything received at the BCR's MIDI IN is directly routed to the BCR's MIDI OUT A.

So in S-3 you shouldn't use MIDI OUT A in a bidirectional setup with your computer; instead, you should use MIDI OUT B.

Alternatively, use MIDI OUT A under S-4.
(MIDI IN is routed to MIDI OUT B in this case.)

> Despite the lack of BCR detection (I disabled all my other USB / MIDI devices) I tried to open the Behringer default sysex file in BC Manager, and was greeted by this message:
> Error: MIDI system exclusive error
> Wrong command
> Send Memory ($34)
> This may be the result of a feedback loop
> Message 1

This is in line with what I wrote above: in S-3, BC Manager gets any message it sends to the BCR's MIDI IN straight back from MIDI OUT A.

Incidentally, the "Send Memory ($34)" messages contain BCR firmware data: if the BCR shows "1.10" upon power-up, there is no need whatsoever to try to update its firmware. (In fact, it's a bit dangerous.)

Hope this helps,
Mark.

--- In bc2000@yahoogroups.com, dave watkinson <dave422x@...> wrote:
> Well, your test WORKED!!

Amazing! I didn't think it would work, but rereading your posts it struck me that all the BCR's MIDI I/O LEDs still seemed to work, and it seemed a bit unlikely that these LEDs would "lie".

> Still nothing in the computer though. I have tried the auto-MIDI-input detection in both REAPER and eDrum MIDI Mapper and neither seems to be receiving anything.

One (not necessairly good...) piece of advice:
if I were you, I would leave Reaper and the BCR out of the equation until I've established working MIDI input and output ports (i.e. device drivers) for the MIDI interface(s).
I would test these I/O ports by MIDI Tools.
Maybe you can set up a loop from an interface's output to its input by means of your MIDI cable, just like you've done with the BCR: then you can send something from MIDI Tools (e.g. note or control messages) and see if these messages come back to MIDI Tools.

Hope this helps,
Mark.

--- In bc2000@yahoogroups.com, dave watkinson <dave422x@...> wrote:
> I tried the USB cable with the BCR in all of its USB modes and it sure does look like USB capabilities are no longer working.

Pity. From your very first report it already looked like this, but your further problems in the S-modes confused the situation a lot.

I think over the years I've heard from about five other people with the same problem, and I've had it too:
My first BCR had a USB controller that worked erratically from the moment I bought it, but it took me almost a year to conclude that it WAS really faulty; luckily I was still in my warranty period then, so the shop gave me a free replacement.

> I connected the MIDI cables to the BCR and to the old Yamaha MIDI interface. Communication with REAPER is working on the BCF setting, but not on the BCR setting.

Strange...
Since I'm not a Reaper user, I don't know how Reaper uses the BCR, but in any case this seems like a software/preset problem that can be solved.

> This also seems to confirm that both my original all-in-one-cable USB-to-MIDI adapter did indeed break, and also that the replacement was partially dead-on-arrival.

Dear oh dear - no wonder we had so much trouble figuring things out...
 
> so a small donation to your Mountain Utilities page will be forthcoming.

Yes, I've received your "small" donation: thank you very much!

> Merry Christmas and THANKS again!

Merry Christmas to you too (and everyone else in this group)!
Mark.