W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2016

Re: Worklets spec status ?

From: Joe Berkovitz <joe@noteflight.com>
Date: Tue, 9 Feb 2016 11:33:46 -0500
Message-ID: <CA+ojG-ZQgrVnguwNB+GzqcipZd2O5PHsqFLe0dvpUmVquVKXAQ@mail.gmail.com>
To: Alex Russell <slightlyoff@google.com>
Cc: Ian Kilpatrick <ikilpatrick@google.com>, Paul Adenot <padenot@mozilla.com>, "public-audio@w3.org Group" <public-audio@w3.org>, Shane Stephens <shanestephens@google.com>
Hi Ian,

Thanks so much for letting the WG know about the updates to Houdini and for
the continued work in this area.

The Houdini work is the gating item for closing one of the key feature gaps
in the Audio API, named AudioWorker -- perhaps Paul has already explained
this to you, so please forgive any repetition. The WG is following the
Worklets progress with great interest, but I think our group doesn't have a
clear picture of the nature of these new WHATWG module dependencies just
mentioned, nor of their timeline. Personally I'm not yet educated enough
about Worklets and module scripts to offer a reasonable response on the
merits. The main thing that I've just learned is that the brand new thing
our spec depends on may now depend on something else that is also brand new.

At the suggestion of Chris Lilley (our W3C contact), I'd like to invite you
to an Audio WG call so that we can have a direct discussion with you. The
goal would be to understand jointly the best way to bring the combination
of Houdini and Web Audio to a place that delivers the features we need. Web
Audio has several implementations in the field receiving heavy use, and the
AudioWorker feature is the single biggest gap impeding its wider adoption.

Are you up for such a talk with the WG, and could we tentatively try to
schedule this for 2 weeks (or some multiple thereof) from Thursday at 12
noon Boston? (25 February, 12 noon EST)  I think it would be a great help
to have you and appreciate your consideration.


.            .       .    .  . ...Joe

Joe Berkovitz
Co-chair W3C Audio WG
Noteflight LLC

+1 978 314 6271

49R Day Street
Somerville MA 02144

"Bring music to life"

On Sun, Feb 7, 2016 at 7:00 AM, Alex Russell <slightlyoff@google.com> wrote:

> Dumb question: why cause these to be module scripts when they're clearly
> going to be loaded async from the perspective of the main script anyhow?
> On Sat, Feb 6, 2016 at 7:43 AM, Ian Kilpatrick <ikilpatrick@google.com>
> wrote:
>> Hey all,
>> I made a bunch of edits during Houdini.
>> See: https://drafts.css-houdini.org/worklets/
>> Major change is that this will require the modules infrastructure which
>> was just added to the html whatwg spec.
>> lmk if you need anything specifically.
>> Thanks,
>> Ian
>> On Thu, Jan 28, 2016 at 9:03 AM, Ian Kilpatrick <ikilpatrick@google.com>
>> wrote:
>>> Hey Paul,
>>> Over the next week I've got some time to spend on it, and aiming it to
>>> get to a stage where it's good for Houdini.
>>> What are the specific things that you need from it to move forward at
>>> the moment?
>>> PRs are great if you have the time.
>>> Thanks,
>>> Ian
>>> On Thu, Jan 28, 2016 at 8:51 AM, Alex Russell <slightlyoff@google.com>
>>> wrote:
>>>> +shane
>>>> On Wed, Jan 27, 2016 at 6:46 AM, Paul Adenot <padenot@mozilla.com>
>>>> wrote:
>>>>> Ian,
>>>>> The Audio-WG (CC-ed) was wondering about the status of the Worklets
>>>>> specification. There are still a few things that need to be done until we
>>>>> have enough infrastructure to write the Audio Worklet text on top of it,
>>>>> and the Web Audio API really need this to go forward.
>>>>> Do you have an estimate on when you'll be able to find some time to
>>>>> work on it? Can we help in any way ? Since this is on the critical path for
>>>>> us, it might make sense we contribute in a more direct way, by directly
>>>>> sending PRs.
>>>>> Cheers,
>>>>> Paul.
Received on Tuesday, 9 February 2016 16:34:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 9 February 2016 16:34:17 UTC