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

Re: Questions about AudioParam

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 11 Dec 2012 13:51:04 +1300
Message-ID: <CAOp6jLa7FetPk8oHNsFA4+fTiAZh1Jb-L18N4N9L33kB-No_WQ@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: Ehsan Akhgari <ehsan.akhgari@gmail.com>, public-audio@w3.org
On Tue, Dec 11, 2012 at 11:55 AM, Chris Rogers <crogers@google.com> wrote:

> I have never seen any desktop audio applications go to great lengths, for
> example, to ensure that the level meters of different channels of a mixing
> board were all sampled from the same "audio render quantum".  It's just not
> considered that much of an issue.

OK, but we aren't building a desktop audio app, we're building an API that
thousands or millions of relatively unsophisticated developers will use in
ways we can't anticipate. We're also doing it in a context where unexpected
delay on the UI thread is an omnipresent threat. As such, given we can
provide a consistent snapshot relatively easily, it seems prudent to do so.
(For example, one way to implement the snapshot would be to just snapshot
the currentTime for an AudioContext and then have every
AudioParam.computedValue refer to that currentTime and compute its value
based on that.)

Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]
Received on Tuesday, 11 December 2012 00:51:37 UTC

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