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

[Bug 20510] send(sequence<short> data) should just be send(any data)

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Dec 2012 18:44:30 +0000
To: public-audio@w3.org
Message-ID: <bug-20510-5429-MDcbLxX1tO@http.www.w3.org/Bugs/Public/>

--- Comment #11 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #10)
> "If data is not a valid sequence, does not contain a valid MIDI message, or
> if timestamp is passed but is not a valid DOMHighResTimeStamp, throw a
> TYPE_ERROR exception."
> 1. "valid MIDI message" is not defined, AFACT. 

Actually, it's defined by [[!MIDI]].  (Explicitly, as in there's a list of MIDI
messages, + definition of sysex.)

> 2. and this is not needed, as it's handled by WebIDL: "if timestamp is
> passed but is not a valid DOMHighResTimeStamp, throw a TYPE_ERROR
> exception." 
> (I think I already filed 2. above)

You did.  Already fixed.

> Also:
> "The data MUST contain one or more valid, complete MIDI messages. Running
> status is not allowed in the data, as underlying systems may not support it."
> 1. Data is not a "conformance class", hence an RFC2119 keyword cannot be
> used there. Please change it to:
> "The data contains one or more MIDI messages." 
> The above is a statement of fact (which may or may not be true, but that is
> irrelevant until processed).


> 2. It's unclear what "Running status is not allowed in the data" means.
> There is no algorithm defined in the specification to check for this (and do
> something if "running status" is found).

Defined by [[!MIDI]] as well.  Online definitions of running status tend to be
shaky; it is, in my opinion, a bit of a hack.  Or, more precisely - the format
of MIDI messages is pretty well documented online (by
http://www.midi.org/techspecs/midimessages.php, for example), but running
status is not.  In short - if you process according to that link and fail if
something looks like it's not a MIDI message, you are detecting and failing on
running status.  Running status is additional compression layered on top.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 26 December 2012 18:44:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:15 UTC