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

Re: Exclusive access to audio hardware

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 10 May 2012 10:32:04 +1200
Message-ID: <CAOp6jLYdkSXfu5PmVoyjLMcZNN4+trR=3E6izk8y+4RuvYCtRA@mail.gmail.com>
To: Jer Noble <jer.noble@apple.com>
Cc: Chris Rogers <crogers@google.com>, "public-audio@w3.org" <public-audio@w3.org>
I think it would be simpler for authors if everything "just worked" as far
as possible. With the proposed renderState and onrenderstatechange, some
developers are likely to simply forget to handle it --- if the renderState
is never idle on their platform or they simply don't test that case --- and
their apps will be broken.

So how about adding no new APIs, but instead just automatically pause the
entire audio graph while the page does not have access to the audio
hardware?

Rob
-- 
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]
Received on Wednesday, 9 May 2012 22:32:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 22:32:36 GMT