Running status for DIN

[dlundqvist]

I don't think the MRCC will take 'long' MIDI messages and create running status versions.  I think what Darryl and Jesse are saying is that gear that sends running status is handled properly.

Well, that is exactly what it must/should do when message is from USB since the concept of running status does not exist there.

Again,  it's up to the sending thing (hw, sw) to generate running status, not up to any middleman since they have no idea what msg is coming next. 

USB in and of itself does not dictate whether running status is allowed.  The MIDI protocol defines the messaging.  USB is really just a transport mechanism.

Correct, USB is a transport for MIDI. But USB MIDI has no concept of running status, whereas DIN MIDI does. It's an integral part of it, and important for cutting down the number of bytes going over the wire. MRCC has it legs in both worlds, USB and DIN. Therefore I presume that it will handle running on DIN fine, regardless if it's input or output.

It's not up to the application, in the end, what goes over the wire (unless you write directly on the serial line). We all use different APIs, and the APIs I've seen so far all deal with complete messages. Then it's the actual transport that does running status or not. 

But API questions are moot, I have hardware (Roland GI-20) that may generate lots of MIDI data, and it does use running status. So I'm quite interested to know if MRCC will correctly preserve running status on DIN output, regardless whether other messages from other inputs have been merged into the output or not. If it can't, that's fine with me. Just means I have to find router/solution. I have no horse in this race, just want to find out if MRCC is a product for me or not.