W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2010

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

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Tue, 2 Feb 2010 09:02:40 +1100
Message-ID: <2c0e02831002011402l5bccc02fo5a6851e5bceddbee@mail.gmail.com>
On Tue, Feb 2, 2010 at 4:05 AM, Chris McCormick <chris at mccormick.cx> wrote:
> On Sun, Aug 09, 2009 at 08:29:28PM +1000, Silvia Pfeiffer wrote:
>> On Sun, Aug 9, 2009 at 7:20 PM, Chris McCormick<chris at mccormick.cx> wrote:
>> > Hi Sylvia,
>> >
>> > On Sun, Aug 09, 2009 at 11:16:01AM +1000, Silvia Pfeiffer wrote:
>> >> On Sun, Aug 9, 2009 at 3:15 AM, Chris McCormick<chris at mccormick.cx> wrote:
>> >> > On Wed, Jul 08, 2009 at 09:24:42AM -0700, Charles Pritchard wrote:
>> >> >> There are two use cases that I think are important: a codec
>> >> >> implementation (let's use Vorbis),
>> >> >> and an accessibility implementation, working with a <canvas> element.
>> >> >
>> >> > Here are a few more use-cases that many people would consider just as
>> >> > important:
>> >> >
>> >> > * Browser based music software and synthesis toys.
>> >> > * New types of 'algorithmic' music like that pioneered by Brian Eno.
>> >> > * Browser based games which want to use procedural audio instead of
>> >> > pre-rendered sound effects.
>> >>
>> >> Why don't you just implement an example in javascript to show off what
>> >> you're talking about and make a use case for having it implemented
>> >> inside the browsers?
>> >
>> > Yes, you are right I should definately do that. What is the normal process for
>> > that: write some code, post it up on my website, and then post here with a
>> > link? Is that sufficient to get the attention of the browser implementors?
>>
>> I would think so. Not automatically, of course, but it would go a long way.
>>
>>
>> > By 'implement an example in javascript' do you mean that I should implement an
>> > example of what I wish the browsers could do, or implement an actual reference
>> > vector library that the browsers could use? The former I can see myself doing,
>> > but the latter has been on my TODO list long enough for me to know that I won't
>> > get it done any time soon. :/
>>
>> The former. Do it in javascript even if it is very slow. Just needs to
>> demonstrate the idea and how useful it is for browser users.
>
> Hi Silvia,
>
> Whilst I haven't had the time to do this myself, I did hear about the perfect
> example use-case for what I was getting at. Someone required a very small flash
> applet just to do the last javascript-to-audio bit of synthesis. Everything
> else was done in Javascript.
>
> <http://stockholm.musichackday.org/index.php?page=Webloop>
>
> "Since almost no browser is able to output sound directly from javascript, I
> currently use a small flash applet to push the sound to your speakers, I hope
> you don't mind."
>
> I think I speak for all procedural audio people when I say, can't we get the
> browsers to allow sample-block access to audio?

Sounds like a solid argument to me. But I'm not the one who counts. :-)

Cheers,
Silvia.
Received on Monday, 1 February 2010 14:02:40 UTC

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