Re: [web-audio-api] decodeAudioData should accept a mime-type (#7)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=18510#0) by Chris Rogers on W3C Bugzilla. Thu, 09 Aug 2012 19:18:06 GMT

(In reply to comment #0)
> The decodeAudioData method on AudioContext is stated to support any of the
> formats supported by the <audio> element, but unlike the <audio> element it
> doesn't allow the author to state the format of the audio data (since the
> ArrayBuffer is already a step removed from the XMLHttpRequest likely used to
> fetch the data).
> 
> We should fix this by adding an (ideally required) contentType argument to
> decodeAudioData to communicate the format of the audio in the provided
> ArrayBuffer.

Hi Tony, I'm just trying to get a better idea of why the contentType would be needed.  Are there some particular audio formats which can't be correctly inferred through "sniffing" the audio data, which is what we're doing today.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/7#issuecomment-24244075