decodeAudioData Prose: avoid video containers that have an audio track #34

olivierthereaux opened this Issue Sep 11, 2013 · 4 comments


None yet

6 participants


Originally reported on W3C Bugzilla ISSUE-21520 Tue, 02 Apr 2013 14:41:45 GMT
Reported by Olivier Thereaux
Assigned to

Per discussion at Audio WG f2f 2013-03-26


"Audio file data can be in any of the formats supported by the audio element"


"...can be accepted in formats containing only audio data (w/o video)"

This is to avoid the overhead of dealing with video containers that have an audio track.


Original comment by Robert O'Callahan (Mozilla) on W3C Bugzilla. Wed, 03 Apr 2013 01:19:11 GMT

What's the downside of supporting media formats that contain video tracks? I think in our implementation there's no implementation cost to supporting all the formats our HTML media elements support.

cwilso commented Oct 30, 2014

We do, so I think this is "can be in any of the formats support by the audio or video elements, respectively".

@cwilso cwilso added this to the Web Audio Last Call 1 milestone Oct 30, 2014
@billhofmann billhofmann self-assigned this Sep 10, 2015

Modified per cwilso's comment, 971b33f

@padenot padenot reopened this Sep 23, 2015

ok, taking another swing at it...

@billhofmann billhofmann pushed a commit that referenced this issue Oct 24, 2015
@bill-hofmann bill-hofmann Fix #34, Merge branch '34-audio-element-prose2' of…
…o/web-audio-api into 34-audio-element-prose2
@rtoy rtoy closed this in 45496c0 Nov 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment