Bc2000 (for the BCF2000 & BCR2000)

Hi Mark,

The software-update came just in time. I was already about to ask you if you could include an option to send those messages in MidiTools ;-). Well done!

I just tried out the new version and set the Timing Clock ($F8) to 500 BPM and the Active Sensing Timing ($FE) Interval to 250ms. In addition I clicked some keys of the virtual midi-keyboard and recorded all messages with the MIDI-Monitor.

The Hardware-Setup was as in the last test: Soundcard MIDI-Out -> BCN44 MIDI-In, BCN44 MIDI-Out -> Soundcard MIDI-In

The result in this case is that all messages could be received correctly. $FE, $F8 and the note-on messages from the virtual keyboard all come in in realtime with no delays.
From this result i have to conclude that the BCN44 is working properly and that the reason for my delay-problems must be my Yamaha PSR310. Maybe it sends additional brand-specific (non-standard) messages that can't be processed by the BCN44 and confuse it.

I recently found someone else who had similar problems with a Yamaha PSR290 keyboard and the BCN44. Unfortunately he got no responses that might explain the reasons for it:

http://acapella.harmony-central.com/showthread.php?1324442-Behringer-B-Control-BCN44-ISSUES!

Thanks,
electron8000

> I've released a new version of MIDI Tools.
> This includes a "MIDI System" window, which allows you to send nearly all types of MIDI System messages for testing purposes: Exclusive, Common and Real-time.
> (Incidentally, this version also fixes a small but annoying bug in the MIDI Keyboard window.)
> See http://home.kpn.nl/f2hmjvandenberg281/miditls.html .
> 
> So if you're still "on the case" of your BCN44's MIDI Merge, you can now have MIDI Tools generate Timing Clock and/or Active Sensing messages in conjunction with Note messages from the MIDI Keyboard window.
> Maybe in this way you can determine whether it's indeed the Timing Clock and/or Active Sensing messages that mess up your BCN44's MIDI Merge - if you need any further confirmation.