17320 2012-06-05 11:08:32 +0000 Exclusive access to audio hardware 2014-10-28 17:17:53 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED WONTFIX P2 normal TBD 1 jer.noble dave.null crogers public-audio dave.null oldest_to_newest 68629 0 jer.noble 2012-06-05 11:08:32 +0000 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 75413 1 crogers 2012-10-05 21:35:42 +0000 Jer, is this something you still believe is important to consider? I know iOS has been shipping for a little while and didn't know if this was still an issue. 75414 2 jer.noble 2012-10-05 21:36:44 +0000 Yes I believe it is still an issue. It's unfortunate that we weren't able to resolve this prior to iOS 6, but I believe this is still important to resolve for future implementations. 113965 3 olivier.thereaux 2014-10-28 17:14:55 +0000 Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues 114114 4 olivier.thereaux 2014-10-28 17:17:53 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.