Bc2000 (for the BCF2000 & BCR2000)

Thanks very much for your update.  I don't have access to the LS9 at the moment but will try again in a week or so.   

> 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).

I think I did try once using the thru function of Midi-OX but can't remember the details clearly as it was at the start of my experiments.
 
> Are we talking about a bidirectional connection between your BCF and LS9, or just a one-way connection from the BCF to the LS9?

Yes this was a bi-directional setup.  I could move the faders on either the LS9 or the BCF and make the other move.

> 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.

Got that after much reading and a few experiments :-}

> 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.
>
Thanks again for your input. I will post one of the sysex strings when I can get to the LS9 again.  

Duncan