[web-audio-api] Exclusive access to audio hardware (#72)

> Originally reported on W3C Bugzilla [ISSUE-17320](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17320) Tue, 05 Jun 2012 11:08:32 GMT
> Reported by Jer Noble
> Assigned to 

http://www.w3.org/2011/audio/track/issues/15

Raised by: Jer Noble
On product: Web Audio API

On the mailing list, Jer Noble proposed an addition to the WebAudio API which would allow the API to be implemented on platforms which allow exclusive access to audio hardware.

http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0122.html

The proposed changes:

* Add the AudioContext.startRendering() method to the spec.
* Add a new AudioContext.renderState property to the spec.
  + Values:
    - RENDERING
    - INTERRUPTED
    - IDLE

Chris Rogers questioned why the startRendering() method was necessary:

http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0124.html

Jer Noble replied with a use case demonstrating its use:

http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0126.html

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/72