Bc2000 (for the BCF2000 & BCR2000)

***STOP PRESS*** ***STOP PRESS*** ***STOP PRESS*** ***STOP PRESS***

Starting with the head line: It's working again!

I don't know how exactly, but after rebooting for the n-th time and restarting BCM with default settings suddenly I saw that BCM recognized two (2!!!) BCR's. I had not done anything other than I had during my previous sessions, but apparently these things happen (as all people working with technology know). I always credit it either to voodoo or an itch in the software that has disappeared.

Okay, everyone who's been cracking their skulls on this one: thanks.

js

oh, btw: wouldn't it be a great idea to start a Facebook group on the BC Manager subject?

--- In bc2000@yahoogroups.com, "diddywahdiddy1" <550@...> wrote:
>
> hi Mark
> 
> yes, I am using the latest version. I can see the absent and/or disabled state messages when they are appropriate. The thing is that the BCM refuses to show the second BCR. I can see that they are both connected, in the windows sound device info AND in BCM itself in the device list. But I am unable to connect the second device.
> 
> I use the BCR's to control Reaper DAW (controlling 16 channels, volume, panning, mute and send and start.stop.record.loop and what not). Reaper both receives and sends mid control messages. The second BCR is now unable to receive the control messages of Reaper. So BCR1 is able to send and receive and BCR2 is able to send but not receive.
> 
> What bothers me the most is that I cannot control the BCR2 in BC manager. Even if I set up manually (add BCR2000, set the deviceID, etc) BC Manager is not able to connect to it (as stated in my previous message).
> 
> 
> > Are you using the most recent version of BC Manager (2.3.1)?
> > This version has slightly more informative status messages in the MIDI input/output port columns in the B-Controls window than previous versions.
> 
> ANd last but not least: I cannot get BCR2 into default/factory settings (using exit/store while booting up). I do get the 'init' message but then things return to their previous setting.
> > 
> > Quoting from the manual:
> > 
> > "For clarity, the name of a disabled MIDI I/O device is no longer prefixed by an asterisk (*), but by `DISABLED ', and the name of an absent MIDI I/O device is no longer written between parentheses, but prefixed by `ABSENT '."
> > 
> > So what do these columns show for your 2nd BCR?
> > If there's "DISABLED" or "ABSENT" somewhere, the problem has to do with the BCR's USB device:
> > 
> > "DISABLED" can be corrected in the main window's "MIDI devices" dialog box by enabling the MIDI I/O device.
> > 
> > "ABSENT" means that the MIDI I/O device name you've been using in BC Manager is currently invalid. In the "MIDI options" dialog box of the BCR you should select an EXISTING (and enabled!) MIDI I/O device.
> > 
> > And of course the actual BCR's ID# should match the ID# defined in BC Manager (which can also be set in the "MIDI options" dialog box of the BCR).
> > 
> > For further information (in particular possible causes for the "Offline" message), see BC Manager Manual (for vs. 2.3.1), p. 32.
> > 
> > Hope this helps,
> > Mark.
> >
>