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: Sat, 17 Nov 2012 13:51:54 +0000
To: public-audio@w3.org
Message-ID: <bug-18992-5429-8zI6w7HtHb@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18992

--- Comment #12 from Florian Bomers <w3c_bugz@bome.com> ---
Hi Chris,

I agree:
1) webmidi apps will never receive running status
2) it's a good idea to state whether running status is allowed in the send()
method.

"Discouraging" implies that running status is allowed (and the webmidi
implementation might need to parse the data for iOS, OSX and so on).

My main motivation for my reasoning is that I am not comfortable with API's
that try to "hold the hand" of developers, by restricting the API with
parameters or functionality that the *API* designers find useful. For me,
ideally, a MIDI API allows you to send and receive arbitrary bytes. It will be
the responsibility of the developer to send data that is meaningful to the
receiver.

But obviously, the makers of most (or all) MIDI API's chose a different way, by
disallowing certain messages or ways to use MIDI. I hoped the webmidi API could
be a place to make things better. But since it will usually depend on an
underlying OS API, sending running status would complicate matters with very
little benefit. 

So I won't oppose disallowing sending running status anymore, but it's sad ;)

And I hate to bring this up, but have you thought about those undefined MIDI
messages with status bytes F4, F5, F9, FD? Some OS's do not handle them,
because it is not defined how many data bytes those messages have.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 17 November 2012 13:51:56 UTC

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