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: Tue, 28 Aug 2012 14:37:22 +0000
Message-Id: <E1T6Muw-0000rq-2c@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18510

--- Comment #10 from Ehsan Akhgari [:ehsan] <ehsan@mozilla.com> 2012-08-28 14:37:20 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > I would also prefer decodeAudioData to accept a non-optional mimeType argument,
> > and I think we raise an error if the mimeType argument is not supported by the
> > engine.  The reason that I would advocate for this change is that the audio
> > codecs supported by each engine (potentially on each platform) is different,
> > and that makes sniffing even worse than it already is.
> 
> Can you clarify how varying codec support between browsers and platforms make
> sniffing any harder? AFAIK, none of the formats supported by any browser are
> hard to sniff or possible to mistake for another supported format.

They won't make sniffing harder -- it just makes people rely on sniffing
potentially multiple audio streams, which means that the browser engine needs
to download the first few kilobytes of all of them until it finds one which it
can decode.

The idea that I'm going after is very similar to the HTML5 source element.  The
source element allows the browser engine to select the encoding that it
supports *without* needing to download all of the available resources and sniff
them.  If decodeAudioData takes a mimetype argument, then the browser engine
can also avoid having to download the resource just to find out that it cannot
decode it.

-- 
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 Tuesday, 28 August 2012 14:37:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 28 August 2012 14:37:26 GMT