Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "duncanfoster" <duncan@...> wrote:
> I had worked out that
> I could use the U3 setting and connect up my BCF2000 to a Yamaha LS9
> digital console to provide some testing options when programming the
> encoders and faders with BC Manager.
> 
> When I was testing the thru function I could make the NRPN and CC
> (faders and encoders) messages work fine but the sysex messages for
> the Yamaha Cue (i.e. PFL) functions (on a row of buttons) would not
> work. I downloaded the settings to the BCF  but they would not work
> until I reconfigured the BCF to S1.
> 
> Am I missing some config option for the thru function?  eg filtering
> sysex somewhere?  I could see the sysex traffic on the BC Manager
> midi metering as I expected but the console just would not respond to
> the Cue control until I set the BCF to S1.

BC Manager's thru function is COMPLETELY passive. All it does is tell Windows to connect a MIDI input device to an output device: Windows then handles all traffic automatically; and no special settings are involved.

The fact that you can indeed see the SysEx traffic in BC Manager's meters seems to confirm that the problem doesn't lie with BC Manager itself.
However, to be even more sure that BC Manager isn't interfering, you might try the generic "MIDI Tools" program (available via http://home.kpn.nl/~f2hmjvandenberg281/miditls.html), which provides exactly the same thru functionality, but doesn't actively communicate with the BCF (or any other MIDI device).

Are we talking about a bidirectional connection between your BCF and LS9, or just a one-way connection from the BCF to the LS9?
One thing to realize is that the BCF's buttons/encoders/faders do not respond to parameter changes sent from the LS9: this only works for CC, NRPN etc.
But SysEx messages sent from the BCF to the LS9 should work - I can't immediately think of a reason why it would be different for S-1 and U-3. (Unless there's something invalid about the SysEx messages themselves (e.g. no final $F7 byte) that causes Windows to modify them in a negative way??)

You can examine all incoming MIDI messages in BC Manager or MIDI Tools via the "MIDI input messages" window. That might tell you if there's something wrong with the actual SysEx messages.

Mark.