Did I brick my BCR2000?

3 posts / 0 new
Last post
BarBryzze
BarBryzze's picture
Did I brick my BCR2000?

Hi, I recently purchased a BCR2000 from a pawnshop. It was only 30 euro's and I wanted to try use it with Cakewalk. A friend of mine recently gave me a few of his synths to try out, and in that time I got one of my own. That BCR2000 looked like it could be perfect for the job, and despite being familiar with Behringer products I bought it, especially because it mentioned Sonar in the documentation I found online. Back home, I continued searching, found AJ's thread on the Cakewalk forum, which ultimately lead me here. The BCR had been sitting on my desk for a month, and I finally felt confident enough to try and get it to work. 

I've been knee deep in manuals for weeks now, and have little to no knowledge about midi. Actually I have no idea what I'm doing, this is all new to me. I need a manual just to understand the manual, sort of speak. So yesterday I wanted to install AJ's plugin (there's still a download available in yet another different thread on the old forums) but to be sure I knew what I was doing I first installed the official firmware, to see if that worked. Low and behold, it did. I continue searching and reading further, and when I returned to my desk the BCR was out. No lights on the knobs, no response when turning them, nothing, except for the controls of the BCR itself. I can change the mode and pick a channel, or choose a preset, assign a control, maybe store it, I can't tell, but the entire control section seems dead. It doesn't show up in BC Manager anymore, or Windows. 

Can it still be fixed somehow or did I screw it up? I had it in U3 hooked up to my pc, and left BC Manager as well as MidiOX running the whole time too. All I did was successfully install the firmware and back up the modified data which I then sent back to the BCR. At least, that's what I know I did, I don't know what else I might have done wrong in the process, and no one's here to stop me when I'm about to make a mistake. 

Lastly, I can't believe how much work and dedication has gone into this. It's truly remarkable someone took it upon them to do this. I mean, might as well get better gear and move on but this website restored some of my faith in humanity. Not in Uli Behringer though.

I hope someone can help me, or can guess what might have happened and tell me if it's still worth the trouble of trying to fix it. 

Thank you. 

Mark van den Berg
Mark van den Berg's picture

So yesterday I wanted to install AJ's plugin (there's still a download available in yet another different thread on the old forums)

In case you've missed it: I've written a document detailing some of the ways in which the BCF2000 and BCR2000 can be used with SONAR, and concocted a package concerning A.J. Mayo's BCR2000 Control Surface for SONAR, which you can download from this website. See this topic. (Note: this was long before "Cakewalk by Bandlab", so I don't know to what extent any of this still works for CbB.)

but to be sure I knew what I was doing I first installed the official firmware, to see if that worked. Low and behold, it did.

(Re-)installing the BCR's firmware is completely superfluous If the BCR shows "1.10" on startup (because the BCR refuses to run if the firmware doesn't match a checksum). Worse, re-installing the firmware is actually dangerous, because if the procedure gets interrupted, the firmware ends up in an invalid state, so that the next time the BCR is powered on, its display will brick at "noOS", and you will have to re-install the firmware via a "real" MIDI cable (because the BCR's USB modes require fully functional firmware).
See sections 4 and 10 (MIDI -> Maintenance -> Send firmware) of the BC Manager manual for further discussion.

I continue searching and reading further, and when I returned to my desk the BCR was out. No lights on the knobs, no response when turning them, nothing, except for the controls of the BCR itself. I can change the mode and pick a channel, or choose a preset, assign a control, maybe store it, I can't tell, but the entire control section seems dead. It doesn't show up in BC Manager anymore, or Windows. 

Can it still be fixed somehow or did I screw it up? I had it in U3 hooked up to my pc, and left BC Manager as well as MidiOX running the whole time too. All I did was successfully install the firmware and back up the modified data which I then sent back to the BCR. At least, that's what I know I did, I don't know what else I might have done wrong in the process

There might be something wrong with the hardware of your BCR (e.g. faulty buttons/encoders, or a defective USB controller), but this doesn't seem likely, considering that things used to work initially. In any case you can't have bricked any of the BCR's hardware by updating the firmware, except that the firmware itself might end up corrupted, as I described above.
So my best guess at this point is that your problems are software-related.

You state that you can still "change the mode and pick a channel" etc.
So I assume that the BCR's display still briefly says "1.10" on startup (rather than bricking at "noOS"), and that means that the firmware is OK. So then the next question is: in what Operating Mode is the BCR? You say it used to be U-3, but what is it now?
Obviously, if you're using the USB cable to the computer, the BCR needs to be in a U-mode, not an S-mode. U-1 is probably best at this stage, because it excludes the I/O devices related to the BCR's MIDI sockets, which can be a source of confusion.
Beware: you shouldn't change the BCR's Operating Mode when any MIDI application (BC Manager, Cakewalk etc.) is running, because this will make the I/O software devices (as used by these applications) dysfunctional: you would then have to restart these applications.
If the BCR is in U-1, the BCR should be represented by one MIDI input device and one MIDI output device on the computer, and MIDI applications like BC Manager should see these devices.
Beware: the Windows driver for the BCR's MIDI I/O devices is buggy: on a restart of Windows the driver may alter the previous BCR's MIDI I/O device names by adding a "weird" character, or indeed changing the previously used weird character. So you always have to be on the lookout: if a MIDI application (like BC Manager or Cakewalk) suddenly can't find the BCR any more, you may have to tell these applications that they should connect to the I/O devices with the new name.

You may want to take a look at "BC MIDI Implementation.pdf" (shipped with BC Manager, also available from the BC2000 page at this website): sections 22 and 23 describe various startup and other functions that you can perform on the BCR itself, which may help you solve your problems. E.g. STORE + EXIT should give you an initialized (empty) temporary preset.

You may try BC Manager's "Test hardware" operation to test the individual buttons and encoders of the BCR. See under MIDI -> Maintenance -> Test hardware in section 10 of the BC Manager manual. (But of course you'll need to get your BCR and BC Manager to talk to each other in the first place...)

Hope this helps,
   Mark.

BarBryzze
BarBryzze's picture

According to Bandlab, everything Sonar works in Cakewalk, so we'll see when or if I can get it running again. I'll let you know. Thanks for replying!