Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Thread

Driver issues, defective unit?

Driver issues, defective unit?

2012-01-19 by leckmichunten

Hi,

I have spent the last 2 days trying to get my BCR2000 to work, but have serious issues each time I restart my computer.

My BCR will only work properly, whenever I unplug it from USB, delete it in the device manager, reboot and plug it in again and the driver gets reinstalled. Everything seems fine then.

But as soon as I restart my PC, multiple things will not work correctly. Ableton Live will receive Midi data from the BCR, but the BCR will not update it's encoder values when I do changes in Live. If I try to use MidiOX and send SysEx to the BCR, the display will not start rotating like it uses to. The transfer stops after a while with the error message: SysEx: No Buffers Available.
BC Manager will not find the BCR at all. Trying to do a SysEx transfer results in an error too: Not enough memory available.

If I reboot now, and uninstall it, plug the BCR in again, the driver gets reinstalled and it will work fine again. BC Manager finds the BCR, I can transfer SysEx data to it with MidiOX and encoder values will be updated with changes via mouse in Live.

I have read probably hundreds of threads here and in other forums to find users with similar problems, but nothing really helped.

I am on Windows 7 64bit, using the Behringer driver for 64bit. My BCR is in mode U1 and connected via USB. I have tried switching the USB port and tons of other things but it stays the same. And I am out of ideas... What is going on with my BCR? I am even considering it's defective, although it's new and works fine after the fresh install.

Any help is appreciated. Thank you!

Re: Driver issues, defective unit?

2012-01-19 by leckmichunten

Wohoo I seem to have it sorted out.
The cause is...

Drumroll...

THE FREAKING USB CABLE IT CAME WITH!


After changing the cable it seems to work fine now and keeps doing so after a reboot. I can't possibly imagine how the cable would cause it to work properly after a fresh install, but not anymore after rebooting, but whatever.

At least it works now with a new cable. If anybody has weird issues with his BCR, change the cable first... Might save you from a lot of grey hair.



 

--- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@...> wrote:
Show quoted textHide quoted text
>
> Hi,
> 
> I have spent the last 2 days trying to get my BCR2000 to work, but have serious issues each time I restart my computer.
> 
> My BCR will only work properly, whenever I unplug it from USB, delete it in the device manager, reboot and plug it in again and the driver gets reinstalled. Everything seems fine then.
> 
> But as soon as I restart my PC, multiple things will not work correctly. Ableton Live will receive Midi data from the BCR, but the BCR will not update it's encoder values when I do changes in Live. If I try to use MidiOX and send SysEx to the BCR, the display will not start rotating like it uses to. The transfer stops after a while with the error message: SysEx: No Buffers Available.
> BC Manager will not find the BCR at all. Trying to do a SysEx transfer results in an error too: Not enough memory available.
> 
> If I reboot now, and uninstall it, plug the BCR in again, the driver gets reinstalled and it will work fine again. BC Manager finds the BCR, I can transfer SysEx data to it with MidiOX and encoder values will be updated with changes via mouse in Live.
> 
> I have read probably hundreds of threads here and in other forums to find users with similar problems, but nothing really helped.
> 
> I am on Windows 7 64bit, using the Behringer driver for 64bit. My BCR is in mode U1 and connected via USB. I have tried switching the USB port and tons of other things but it stays the same. And I am out of ideas... What is going on with my BCR? I am even considering it's defective, although it's new and works fine after the fresh install.
> 
> Any help is appreciated. Thank you!
>

Re: Driver issues, defective unit?

2012-01-21 by leckmichunten

Nope! After 1 day of working we are back to square 1 again. Or more square 0 in this case because now it's not working anymore at all. BC Manager doesn't find it, Ableton gets incoming Midi messages but doesn't transmit any to it, nor does MidiOX.

I am out of ideas here. Is it defective?



--- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@...> wrote:
Show quoted textHide quoted text
>
> Wohoo I seem to have it sorted out.
> The cause is...
> 
> Drumroll...
> 
> THE FREAKING USB CABLE IT CAME WITH!
> 
> 
> After changing the cable it seems to work fine now and keeps doing so after a reboot. I can't possibly imagine how the cable would cause it to work properly after a fresh install, but not anymore after rebooting, but whatever.
> 
> At least it works now with a new cable. If anybody has weird issues with his BCR, change the cable first... Might save you from a lot of grey hair.
> 
> 
> 
>  
> 
> --- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@> wrote:
> >
> > Hi,
> > 
> > I have spent the last 2 days trying to get my BCR2000 to work, but have serious issues each time I restart my computer.
> > 
> > My BCR will only work properly, whenever I unplug it from USB, delete it in the device manager, reboot and plug it in again and the driver gets reinstalled. Everything seems fine then.
> > 
> > But as soon as I restart my PC, multiple things will not work correctly. Ableton Live will receive Midi data from the BCR, but the BCR will not update it's encoder values when I do changes in Live. If I try to use MidiOX and send SysEx to the BCR, the display will not start rotating like it uses to. The transfer stops after a while with the error message: SysEx: No Buffers Available.
> > BC Manager will not find the BCR at all. Trying to do a SysEx transfer results in an error too: Not enough memory available.
> > 
> > If I reboot now, and uninstall it, plug the BCR in again, the driver gets reinstalled and it will work fine again. BC Manager finds the BCR, I can transfer SysEx data to it with MidiOX and encoder values will be updated with changes via mouse in Live.
> > 
> > I have read probably hundreds of threads here and in other forums to find users with similar problems, but nothing really helped.
> > 
> > I am on Windows 7 64bit, using the Behringer driver for 64bit. My BCR is in mode U1 and connected via USB. I have tried switching the USB port and tons of other things but it stays the same. And I am out of ideas... What is going on with my BCR? I am even considering it's defective, although it's new and works fine after the fresh install.
> > 
> > Any help is appreciated. Thank you!
> >
>

Re: [bc2000] Re: Driver issues, defective unit?

2012-01-21 by Bruno

2012/1/21 leckmichunten <leckmichunten@...>:
> Nope! After 1 day of working we are back to square 1 again. Or more square 0 in this case because now it's not working anymore at all. BC Manager doesn't find it, Ableton gets incoming Midi messages but doesn't transmit any to it, nor does MidiOX.
>
> I am out of ideas here. Is it defective?

I wonder if that could be the USB connector getting loose. If it's
new, can you exchange it for another unit?

Bruno

Re: Driver issues, defective unit?

2012-01-21 by Mark v.d. Berg

--- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@...> wrote:
> BC Manager doesn't find it, Ableton gets incoming Midi messages but doesn't transmit any to it, nor does MidiOX.
> 
> I am out of ideas here. Is it defective?

I get the impression that the problem is only with the connection FROM the computer TO the BCR that is defective? (I.e. the "MIDI output device" from the perspective of the computer.) Is this so?

In any case, my guess at this point is that there is a hardware fault in the USB controller of your BCR, assuming it's not a cable problem.
And have you ruled out a fault in the computer's USB hardware? Not that I think this is likely, but when things are this desperate... To check this, you might try connecting your BCR to a different computer.

You may want to look at question 42 in section 24 of the BC Manager Manual (p. 93), in particular point 3: basically this is about checking whether things do work if you connect the BCR to a computer via its standard MIDI I/O sockets. That should give you strong evidence that the problem indeed lies with the USB hardware.

You could also connect your BCR directly to a synth or master keyboard via MIDI: e.g. see if you can get the BCR to switch between presets by sending Program Change messages from the synth/master keyboard.

Hope this helps,
Mark.

Re: Driver issues, defective unit?

2012-01-21 by leckmichunten

The connector itself seems to be fine, not moving or anything. I have tried 3 cables by now, so I doubt it's the cable either.

And yes, I guess I can exchange it. I will call support and ask to be sure. But I bought it new and from an authorized online shop, so they should have a return policy.



--- In bc2000@yahoogroups.com, Bruno <brunorc@...> wrote:
Show quoted textHide quoted text
>
> 2012/1/21 leckmichunten <leckmichunten@...>:
> > Nope! After 1 day of working we are back to square 1 again. Or more square 0 in this case because now it's not working anymore at all. BC Manager doesn't find it, Ableton gets incoming Midi messages but doesn't transmit any to it, nor does MidiOX.
> >
> > I am out of ideas here. Is it defective?
> 
> I wonder if that could be the USB connector getting loose. If it's
> new, can you exchange it for another unit?
> 
> Bruno
>

Re: Driver issues, defective unit?

2012-01-21 by leckmichunten

Receiving data from the BCR always works fine.

I have tried 3 cables now, so I doubt it's a faulty cable. I have also tried 3 different USB ports, all with the same result. Other USB hardware (like a Frontier Alphatrack and a Korg Kontrol 49) work fine. I have uninstalled anything else connected via USB for the time being, to make sure it's not some driver conflict. But that didn't fix it either. So I'm pretty positive it's the BCR itself, that has issues, not the USB ports on my motherboard or a driver conflict with other USB hardware.

I read your mentioned section in the BC Manager now. Sadly although I have Midi ports, I don't have any cables. But I hooked up the BCR to another computer here and have issues there, too. On the other computer, the BCR installs fine, but BC Manager will freeze upon "Detecting B-Controls". The program itself runs fine if I answer "No" to the question if I wanna detect them. But as soon as I try to detect them, BC Manager will freeze and won't recover. I tried to reboot and reinstall the BCR multiple times, but BC Manager always hangs up.

Thank you for help, Bruno and Mark btw!!!





--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
Show quoted textHide quoted text
>
> --- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@> wrote:
> > BC Manager doesn't find it, Ableton gets incoming Midi messages but doesn't transmit any to it, nor does MidiOX.
> > 
> > I am out of ideas here. Is it defective?
> 
> I get the impression that the problem is only with the connection FROM the computer TO the BCR that is defective? (I.e. the "MIDI output device" from the perspective of the computer.) Is this so?
> 
> In any case, my guess at this point is that there is a hardware fault in the USB controller of your BCR, assuming it's not a cable problem.
> And have you ruled out a fault in the computer's USB hardware? Not that I think this is likely, but when things are this desperate... To check this, you might try connecting your BCR to a different computer.
> 
> You may want to look at question 42 in section 24 of the BC Manager Manual (p. 93), in particular point 3: basically this is about checking whether things do work if you connect the BCR to a computer via its standard MIDI I/O sockets. That should give you strong evidence that the problem indeed lies with the USB hardware.
> 
> You could also connect your BCR directly to a synth or master keyboard via MIDI: e.g. see if you can get the BCR to switch between presets by sending Program Change messages from the synth/master keyboard.
> 
> Hope this helps,
> Mark.
>

Re: Driver issues, defective unit?

2012-01-21 by Mark v.d. Berg

--- In bc2000@yahoogroups.com, "leckmichunten" <leckmichunten@...> wrote:
> I hooked up the BCR to another computer here and have issues there, too. On the other computer, the BCR installs fine, but BC Manager will freeze upon "Detecting B-Controls". The program itself runs fine if I answer "No" to the question if I wanna detect them. But as soon as I try to detect them, BC Manager will freeze and won't recover. I tried to reboot and reinstall the BCR multiple times, but BC Manager always hangs up.

I think this settles it:
Apparently a hardware fault in your BCR's USB controller causes the USB driver on the computer (and thereby BC Manager) to hang whenever an attempt is made to send data from the computer to the BCR.

It's a pity you can't check whether the standard MIDI sockets do work.
However, since your BCR is brand-new, it's very simply anyway:
you should either get a refund or a replacement.

Mark.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.