- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 1 Oct 2020 10:57:21 -0700
- To: "public-audio@w3.org Group" <public-audio@w3.org>, public-audio-comgp@w3.org
- Message-ID: <CAE3TgXFgDYaE4CUh02cvDo0fDhg6oyT+PkU59jmWMDO3Q1WPdw@mail.gmail.com>
Attendees: Jeff Switzer, Chris Lilley, Paul Adenot, Raymond Toy, Christoph
Guttandin, Attila Haraszti
Minutes:
- TPAC 2020
- V1
- Next steps
- Raymond has spreadsheet on failing tests. Will send to Firefox
to fill out
- Chris Lilley asks if wpt.fyi has the latest Safari. Not really
clear.
- Chris: Need to update the implementation report with latest
safari news. (Raymond to update).
- Chris to follow up with security and privacy reviews
- Change log needs to be updated. (After we fix the outstanding
issues.)
- New issues
- Issue 2251: Allow to start vs [[suspended by user]]
<https://github.com/WebAudio/web-audio-api/issues/2251>
- Chris and Raymond agree it should be in V1. Just add note
that allowed-to-start needs to honor suspended by user.
- Issue 2252: Resolving [[pending resume promises]]
<https://github.com/WebAudio/web-audio-api/issues/2252>
- Raymond: Specced behavior is odd. resume() causes pending
resumes to be rejected not resolved.
- Raymond: should fix this in v1.
- Chris: Agreed.
- Jeff: Can i write a test for this?
- Chris: Yes, it should be possible
- Paul: Might have a test in Firefox already.
- Outstanding issues
- FrozenArrays
<https://github.com/WebAudio/web-audio-api/issues/1933>
- Raymond: PR for this up, but need help from Hongchan to
describe how corner cases are handled. Also can't figure
out a WebIDL way
to say the callback must be named "process".
- Paul: Using callback will automatically get things set up
correctly.
- PRs
- Paul to review dup IDs for decode callbacks
<https://github.com/WebAudio/web-audio-api/pull/2253>.
- V2
- #13: User selectable render size
<https://github.com/WebAudio/web-audio-api-v2/issues/13>
- Still needs IDL proposal
- Paul: Will get new devices for testing. 50% improvement on
most of the Android devices (buffer size is 160).
- #10: Access to different output devices
<https://github.com/WebAudio/web-audio-api-v2/issues/10>
- Raymond: Need to support selection somehow.
- #11: 16-bit AudioBuffers
<https://github.com/WebAudio/web-audio-api-v2/issues/11>
- Raymond: Should do it but not sure how.
- Paul: Firefox already does this internally and works well.
- Paul: Could do compression (with very fast decompressors).
There are non-patented techniques for this.
- More design needed.
- AOB
- None
On Wed, Sep 30, 2020 at 2:59 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:
>
> - TPAC 2020 Oct 12-16, 26-30, virtual
> - Time is 9am-11am San Francisco time
> - Tentative agenda to be sent out before next meeting.
> - V1
> - Next steps for recommendation status, from Chris Lilley:
> 1. Resolve the 7 issues ready for editing.
> 2. Explain why tests don't pass
> 3. Complete horizontal review (accessibility, i18n,
> security/privacy)
> - 3 closed privacy issues, 0 security issues, 0
> accessibility, 1 closed i18n.
> 4. Update changes section
> 5. Minuted WG decision for requesting proposed recommendation
> - New issues
> <https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs+WG+review%22>
> - Status of outstanding issues that we should fix for v1.
> - FrozenArrays for AudioWorkletNode
> <https://github.com/WebAudio/web-audio-api/issues/1933>
> - Any others?
> - V2
> - Proposals for selectable render size
> <https://github.com/WebAudio/web-audio-api-v2/issues/13>
> - Other priority-1 issues
> <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1>
> - AOB
>
>
Received on Thursday, 1 October 2020 17:57:47 UTC