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

Re: [web-audio-api] Access to individual AudioTracks (#132)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:49 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/132/24244403@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17345#2) by Philip J├Ągenstedt on W3C Bugzilla. Wed, 24 Oct 2012 09:42:37 GMT

That change was in response to Bug 17346 and looks fine to me.

As for createMediaElementSource() vs a property on AudioTrack, I'm fine with keeping a create method for consistency and API separation.

What remains unresolved is the issue of multi-track resources. If instead of a createMediaElementSource we had a createAudioTrackSource, the issue of what to do with media elements without any audio goes away, and it's also possible to process the audio streams separately. Should I file a new bug for this?

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:30:31 UTC

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