At 04:32 PM 5/19/98 -0400, you wrote:
>On Mon, 18 May 1998, Dan Walkowski wrote:
>
>> I have an even more frustrating Midi-to-Pic problem.
>> It is hard to describe, but there is some threshhold of speed, which varies
>> by the device, above which bytes get dropped.  The original MIDI device we
>> used for testing does not cause this behavior at all, and works perfectly
>> no matter how hard we drive the circuit.
>
>  This sound like realtime sysex MIDI messages and/or controller data
>(aftertouch, for example) barreling on through.
>
>  Also, are you handling "running status" message modes correctly?

Assuming they have the same structure as other MIDI messages, then yes.
We read every byte, discarding all until we see either a note on or a note
off.  When we do, we read the next 2 bytes, to get the velocity and note
number.  We act on that message, and then go back to looking for note on or
note off messages.

We can send messages as fast as they can be generated from midi device #1,
and nothing gets dropped.  With other midi devices, if we send messages
close together, the second one gets dropped.  If they are sent slower, they
work.  Note that 'too fast', in this case, is still nowhere near full MIDI
throughput, even though we can handle that from the first device.

It seems like it must be some sort of circuit problem, and not software. (?)
Any additional ideas?  Am I missing something?

Dan