Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "Berk Aarts" <B.E.R.K@...> wrote:
> if everything works, can you tell us what you had to do exactly ?

I'm not sure how Diddywahdiddy1 sees this, but here are my thoughts:

I think that troubleshooting a BCF/BCR setup has three main stages:

1. The BCF/R itself:
- Has the latest firmware (1.10) been installed?
- Do all the buttons/knobs/faders work?
- Have you set up the correct operating mode (S/U-1/2/3/4) and device ID?
- Does the USB controller work?

2. The MIDI/USB cables.
- Are they connected correctly?
- Does the USB hub work correctly?
Etc.

3. Only required in U-1/2/3/4 mode: the USB driver software on the computer.
- Are you using the best USB driver for your OS?
- Are there any interfering left-over USB drivers?
Etc.

4. The set-up of any audio software using the BCF/BCR(s).
- Does the software use the correct MIDI I/O ports?
- (In the case of BC Manager:) Is the right Device ID being used?

Ideally these stages should be checked in this order, since an error at an earlier stage will affect all following stages.
In this sense, the USB controller on the BCF/BCR is a complicating factor: even if it's defective (which has occurred to me and several other people), it often only affects the working of your audio software, which can be very confusing.

But in this particular case with 2 BCRs, the root of all problems turned out to be the USB driver, namely Microsoft's default "USB Audio Device" (or "usb apparaat" in the Dutch version).
This driver caused several problems:

- The MIDI I/O port names were confusing.

- The port names changed dynamically for the 2 BCRs:
If the "first" BCR wasn't switched on, the "second" would get the first's port names.
Note that this also complicated the troubleshooting process: by trying to isolate the problem (by switching only one BCR on), the SITUATION was changed crucially - causing further confusion!

So replacing the Microsoft driver with the Behringer 1.2.1.3 took away the root of all problems.
It then just remained to clear up the lingering "fog", by configuring BC Manager correctly.

And of course it's crucial never to change a BCF/R's operating mode or device ID on the BCF/R itself while an audio program like BC Manager is running.

Incidentally: in response to Diddywahdiddy1's complaint about BC Manager's status messages, the upcoming version of BC Manager (see http://home.kpn.nl/f2hmjvandenberg281/plans.html) will probably indicate the status of the MIDI I/O ports more explicitly in the B-Controls window:

I'm thinking of changing "*Name" into "DISABLED Name" and "(Name)" into "ABSENT Name".
Although these longer tags may look a bit ugly, they should help to avoid further confusion in cases where there is a setup problem.
Anyone please let me know if you have a better idea.

Mark.