W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Exclusive access to audio hardware

From: Chris Rogers <crogers@google.com>
Date: Wed, 9 May 2012 13:45:52 -0700
Message-ID: <CA+EzO0mX=1-K7k-D8kjOXDtqjYiRsez39pmEDtkGkVfsJx+gCQ@mail.gmail.com>
To: Jer Noble <jer.noble@apple.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
On Tue, May 8, 2012 at 2:21 PM, Jer Noble <jer.noble@apple.com> wrote:

>
> On May 8, 2012, at 11:31 AM, Chris Rogers <crogers@google.com> wrote:
>
> Hi Jer, I'm not opposed to something like the proposed
> . renderState attribute and the event for state changes.  I'm still trying
> to understand if we need startRendering() or not.  I understand that in
> some cases when a context is first created it may not be able to start
> playing, at least right away, because the device might be in the middle of
> a phone call, for example.  I'm just wondering if there are any
> alternatives to a startRendering() method?  Can't the developer query the
> .renderState attribute early on to know if rendering will be able to start
> just after the AudioContext has been created.  Maybe the startRendering()
> method is the best choice.  I'm just trying to get a better understanding
> of why it's needed.
>
>
> The purpose would be to give the developer more control about when to
> restart audio processing.  Take for example a web-based game: during an
> interruption, the script may want to pause the game (if the audio is
> important to the game).  It seems to be a common convention that, in this
> situation, the game will wait for user interaction before restarting.
>  Rather than explicitly tearing down the node graph during the interruption
> and rebuilding it after resuming, it would be much easier to leave the
> graph in place and resume by calling startRendering().
>
> -Jer
>

I see.  This seems reasonable.  We might want to consider shortening the
name "startRendering()" to simply "start()", but that's just a naming
detail.  One other thing we'd need to consider is what happens if the
AudioContext is in the INTERRUPTED state, but we try to create and connect
additional nodes to the graph.  Should those calls throw exceptions, or
should they be allowed and those nodes are simply handled seamlessly when
startRendering() is later called?  Probably it would be best if it *just
works* with no exceptions.

Chris
Received on Wednesday, 9 May 2012 20:46:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 20:46:24 GMT