Bc2000 (for the BCF2000 & BCR2000)

New episode

At your suggestion I did a renewed install of the Behringer drivers. Immediately things deteriorated. Yes, usb-apparaat is now BCR-2000 but  BC manager does not recognize the BCRs anymore (B-controls is empty). input and output meters In my apps they are working in the sense that one controller has input and output, the other one only output (meaning: it receives no feedback from the DAW).

I do get a message from windows that there is an i/o error but it's unclear from which device. I will have start all over again.....



--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "diddywahdiddy1" <550@> wrote:
> > Maybe change the message? It was rather confusing to me. I thought it 
> > was actually polling for devices and getting a response.
> 
> By "message" you mean "Offline" in the Personality column?
> 
> > Strangely, the USB devices are both called USB device (USB apparaat) in 
> > the B-controls list. But in the midi devices list they are called as below.
> 
> This suggests that the two BCR "contexts" in the B-Controls list are BOTH using the SAME MIDI I/O devices, namely the ones called "usb apparaat".
> You can edit the MIDI I/O devices of each BCR context in the MIDI -> Options dialog box.
> 
> > Yup, I installed Behringer drivers but was advised to deïnstall 
> > somewhere on the net.
> 
> Well, I can only say I disagree completely...
> 
> For one thing, the Microsoft drivers are "single-client": you can only connect one application at any moment in time to a particular port.
> The Behringer drivers allow you to connect as many programs simultaneously as you wish.
> 
> > I have a standard XP sp3 OS
> 
> I have XP+SP3 myself, and I can warmly recommend Behringer's 1.2.1.3 driver.
> This is the only driver that creates fully correct, transparent, persistent I/O device names, including the Device IDs, and (in U-2, U-3 and U-4) the correct port letters of the MIDI IN and OUT sockets.
> For instance, a BCR with Device ID 1 gets called "BCR2000[1]".
> So in your case you could then set the second BCR's Device ID to 2; this BCR will then ALWAYS be called "BCR2000[2]", even if you haven't switched the other BCR on.
> Basically you'll always know which is which.
> 
> >  > (I suppose that if you put BCR2 in U-3, you get names like "usb 
> > device (2) [2]" or something?)
> > 
> > I have seen that happening :)
> 
> Yes, me too, actually. I have one BCR and one BCF, but the Microsoft driver doesn't distinguish between those two either, so it gave me the same "device (2) [2]" headaches...
> 
> Best wishes,
> Mark.
>