- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 18 Feb 2021 10:25:45 -0800
- To: "public-audio@w3.org Group" <public-audio@w3.org>, public-audio-comgp@w3.org
- Message-ID: <CAE3TgXESfHM4_63MdApe3aw6nGBJK=mjhHRKyxDGmFwRBM7Kgw@mail.gmail.com>
Attendees: Ruth John, Jeff Switzer, Hongchan Choi, Raymond Toy, Athanasios Malamos Minutes: - V1 - CR and Rec Status - Testimonials - Raymond: How many do we need - Chris: Need about 6 testimonials min. IF there are too few, it's probably best not to include any. - Raymond: BBC will have one. Hopefully browsers will have one. I'll try to contact Michel Buffa and X3D for testimonials since they're W3C members. - Chris: Probably won't meet original deadline of Apr. - Chris: Proposed press release: https://docs.google.com/document/d/1gdLssN9h82wKjVcd-QtjEQo_NhV91cFcZrwJ3xam7tU/edit?userstoinvite=koalie@gmail.com&ts=602e76e6&actionButton=1 - Chris: More concerned about issues where there's no action. - Ruth: The blocker is issues, not testimonials. - Ruth: What would the next deadline be? - Chris: Sometime after next AC meeting. - Chris: Have asked about testimonials from invited experts, but no info yet. - Ruth: Priority should be to get to V1. - 9 Outstanding issues - ABSN.start control messages <https://github.com/WebAudio/web-audio-api/issues/2248> - Invoking JS in the rendering loop needs a bunch of setup that doesn't seem to be in the spec <https://github.com/WebAudio/web-audio-api/issues/1967> and Integration between event-loop of AudioWorkletGlobalScope and rendering loop <https://github.com/WebAudio/web-audio-api/issues/2008> - [Raymond: Paul has a PR up and Hongchan has started reviewing it] - Implementation and test reports need updating <https://github.com/WebAudio/web-audio-api/issues/2300> - Chris: Updated impl report as wpt tests are updated. Test report hasn't been updated. - Raymond: I'll update chrome soon, but firefox and safari have to update it themselves. - PRs - Fix #2248: Clean up ABSN start algorithm <https://github.com/WebAudio/web-audio-api/pull/2286> - Admin: Fix #2291: Add script to create a zip for for CR <https://github.com/WebAudio/web-audio-api/pull/2290> - V2 - Admin - Get Travis CI working to deploy the v2 spec. <https://github.com/WebAudio/web-audio-api-v2/issues/114> - [Raymond: Paul not on call so no progress] - New Issues - AudioWorklet should have a 'oversample' and 'bufferSize' property. <https://github.com/WebAudio/web-audio-api-v2/issues/117> - [Raymond summarizes issue] - Hongchan: oversampling seems difficult - Raymond: Really increases processing in worklet - Chris: worklet should do it itself to manage tradeoffs. - Hongchan: Many vst plugins do their own oversampling. - Chris: We should close the issue, but explain why. - Raymond: I'll do that. - priority-1 issues <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1> - Expose AudioBuffer to DedicatedWorker <https://github.com/WebAudio/web-audio-api-v2/issues/111> - Raymond: Any news? - Hongchan: Want feature fast, and PR is already there. Generally agreed it's not really harmful. But waiting to discuss with Paul one last time [who isn't on the call]. - Render capacity <https://github.com/WebAudio/web-audio-api-v2/issues/40> - Hongchan: still need to discuss with the privacy team and still need to work on it. - Render quantum size <https://github.com/WebAudio/web-audio-api-v2/issues/13> - Raymond: Said he'd clean up the proposal but hasn't done that. - [Raymond summarizes] - Hongchan: What happens when latencyHint and render size are both specified? - Raymond: render size is fairly simple. Interaction with latencyHint is hard. We'll have to specify this somehow. Not sure right now what to do. - Hongchan: Could latencyHint be replaced by render size? - Raymond: Maybe, but units are different. - Hongchan: Concerned that some blog post will say to set rendersize to 32 and latencyHint to 0 to get best latency - Raymond: That's probably the best way, actually. - Hongchan: What about fingerprinting? - Raymond: If the user specifies a (weird) value, then you probably won't learn anything that you didn't already know from the UA string. But requesting "hardware" will provide a lot more information that you wouldn't get from the UA string. We'll need to think about that. But this would be closely coupled to what baseLatency fingerprinting provides anyway.. - Select audio device <https://github.com/WebAudio/web-audio-api-v2/issues/10>, get device change notification, audio config - [No discussion] - Headphone detection <https://github.com/WebAudio/web-audio-api-v2/issues/89> - Hongchan: depends on device and OS. Windows can detect headphones or speakers. Chrome OS and Android can provide this info in some way. Needs more investigation. - Raymond: What about USB devices where I could plug in headphones or speakers? - Hongchan: Might not be detectable - Raymond: I guess that's ok; we don't have to work 100% everywhere. - [Raymond: Other comments that I didn't catch.] - Others? - priority-2 issues <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+sort%3Aupdated-desc+label%3Apriority-2> - AOB - F2F in late Apr? - Raymond: It's been about 6 mo since the last TPAC. I'll set up a poll soon on potential dates - Ruth: Any info on TPAC? - Chris: Will be virtual again. No dates yet. On Wed, Feb 17, 2021 at 4:27 PM Raymond Toy <rtoy@google.com> wrote: > Here's the agenda for our WG/CG meeting. > > Meeting venue https://meet.google.com/wgg-wjtd-kdu > > Agenda: > > - V1 > - CR and Rec Status > - Testimonials > - 9 Outstanding issues > - ABSN.start control messages > <https://github.com/WebAudio/web-audio-api/issues/2248> > - Invoking JS in the rendering loop needs a bunch of setup that > doesn't seem to be in the spec > <https://github.com/WebAudio/web-audio-api/issues/1967> and Integration > between event-loop of AudioWorkletGlobalScope and rendering loop > <https://github.com/WebAudio/web-audio-api/issues/2008> > - PRs > - Fix #2248: Clean up ABSN start algorithm > <https://github.com/WebAudio/web-audio-api/pull/2286> > - Admin: Fix #2291: Add script to create a zip for for CR > <https://github.com/WebAudio/web-audio-api/pull/2290> > - V2 > - Admin > - Get Travis CI working to deploy the v2 spec. > <https://github.com/WebAudio/web-audio-api-v2/issues/114> > - New Issues > - AudioWorklet should have a 'oversample' and 'bufferSize' > property. > <https://github.com/WebAudio/web-audio-api-v2/issues/117> > - priority-1 issues > <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1> > - Expose AudioBuffer to DedicatedWorker > <https://github.com/WebAudio/web-audio-api-v2/issues/111> > - Render capacity > <https://github.com/WebAudio/web-audio-api-v2/issues/40> > - Render quantum size > <https://github.com/WebAudio/web-audio-api-v2/issues/13> > - Select audio device > <https://github.com/WebAudio/web-audio-api-v2/issues/10>, get > device change notification, audio config > - Others? > - priority-2 issues > <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+sort%3Aupdated-desc+label%3Apriority-2> > - AOB > - F2F in late Apr? > >
Received on Thursday, 18 February 2021 18:26:12 UTC