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

> [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:
https://github.com/WebAudio/web-audio-api/issues/132#issuecomment-24244403