W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 18992] Running status should be prohibited

From: <bugzilla@jessica.w3.org>
Date: Fri, 16 Nov 2012 11:07:48 +0000
To: public-audio@w3.org
Message-ID: <bug-18992-5429-kslWBxWG5X@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18992

--- Comment #10 from Florian Bomers <w3c_bugz@bome.com> ---
The fact that CoreMIDI disallows running status was already part of Yamahas
original request to ban running status. 

I don't think that a limitation on ONE system is a good enough reason to limit
a cross platform API. I think it's more important to create an API that is
generally useful and makes sense, than to find the common denominator of
functionality available in today's OS's.

We do the right thing with timestamped messages: although on some OS's, the
webmidi implementation will need to create an own scheduler, there is still a
way for sending timestamped MIDI messages.

So I think it's still the right thing to discourage running status but not to
prohibit it. As previously said, Yamaha's concern that a receiver might not be
able to understand running status is not reasonable. The disclaimer might even
say that sending a message with running status might not work the same on all
OS's. Then the CoreMIDI implementation does not need to take care of undoing
running status, though it's really not that hard.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 16 November 2012 11:07:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:03 UTC