Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, karel skakal <s_y_nagual@...> wrote:
> Reading (your?) manual, I updated the midi driver to 1.2.3.1 or something...

Yes, USB-based MIDI driver 1.2.1.3.
Indeed a fine choice! (In any case the errors you've been experiencing have nothing to do with the type of driver you've installed, so don't waste your time installing other drivers.)

By the way: are you using the latest version of BC Manager (2.0.3)?

> Actually I got it working now, just this window always starts.

"Always"?
You're not talking about the startup sequence of BC Manager, are you? Unless I'm very mistaken, BC Manager doesn't send this type of data when you start BC Manager.
The error messages in your screen dump seem to concern a "manual" data dump (e.g. via "Send all data"), so I suppose you're talking about that?

> It says BCL errors and the line is loooooooooong
> Line 1:$rev R1
> Error 4:invalid model
> 
> Line 2: $global
> Error 6: no blocks defined
> etc...
> I will take a snapshot and send it to you.

OK, thanks, that's very helpful.

The error message concerning line 1 is the crucial one: as far as I can think, this error only occurs when a BCR2000 definition ("$rev R1") is being received by a BCF2000.
(See "BC MIDI Implementation.pdf", section 21.7.)
All the other messages follow directly from the fact that the $rev statement is incorrect.

So do you have a BCF2000 running simultaneously?
Maybe your MIDI routing is such that this BCF (also) receives the BCL message chain, which causes the BCF to spew out all these messages.

However, even if this is so, I still don't immediately understand WHY this BCF responds at all to the messages intended for the BCR.
At least, the SysEx MIDI messages (containing BCL statements) that BC Manager generates, include a Model ID (14h for the BCF, 15h for the BCR), and as far as I know a BCF does NOT respond to a BCR message (i.e. to a message with Model=15h).

So are you sending a "third-party" syx file containing the "wildcard" Model ID (7Fh)? That would explain the problem: in the case of 7Fh, both the BCF and the BCR try to process the embedded BCL message, so then a BCF notices that "$rev R1" is invalid (it expects "$rev F1"), etc.

I've just checked: e.g. Behringer's bcr_FACTORY_PRESETS.syx (which contains the 'all controls' preset occurring in your screen dump) indeed uses 7Fh for Model ID, so upon reception of these messages a BCF indeed returns those error messages, which BC Manager then conscientiously reports.

Hope this helps,
Mark.