Re: Two general reasons why AudioParam.value setter cannot be changed to a setTargetAtTime alias

Karl,

On 20 Jan 2014, at 08:19, Karl Tomlinson <karlt+public-audio@karlt.net> wrote:

> There is no bug in the current spec.

There clearly was an issue with underspecified smoothing behaviour when using the .value setter.

> I would like to come back to the motivation for this.  The only
> reasons I've noticed given are that Blink and Webkit do it this
> way, consistency, and clarity.  I assume there are no other
> reasons for the proposed change?

The goal was to do “the right thing” in as many cases as possible, making it easy for non-experts to get acceptable results in most cases, while giving people who want no smoothing an option to do so (with SetValueAtTime).

There was an element of “paving the cowpaths”, that is, going the solution closest to the current behaviour, but this certainly wasn’t “just” a documentation of Blink/Webkit behaviour.

At this point, there is still overwhelming consensus in the group that smooth-by-default is the best compromise, after a substantial amount of time was spent discussing it.

http://www.w3.org/2013/11/21-audio-minutes.html#item03
http://www.w3.org/2013/12/19-audio-minutes.html#item02
https://github.com/WebAudio/web-audio-api/issues/76


Your objection has been noted, and I am keen to make sure the group considers it in detail before deciding whether the consensus stands.

--
Olivier





-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

Received on Monday, 20 January 2014 09:05:51 UTC