W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] (activeSourceCount): AudioContext.activeSourceCount (#139)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:34 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/139@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17329](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17329) Tue, 05 Jun 2012 11:21:09 GMT
> Reported by Philip Jägenstedt
> Assigned to 

Audio-ISSUE-31 (activeSourceCount): AudioContext.activeSourceCount [Web Audio API]

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

Raised by: Philip Jägenstedt
On product: Web Audio API

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#dfn-activeSourceCount

"currently playing" is not sufficiently defined.

Possibly, is it the number of AudioBufferSourceNodes with playbackState == PLAYING_STATE. However, which AudioBufferSourceNodes? After creating them, the spec doesn't define any association with the AudioContext, so it's not clear how to count them.

Seemingly, only AudioBufferSourceNodes are included in the count, but given the name including Oscillator and MediaElementAudioSourceNode ought to also be included, given that they also have playing states (directly or indirectly).

Finally, what is the use case for activeSourceCount? If it can be dropped, the above issues become moot.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/139
Received on Wednesday, 11 September 2013 14:31:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC