Re: Making Web Audio APIs More Competitive with native

Hi Kumar,

There's a big difference between OpenGL and OpenSL.  OpenGL is a mature API
which has existed for a long time, has many implementations supporting it,
and lots of code written for it.  OpenSL is a much newer proposal which
doesn't have these features.  Other than the name being similar to OpenGL, I
don't think there's anything particularly "symmetric" about it.

Chris

On Thu, Dec 9, 2010 at 10:00 PM, Kumar <srikumarks@gmail.com> wrote:

> Hi all,
>
> I joined the public forum relatively recently and
> I've been reading this thread with great interest.
> The work on the audio API thus far is impressive.
>
> That said, I couldn't help wonder whether some of
> the initiatives in other standards groups can be
> merged into this effort - particularly that of
> OpenSL ES (http://www.khronos.org/opensles/)
> That would make the audio path symmetric compared
> to what the visual group is doing with WebGL, which
> is taking OpenGL ES and making it available via
> a JavaScript API built atop Canvas 3D.
>
> Any thoughts on this? On first glance, there doesn't
> seem to be anything particularly limiting about
> OpenSL ES (to me at least) that would make it
> inappropriate for web use. I hope to get a better
> idea of it in the coming days.
>
> Anyone here who straddles both groups?
>
> Regards,
> -Srikumar
>
> On Fri, Dec 10, 2010 at 3:28 AM, Noah Mendelsohn <nrm@arcanedomain.com>
> wrote:
> >
> >
> > On 12/9/2010 2:12 PM, Chris Rogers wrote:
> >>
> >> I don't expect that a JavaScript developer is going to play with my API
> >> for
> >> a couple of weeks and come back with Digital Audio Workstation software
> to
> >> rival something like Apple's Logic Audio
> >
> > Indeed, but if we set off down the path that would lead to such things
> in,
> > say 5 years, with interesting DAWs of lesser capability emerging along
> the
> > way, that would be really wonderful.  I'm actually curious what will
> prove
> > to be implementable in Javascript over time from a performance point of
> > view.  E.g. it's very cool that Javascript is doing FFts with plausible
> > performance today, but it will be interesting to see when it can do 20 in
> > parallel on a many core chip.  Still, this all looks very, very
> promising.
> >  Thanks!
> >
> > Noah
> >
> >
> >
>