Re: [Jack-Devel] Dispersing MIDI messages: one to multiple

Sure, and that will certainly continue in future that some MIDI keyboards are 
sold using MIDI Running Status (even though the ratio is declining since USB 
MIDI). But that's not the point. The design decision of JACK is simply that 
JACK client developers can safely assume that they don't have to handle 
Running Status and instead the respective MIDI input driver of JACK must take 
care of that, that is if the OS's MIDI subsystem does not handle it already. 
For example the ALSA MIDI driver handles RS and the CoreMIDI driver of JACK2 
handles it (the CoreMIDI driver though was just equipped with that because a 
user reported that he encountered RS with CoreMIDI, which turned out to be 
false later on).

So if you encounter MIDI RS with JACK, then this is a bug and the respective 
MIDI input driver in JACK must be fixed.

CU
Christian

On Saturday 31 January 2015 07:16:36 Happy wrote:
> For whatever it is worth, many older devices any even modern devices
> (For example I can guarantee it for the Roland TR-8, released in 2014)
> still apply running status on their MIDI outs.
> 
> On 五, 2015-01-30 at 18:13 +0000, Harry van Haaren wrote:
> > On Fri, Jan 30, 2015 at 2:29 PM, Happy <[hidden]> wrote:
> > > Consider to check for "MIDI running status"?
> > 
> > Actually the JACK MIDI spec states that running-status is not allowed,
> > and all MIDI notes should be normalized:
> > https://github.com/jackaudio/headers/blob/master/midiport.h#L62
> > 
> > It makes it a lot easier for applications to implement MIDI : and
> > places the running status-byte check burden on JACK MIDI
> > implementations instead of in every JACK MIDI client. Thanks JACK devs
> > 
> > :D
> > 
> > Cheers, -Harry
> 
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

1422700898.26359_0.ltw:2, <201501311050.17259.schoenebeck at crudebyte dot com>