- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 1 Aug 2019 10:16:56 -0700
- To: public-audio-comgp@w3.org
- Message-ID: <CAE3TgXHTUk92RSPJx7_FHn1fJtyjTpRu_1f9o3AxDPioRD3f9A@mail.gmail.com>
Minutes: Attendees: Paul, Varun, Chris Guttandin, Ruth John, Hongchan, Raymond - ADC - Prototype for ADC still in progress - Ray mentioned an experiment in chrome to allow setting the render quantum size in WebAudio, which mostly works. - Paul then asked with this and a worklet, is an ADC still needed? - General consensus was yes, because it's a nice layering and provides better integration of input, which isn't available today. - Hongchan asked if a push model could be supported (raised by external partner). - Consensus was yes, but since all OSes use pull models, ADC should be a pull model. - WebAudio V2 - Quick summary of new features to be implemented (noise gen, pulse-width oscillator, phase-offset for oscillator, noise gate/expander/compressor). Comments on these should be on the existing WebAudio issues for them. - Proposed that CG input for WebAudio features should be on the WebAudio issue tracker and not the CG tracker. - Chris asked about AudioContext.resume with autoplay. I think this is answered in https://github.com/WebAudio/web-audio-api/issues/1759 - Next meeting Sep 5 Fun fact: Paul mentioned that he's optimized the latency of Firefox on Mac OS and curiously the latency for the builtin speakers is higher than for wired headphones. We speculated that there must be some processing happening for the speakers, possibly to compensate for the speaker quality in a laptop. On Thu, Aug 1, 2019 at 7:45 AM Raymond Toy <rtoy@google.com> wrote: > It's time for our monthly CG meeting. Usual time and place. > > Agenda: > > - ADC > - WebAudio V2 > - Any other business > >
Received on Thursday, 1 August 2019 17:17:31 UTC