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

[Bug 18510] decodeAudioData should accept a mime-type

From: <bugzilla@jessica.w3.org>
Date: Thu, 09 Aug 2012 19:18:06 +0000
Message-Id: <E1SzYFC-0004cP-9R@jessica.w3.org>
To: public-audio@w3.org

--- Comment #1 from Chris Rogers <crogers@google.com> 2012-08-09 19:18:06 UTC ---
(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.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 9 August 2012 19:18:07 UTC

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