- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 8 Jul 2021 09:56:38 -0700
- To: "public-audio@w3.org Group" <public-audio@w3.org>, public-audio-comgp@w3.org
- Message-ID: <CAE3TgXHY-oW3w2v7wmmbxo1WO9GtX4Lg-2a2a2KjNdaZvO0mxg@mail.gmail.com>
Attendees: Jeff Switzer, Paul Adenot, Christoph Guttandin, Raymond Toy Minutes: - Admin - Review of process to update the spec <https://github.com/WebAudio/web-audio-api/issues/2362> - [Raymond explains the key points of the process] - V1 - PRs - Fix #2339: Fix ecma262 completion <https://github.com/WebAudio/web-audio-api/pull/2350> - Raymond: Just needs a quick review; no need to add amendment boxes since this is already in the recommendation - Use new Web IDL buffer primitives <https://github.com/WebAudio/web-audio-api/pull/2363> - [Raymond describes how the amendment boxes work] - Paul: This looks pretty good; a list of changes for the change log is good, but too bad it doesn't show up in the preview. - Raymond: Yeah, a bikeshed problem where bikeshed processes the script tag as regular text. Could possibly be worked around. - Fix typo in VUMeterNode <https://github.com/WebAudio/web-audio-api/pull/2356> - Raymond: Simple typo fix, but needs to land after the WebIDL one, since that has all the infrastructure in place. - RangeError for only for negative cancelTime <https://github.com/WebAudio/web-audio-api/pull/2352> - Raymond: Must land after WebIDL to get the infrastructure changes. - V2 - 16 Priority-1 issues <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1> - user-selectable size - Raymond: As discussed last week, we can proceed with writing a PR for this. One issue is the size of the SciriptProcessor buffers. Still power of two? The proposal says power of two times the render size. - Paul: Still has to buffer, so power of two and not doesn't make much difference. - Paul: Maybe need to add that convolvers may add additional latency? - Raymond: Chrome uses PFFFT so powers of 2,3,5 are supported so no additional latency needed. And browsers are allowed to round up to the next supported size. - Paul: That's complicated on windows with 441 or 480. - Raymond: Neither of these are supported by PFFFT since 441 is powers of 3 and 7. 440 (which chrome uses) is a power of 2, 3, and 11. 480 is power of 2,3,5, so supported. Could extend PFFFT to support 7 and 11, but it will be slower. But browser could round up 440/441 to 480. Might be ok? - Paul: Yeah, it's pretty complicated. - output selection - Paul: Well under way in Firefox - Raymond: Just adding a sinkID to the constructor dictionary? - Paul: Yes. - AOB On Thu, Jul 8, 2021 at 8:33 AM 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: > > - Admin > - Review of process to update the spec > <https://github.com/WebAudio/web-audio-api/issues/2362> > - V1 > - PRs > - Fix typo in VUMeterNode > <https://github.com/WebAudio/web-audio-api/pull/2356> > - Fix #2339: Fix ecma262 completion > <https://github.com/WebAudio/web-audio-api/pull/2350> > - Use new Web IDL buffer primitives > <https://github.com/WebAudio/web-audio-api/pull/2363> > - RangeError for only for negative cancelTime > <https://github.com/WebAudio/web-audio-api/pull/2352> > - V2 > - 16 Priority-1 issues > <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1> > - AOB > > >
Received on Thursday, 8 July 2021 16:57:38 UTC