Bc2000 (for the BCF2000 & BCR2000)

Hi,
This is my first foray into BCMan  except I brifly had a chance to 
try the last revision of BCMan and never got further than poking 
around the controls of the program.
Now I am trying again with 1.30 and am instantly getting a error 
window during the "Detect B-Controls" that says

Error:Midi system exclusive error
Wrong Model
Address: 00496250

When I click OK I get another error that says:

Error: Cannot store short MIDI input message
Address: 0048FDD4

Then I can click ok indefinately and the error repeats over and over 
again forcing me to force quit the app.
Any ideas?

I have both a BCR2000 and a BCF2000 each connected to individual midi 
input and output ports of an older model MOTU Midi Express XT.
I am using presets S-3 on each device and am using midi output 2/thru 
on each device.
Windows XP, SP2 Both units upgraded to latest firmware yade-yade...

Ok, these errors are happening even with both Behringers turned off 
and a fresh install including deleting the .ini file that was left 
after uninstallation.That only leaves my Motu setup (factory setting 
1) or the app or my software environment.

--- In bc2000@yahoogroups.com, "islandgroove2002"
<islandgroove2002@...> wrote:
> Now I am trying again with 1.30 and am instantly getting a error 
> window during the "Detect B-Controls" that says
> 
> Error:Midi system exclusive error
> Wrong Model
> Address: 00496250
> 
> When I click OK I get another error that says:
> 
> Error: Cannot store short MIDI input message
> Address: 0048FDD4
> 
> Then I can click ok indefinately and the error repeats over and over 
> again forcing me to force quit the app.
> Any ideas?
> 
> I have both a BCR2000 and a BCF2000 each connected to individual midi 
> input and output ports of an older model MOTU Midi Express XT.
> I am using presets S-3 on each device and am using midi output 2/thru 
> on each device.
> Windows XP, SP2 Both units upgraded to latest firmware yade-yade...
> 
> Ok, these errors are happening even with both Behringers turned off 
> and a fresh install including deleting the .ini file that was left 
> after uninstallation.That only leaves my Motu setup (factory setting 
> 1) or the app or my software environment.

This is all very nasty: it seems a conspiracy of worst case scenarios...

The first error message ("MIDI system exclusive error - Wrong Model")
indicates that an Identity Request sent from BC Manager during
auto-detection has been answered with a System Exclusive message from
a Behringer model other than a BCF or BCR. I don't quite understand
how this can happen in your situation: I'm curious what the actual
offending received message. (The MOTU isn't Behringer-made, is it?)
In any case this error message shouldn't be fatal. (But anyway I'll
see if I can improve BC Manager's auto-detection algorithm, so that
you don't get this first error message.)

The second category of error messages is the really disturbing one. It
indicates that BC Manager's MIDI input buffer for "short" (i.e.
non-System Exclusive) messages is full. This buffer can contain 4096
messages, so what's apparently happening is that the MOTU sends a
continuous stream of "short" MIDI messages to the computer - maybe
"Autosensing" ($FE). In any case BC Manager itself does NOT send any
"short" MIDI messages during B-Control detection - only SysEx ("long")
 ones.

BC Manager regularly clears this MIDI input buffer, so this buffer
should never overflow. There are several reasons why this might go
wrong in your case:
- The FIRST ("Wrong Model") error message window might cause this
regular buffer clearing to be too slow - although I can't see how this
could happen. (Have you tried clicking away this first error message
IMMEDIATELY after it appears? Do you then STILL get the second category?)
- Your MOTU (or some feedback loop) causes a STRUCTURAL overflow of BC
Manager's short message buffer.

To establish what's causing this short MIDI message buffer overflow,
try the following procedure:

1. I've uploaded a special, "safe" version of BCMan.ini to the BC
Manager folder (under Applications) in the Yahoo group's file section:
"BCMan130Safe.ini". Copy this file to the folder on your harddisk
where BCMan.exe is located, and rename (or better: copy) it to
"BCMan.ini".

2. Switch off all BCs, and disconnect ALL your MIDI cables from your
computer/MOTU. Then start BCMan.exe: all MIDI I/O ports are now
disabled (cf. Options -> MIDI devices), and no auto-detection takes
place (cf. Options -> Detect B-Controls), so you should not get any
error message windows.

3. Open the MIDI input message window, either via the main window's
View -> MIDI input messages (general) or by clicking on the
red-striped button on the main window's toolbar. In the MIDI input
messages window, click on the Record button. (No messages should start
being recorded at this stage, since no MIDI input ports are enabled yet.)

4. Open the MIDI devices dialog box (via Options -> MIDI devices),
enable one of the relevant MIDI input ports, click OK, and watch the
"MIDI input messages" window: do any input messages start appearing
(and which ones)? Or do you get those "short message" error windows
again? As long as all remains well, you can enable the other relevant
MIDI input port(s), and after that your MIDI OUTPUT ports.

5. If you STILL have no problems at this point, you can connect and
power on your actual BCs. Then go to the B-Controls window, link each
BC 's MIDI I/O ports via the MIDI options window (MIDI -> Options),
and execute "Receive identity".

Let me know how far you get. Good luck!

Mark.

Thanks for your help, so far so good with your instructions up until 
receive ident which is only working with one Behringer device at a 
time. 

>I did some basic messing around with one preset and skimmed ther 
manuaL.
I see there's going to be a bit of a learning curve figuring out how 
exactly things work in BCMan:)

If I remove the "safe" .ini file the errors continue upon launch 
although I did manage to click through "both" error boxes quick enough 
to get into the program.
Then I disabled all of the uneeded midi ports and set the midi channels 
for both Behringers.Once again only the Identity for one device is 
shown.
Just for "fun" I re-enabled all of the midi ports and everything still 
works without any error messages.

http://www.youtube.com/watch?v=pPsqoUsc9pI&NR=1



--- In bc2000@yahoogroups.com, "islandgroove2002"
<islandgroove2002@...> wrote:

>
> Thanks for your help, so far so good with your instructions up until 
> receive ident which is only working with one Behringer device at a 
> time. 
> 
> >I did some basic messing around with one preset and skimmed ther 
> manuaL.
> I see there's going to be a bit of a learning curve figuring out how 
> exactly things work in BCMan:)
> 
> If I remove the "safe" .ini file the errors continue upon launch 
> although I did manage to click through "both" error boxes quick enough 
> to get into the program.
> Then I disabled all of the uneeded midi ports and set the midi channels 
> for both Behringers.Once again only the Identity for one device is 
> shown.
> Just for "fun" I re-enabled all of the midi ports and everything still 
> works without any error messages.
>

--- In bc2000@yahoogroups.com, "islandgroove2002"
<islandgroove2002@...> wrote:
> Thanks for your help, so far so good with your instructions up until 
> receive ident which is only working with one Behringer device at a 
> time. 

> If I remove the "safe" .ini file the errors continue upon launch 
> although I did manage to click through "both" error boxes quick enough 
> to get into the program.
> Then I disabled all of the uneeded midi ports and set the midi channels 
> for both Behringers.Once again only the Identity for one device is 
> shown.

Very strange. Does this also happen when you execute "Receive
identity" manually from the "B-Controls" window for the unrecognized
Behringer?
And does it help to increase "Waiting time ..." (e.g. to 1000 msec) in 
the "Detect B-Control options" dialog box?

> Just for "fun" I re-enabled all of the midi ports and everything still 
> works without any error messages.

I haven't had time yet to really get to the bottom of this problem,
but in the new version of BC Manager (1.4.0) you can at least skip the 
auto-detection on first startup (i.e. when no previous ini-file
exists), so that should help a bit. So you shouldn't need the special
"safe" ini-file any more - but you still might have to set "Startup
detection" in the "Detect B-Control options" dialog box to "None".

Mark.