Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, James Glover <james.glover@...> wrote:
> I have attached the sysex files I am trying to use.
>  
> I change to U-1 as well, although I think on of the sysex files
changes it to U-3.

First of all: not that it matters much, but in any case the files you
sent me DON'T alter the U-mode. I know this because I've converted
them to text files via the "Convert" utility from BC Manager's main
window: I saw then that there simply are no "$global" sections (let
alone containing ".midimode" statements) in these two files.

I then uploaded the presets to my own BCR (in U-3 mode) from both BC
Manager and Sonar 7: no problems whatsoever.

I also looked at the syx-files themselves: from what I've seen, the
message indexes (related to error 22) seem totally OK.

However, on the "forensic" side, I did notice that one of the files
uses the generic $7F for both the "Device ID" and the "Model ID", so
this file was definitely not generated by BC Manager - did you use
Royce's editor? (The other file WAS probably made in BC Manager, using
$00 for Device ID and $15 (="BCR2000").)

Model $7F CAN create problems if you have both a BCF and a BCR
switched on: e.g. if a BCF2000 receives your sequence for the BCR with
the generic Model ($7F), the BCF shows "Er 6" in its display (and
returns a host of "error 6" messages via MIDI): this is because the
BCF feels "spoken to" by any message containing Model $7F - but it
then rejects the actual BCL (preset) data, since that is for the BCR
only. In other words: it's a bad idea to use Model=$7F in BCL dumps,
since it makes any  receiving BCF start balking at BCR data, and vice
versa.
Anyway, since you're having problems with both files, I can't imagine
that the Model $7F's are in any way responsible for your problem.

Some pretty cool use of "ifn"/"ifp", by the way!

> I'm trying again now, and it seems something is very wrong.
>  
> Sometimes the sysex file starts to load, and in fact sometimes most of 
> the buttons light up. But then other times I get a message saying:
>  
> "Error: Error preparing MIDI input header. There is no driver installed 
> on your system. Address: 004B2B2D"
>  
> And this is when I've just tried the same sysex file in the exact same 
> way 20 seconds earlier and it started to load!

This is VERY telling: "There is no driver installed on your system"
indicates that the USB connection (as maintained by Windows) between
the BCR and the computer has been lost, i.e. behind BC Manager's back
while it's been running.

Personally I get the very same error message when I simply switch off
my BCR while running BC Manager, and then still try to send something
to the BCR from BC Manager.

In your case, this sudden connection loss MIGHT be due to a problem in
Windows, but in all likelihood it probably indicates that your BCR's
USB controller is defective. Several people in this forum have
reported something similar, and in fact I myself had a BCR that kept
shutting down the connection in mid-operation - ultimately I went back
to the shop and they gave me a new one (it was still within the 2-year
warranty period): the new one has never given me any problems - I
didn't even reinstall any drivers or whatever.

However, even my BCR with the defective USB controller never had any
problems via the standard MIDI ports (S-1/2/3/4). So if you can hook
your BCR up to your computer via e.g. your sound card's MIDI ports and
set the BCR's to an S-mode, you can try to see if you can upload your
presets then. My guess is that you can indeed - that would then
confirm that there is no software problem with either your presets or
BC Manager (or any other program), or even with your BCR's Global
Setup. Little consolation, though, but at least you'll know where you
stand.

It may be time by now to lodge a collective complaint or appeal or
insult or threat to Behringer about their faulty USB controllers! Any
suggestions, anyone?

> When I get the error message I have to close it about 20 tiumes
before I 
> can close BC Manager!!!

Yes, that's because BC Manager maintains 16 buffers for SysEx messages
- I recently tried to make things work so that you only get ONE error
message, but it's kind of complicated.

Mark.