Re: AudioWorker status

I'm all for the approach of defining concepts and vocabulary up front.  One
question, how can there be more than one rendering thread, without
introducing latency at arbitrary points in the graph?

On Wed, Sep 23, 2015 at 8:53 AM, Paul Adenot <padenot@mozilla.com> wrote:

> Joe,
>
> Sorry for the delay. I've started converting my raw notes into spec text,
> and to put them publicly online for (very early !) review. I've done a
> first bit today, here:
> http://padenot.github.io/web-audio-api/#processing-model. For now, I've
> only converted how the main thread JS API call send operation to the
> rendering thread, layoing out some vocabulary and concepts.
>
> I'm freeing up from Gecko work at the moment and should be full time on
> this starting next week (or so). My goal is to have something in good shape
> before TPAC so we can discuss.
>
> I plan to leave some TODO items inline so we can discuss those earlier
> than later, if needed, look for ugly red TODO boxes.
>
> Cheers,
> Paul.
>
>
>
> On Fri, Sep 11, 2015 at 3:30 PM, Joe Berkovitz <joe@noteflight.com> wrote:
>
>> Hi Paul,
>>
>> The group is making good progress on resolving small issues. At the same,
>> we're not sure where the AudioWorker spec stands, and TPAC is approaching
>> quickly.
>>
>> Are you able to give the group an update on the progress of AudioWorker?
>>
>> Thanks so much.
>>
>> Best,
>> .            .       .    .  . ...Joe
>>
>> *Joe Berkovitz*
>> President
>>
>> *Noteflight LLC*
>> 49R Day Street / Somerville, MA 02144 / USA
>> phone: +1 978 314 6271
>> www.noteflight.com
>> "Your music, everywhere"
>>
>
>