17346 2012-06-05 11:38:36 +0000 (HTMLMediaElementIntegration): HTMLMediaElement integration 2014-10-28 17:18:01 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED FIXED P2 normal TBD 1 philipj dave.null crogers public-audio dave.null oldest_to_newest 68657 0 philipj 2012-06-05 11:38:36 +0000 Audio-ISSUE-55 (HTMLMediaElementIntegration): HTMLMediaElement integration [Web Audio API] http://www.w3.org/2011/audio/track/issues/55 Raised by: Philip Jägenstedt On product: Web Audio API https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#MediaElementAudioSourceNode https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#AudioElementIntegration The section "Integration with the audio and video elements" should be merged into the definition of MediaElementAudioSourceNode. Unfortunately, the combination of the two still leaves the behavior completely undefined, with only an example given and no normative requirements for implementations. What happens when a HTMLMediaElement * has readyState HAVE_NOTHING? * is paused? * is seeking? * has no audio channels? * switches the active audio channel using the AudioTrack.enabled interface. * is muted? * has volume < 1? 75750 1 crogers 2012-10-09 23:09:33 +0000 Fixed: https://dvcs.w3.org/hg/audio/rev/9224fb26e77d 76096 2 philipj 2012-10-12 12:41:04 +0000 Looks like "must behave in an identical fashion after the MediaElementAudioSourceNode has been created" answers all of the questions. I note that it implies that when two audio tracks are enabled at the same time, they will be mixed before entering the Web Audio API and there's no way to process them separately. 114126 3 olivier.thereaux 2014-10-28 17:18:01 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.