Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "sexontony" <sexontony@...> wrote:
sexontony wrote:
> Do I have to press any buttons on my BCR2000 also to receive data from 
> BC Manager?

No, you don't have to do anything on your BCR, except that you have to 
make sure that it's not in Global Setup mode (in which case it doesn't 
receive ANYTHING).

> What I did was:
> - start BC Manager
> - set the correct midi devices for input and output (USB Audio Device)
> - my BCR2000 is in U1 mode

> - select preset 32 on my BCR2000
This should be unnecessary.

> - select preset 32 on "BC Manager.BCR2000: Presets"-window and then in 
> this window selecting menu MIDI.Send
> 
> The result is the window "BCR2000: send preset 32" appears with some 
> info (Lines to send: 831 (22393 bytes) but the sending process does not 
> continue, it just remains in this state.
> Do you have any ideas what could be the reason for this behaviour?

Well, BC Manager's "send preset"-routine uses a handshaking protocol:
it sends a message, then waits for the BCF/BCR to confirm that
message's reception before sending the next message. But of course
this doesn't tell us what exactly is wrong.

Did you try pressing the "Receive Identity" button? If that also
didn't work, that would be further indication of a basic problem with
the handshake connection.

In view of your later message mentioning the newer USB driver solving 
the problem, it might indeed have been a problem with the older
drivers (Windows' "USB Audio Device", possibly Behringer's own
1.1.1.0/1 as well). I must admit that I've only tested BC Manager with
1.2.1.3 (and never had any problem with it, at least not in this
respect). I'll see what happens when I revert to the other drivers.

By the way, the upcoming BC Manager 1.3 will include an autodetection 
feature, which should facilitate working with any USB driver.

> Maybe its just a question of setting the parameters right in BC
> Manager like in the menu.Options.Midi devices."Timer tab"
> -  Resolution (msec) (default: 1)
> -  Gauges.Window (csec) (default: 40)
> -  Gauges.Update frequency (csec) (default: 10)

The Timer tab has absolutely nothing to do with this problem. (It only 
affects the MIDI meter windows.)

Mark.