W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

Re: [Bug 18992] Running status should be prohibited

From: Chris Wilson <cwilso@google.com>
Date: Wed, 26 Sep 2012 11:13:02 -0700
Message-ID: <CAJK2wqUhUf0AdMcRASygfXu1p5gWiNEOhqeffjR9z6sd+kBUtw@mail.gmail.com>
To: Ray Bellis <ray@bellis.me.uk>
Cc: public-audio@w3.org
Oh, I KNOW about it.  :)  It made a lot of sense, I think, back when MIDI
was typically running on a 31.25kb serial connection, and it took the time
to send a message from 3/4 of a millisecond to 1/2 a millisecond.  Over USB
2.0 (35 MB/s), I think it's not really necessary - or at least, not
necessary enough to force state maintenance between MIDI messages.  It
would be interesting to know how many MIDI software packages still support
it.

On Tue, Sep 25, 2012 at 11:53 PM, Ray Bellis <ray@bellis.me.uk> wrote:

> On 25/09/2012 19:00, bugzilla@jessica.w3.org wrote:
>
>> Heh. Just wait until you realize that Running Status is *THE* reason why
>> a MIDI Note On message with a velocity of zero is explicitly the same as a
>> MIDI Note Off. That way, you can compress a dense passage of note on/note
>> off messages by 33%.
>>
>
> I'm surprised people don't know about Running Status.
>
> I implemented it in the MIDI -> CV convertor I designed for my Electronics
> A-level back in 1986...
>
> When you only have 31.25 Kbps of bandwidth that compression helps a lot!
>
> Ray
>
>
Received on Wednesday, 26 September 2012 18:13:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 26 September 2012 18:13:34 GMT