Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

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

Message

Re: TWO BCR as controller

2011-02-28 by diddywahdiddy1

Your suggestion of isolating the problem was exactly what I started out with this morning. I turned down the computer and started up with 1 BCR (the new one) to see if it functioned with the sysex that I had been using for a year now with my DAW. That way I would know whether the new BCR wasn't working properly.
Here's what I found:

shut down computer
connect and switch on NEW  BCR
reboot

1. NEW BCR, cable 1

BCm detects 1 device = online
I send sysex uploads OK
test in DAW (REAPER) = ok (both send and receive signals)
test in Audiomulch = ok 

shut down computer
shut down and disconnect NEW BCR
connect and switch on OLD BCR
reboot

2 OLD BCR, cable 2 
reboot with BCR switched on and connected
BCM detects 2 devices (!)
device 1 is online and using correct firmware
device 2 is offline
I send sysex, uploads OK
test in DAW = OK (both send and receive signals)
test in Audiomulch = OK

shut down computer
connect and switch on NEW BCR (Now both BCR's are connected)
reboot

3 both BCR's
BCM detects 1 device
midi devices shows
input: usb device, usb device (2), usb device [2]
output: usb device, usb device (2), usb device [2], usb device [3]
I check usb device and device (2)

BCM detects 2 devices
device 1 is online
device 2 is offline

Yet when I check the midi input both devices show that there is signal

test in DAW = OK (both send and receive signals)
test in Audiomulch = OK

So, now both BCR's are working properly!!! Is it the BC manager that confused me all the time? Yes, but have been other issues as well. It was a very puzzling adventure but, somehow, I now am there where I want to be. I will try and see how stable this is in the next few days and if anything comes up post about it here.

At the Reaper forum there are a few examples of people using multiple BCR's and BCF's in a studio.
http://forum.cockos.com/showthread.php?t=46524

There's also a thread about different setups for getting Reaper to send feedback to the BCR and how to connect it.
http://forum.cockos.com/showthread.php?t=33149

--- In bc2000@yahoogroups.com, "Mark v.d. Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "diddywahdiddy1" <550@> wrote:
> > Okay, so  a lot happened last few days but I'm still not where I want to be. I have:
> > - done all the hardware testing (cables, etc). 
> > - Installed Behringer drivers and UNinstalled them.
> > - Tested on two different pc's
> > 
> > Both BCR's are U1 and each has its own ID.
> > 
> > BCmanager detects two devices and lists them. However 1 of the 2 is offline. And there is NO way of getting it online. I wouldn't know how to try......
> 
> I think what we need to do is try to isolate the problem. I don't have a clear-cut answer right now, but I'll make some suggestions and hopefully we'll get there in the end:
> 
> First question: is it always the same physical BCR that remains offline?
> 
> To test this, have you tried swapping the two BCRs?
> Just to be safe: first switch off both BCRs and the computer. (Personally I don't take any risks: I never connect/disconnect the USB cable at either end whenever either the computer or the BCR has been powered on. ONE defective USB controller on a BCR was enough to scare me for life in this respect!)
> Then disconnect the USB cables from the BCRs, power the BCRs on (yes, completely isolated!) and swap their IDs via "Global Setup".
> Power them off again, connect the SWAPPED USB cables, power the computer on, and finally power the BCRs on.
> To the computer (including USB drivers and BC Manager) it should then be as if nothing has changed:
> Start BC Manager and see which BCR is offline. If it's the one that was offline previously, there must be a hardware problem with that BCR (probably its USB controller).
> On the other hand, if the problem has now moved to the other BCR, your BCRs are fine and there is a software problem at the computer side (although that would be a bit strange, since you've tried several computers).
> 
> Which operating system are you using exactly, and which USB drivers?
> 
> > When I try to send the firmware syx ( bcr2000_1-10.syx ) I get an error message
> > -------------------
> > Error: MIDI system exclusive error
> > Wrong command
> > Send Memory(34)
> > This may be the result of a feedback loop
> > Message1
> > --------------------
> 
> As long as a BCR shows "1.10" after powering it up, its firmware is completely OK (because on startup the BCR performs a checksum test of its firmware), and there is absolutely no point in trying to restore the firmware.
> 
> What caused the above error message is a different matter:
> You used BC Manager's "Send firmware" operation (rather than an external SysEx uploader such as MIDI-OX)?
> If so, the "Send Memory" message that BC Manager received (and complained about) can only be a message that it had just sent itself, so there must indeed be some feedback loop; this seems very strange, assuming that your attempt at uploading the firmware went to the USB device of the BCR.
> 
> One common cause of loops is virtual MIDI ports. Do you have any virtual MIDI ports (e.g. MIDI Yoke) installed?
> If so, you should disable all of them in BC Manager's "MIDI devices" dialog box (at least for now).
> 
> Hope this helps,
> Mark.
>

Attachments

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.