Re: Web Audio API decoder instancing

On Fri, Dec 21, 2012 at 10:51 PM, Bradley, Adam <adam.bradley@jagex.com>wrote:

> Well I looked into <audio> elements with some interest, however as far as
> I could figure out, you can’t define their source content using a buffer of
> data (an ArrayBuffer for example), and instead they require a URL to a
> source file that they then buffer themselves. This may not be enough
> control for my purposes, especially as from what I can make out about
> browser support, that in some cases I cannot use multiple <audio> elements
> concurrently, which will not be satisfactory for our needs. We also like to
> pack our audio data into custom obfuscated formats rather than to use loose
> files, which the <audio> element system doesn’t seem capable of integrating
> with.
>

The Media Source API might give you the control you need:
http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html
This isn't widely implemented yet, but I think it will be.

However, we should not add new APIs to the Web platform to work around
crippled implementations of existing APIs in certain browsers. That makes
no sense at all. If some browser implements <audio> elements in a way that
creates a problem for you, you need to petition that vendor to change their
implementation.

Rob
-- 
Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]