W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] Codecs for <audio> and <video>

From: Charles Pritchard <chuck@jumis.com>
Date: Tue, 07 Jul 2009 08:52:29 -0700
Message-ID: <4A536F3D.7060605@jumis.com>
Philip Jagenstedt wrote:
> For all of the simpler use cases you can already generate sounds 
> yourself with a data uri. For example, with is 2 samples of silence: 
Yes you can use this method, and with the current audio tag and 
autobuffer, it may work to some degree.

We've used the data:audio/midi technique, and we've experimented with 
using the data: injection work-around, does not currently work all that 

It does not produce smooth transitions. We can use raw encoding instead 
of base64 to save on
cpu cycles, but it's still quite "hackish".
> It might be worthwhile implementing the API you want as a JavaScript 
> library and see if you can actually do useful things with it. If the 
> use cases are compelling and require native browser support to be 
> performant enough, perhaps it could go into a future version of HTML.
Overall, we can not make near-real-time effects, nor jitter-free 

We've used wav and midi in a JavaScript library, using the data: url 
The data: injection technique is inefficient, it's not workable.

Opera has been championing Xiph codecs on this list, There are 
ActionScript and Java Vorbis-players developed using the most basic of APIs.
Isn't that use-case compelling enough?

Received on Tuesday, 7 July 2009 08:52:29 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:14 UTC