W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2012

Re: Newbie questions about web audio working group specs

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 2 Feb 2012 09:20:32 +1300
Message-ID: <CAOp6jLY6Uzy0beNWRF7nVeaqCTdmBkTH89TPM70Ry77d5JCbbg@mail.gmail.com>
To: Samuel Goldszmidt <samuel.goldszmidt@ircam.fr>
Cc: public-audio@w3.org
On Thu, Feb 2, 2012 at 4:24 AM, Samuel Goldszmidt <
samuel.goldszmidt@ircam.fr> wrote:

>  - Is there no 'AudioContext' in the MediaStream API ? (so it's the
> element.src value ?)
>

Correct. It's just not needed.

- It seems to me that the Mozilla audio specification here
> https://wiki.mozilla.org/Audio_Data_API, and inside examples, says more
> or less : create a simili Javascript AudioGraph on your own inside a
> worker, and all will be fine, no ?
>

The Audio Data API is obsolete; please ignore it for the purposes of this
discussion.


> In MediaStream Processing, when I read the spec, it seems to me that, with
> block state, glitches would be less present ?
>

In MediaStream Processing, glitches don't cause you to lose sync, but they
will still happen. Dealing with overload well is something that neither of
us have a handle on yet, AFAIK.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive us
our sins and purify us from all unrighteousness. If we claim we have not
sinned, we make him out to be a liar and his word is not in us." [1 John
1:8-10]
Received on Wednesday, 1 February 2012 20:21:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 February 2012 20:21:02 GMT