[sdiy] Midi CC update rate question

[Ingo Debus]

Am 07.01.2012 um 21:23 schrieb Tom Wiltshire:

>> I suspect this is quite likely. Think about what one would have to do in a merge box to support running status from multiple inputs or even the simpler case, running on one and regular on other inputs. What would you do?
> 
> I'd reinsert the status bytes into each incoming message when I put it into the storage buffer. E.g. I'd store each incoming message as if it had arrived in full, without running status.
> Then I'd output bytes from the storage buffer, keep track of the current status and strip them out if possible when the messages go out - e.g. apply running status again to thin the output. It might be a be of a pain, but it's not exactly impossible.

That's pretty much how I do this in my projects. Multiple inputs are no problem, you just have to memorize the status for each input separately.
Careful, on the transmitting side don't use running status too consequently. Always insert a status bit every second or so even if it's redundant. Imagine this scenario: user turns on keyboard and plays one note. Then user turns on (or connects) sound module. If no other MIDI channel messages are being sent, status remains Note On all the time. The keyboard would not sent Note On status messages except for the first one, and this was missed by the sound module. It would just not play.

If you ask me, I don't think that there are many MIDI receivers out there that cannot handle running status. There are so many MIDI transmitters using it.

Ingo