- From: Raymond Toy <rtoy@google.com>
- Date: Thu, 28 Jan 2021 10:29:50 -0800
- To: "public-audio@w3.org Group" <public-audio@w3.org>, public-audio-comgp@w3.org
- Message-ID: <CAE3TgXFu3dS4dFfnFitGeWOw-qsmDn8m=K2ULkzmkQhfkNocGA@mail.gmail.com>
Attendees: Ruth John, Jack Schaedler, Attila Haraszti, Jeff Switzer,
Hongchan Choi, Raymond Toy, Athansio Malamos, Christoph Guttandin, Don
Bruztman NPS
Minutes
- CR and Rec status
- Testimonials
- Chris Lilley not here.
- V1
- New issues
- setTarget changes depending on previous events
<https://github.com/WebAudio/web-audio-api/issues/2294>
- Raymond: I think there's some confusion on the times for
ramps and setTarget. Waiting for more details.
- 9 Outstanding issues
- Interrupted state for AudioContext
<https://github.com/WebAudio/web-audio-api-v2/issues/115>
- Raymond: What is the priority?
- [Oops this was moved from v1 to v2.]
- Hongchan: Leave as is? Need more info. One use case: Unused
contexts can be interrupted to save CPU/power..
- 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>
- Raymond: Needs help from Paul
- Issues
- NoiseGenerator
<https://github.com/WebAudio/web-audio-api-v2/issues/8>
- Raymond: decided not to do bigint.
- Raymond: Needs API to be finalized with names and behaviors.
Please comment if you have suggestions
- Expose AudioBuffer to DedicatedWorker
<https://github.com/WebAudio/web-audio-api-v2/issues/111>
- Christoph: What is the best way to get a buffer to a worker?
getChannelData or copyFromChannel?
- Raymond: Don't know but copyFrom needs more memory
- Hongchan: Look at "acquiring the contents"
<https://webaudio.github.io/web-audio-api/#acquire-the-content>
- Attila: What case? getChannelData or copy.
- Hongchan: How do we transfer the buffer that's already
started?
- Raymond: Like how getChannelData works where you get a copy?
- Raymond: Issue is from worker to webaudio
- Christoph: Really want both ways
- Jeff: Yeah, really want to move buffers around.
- Raymond: Don't fully understand webcodec case and whether the
buffer can be reused.
- Hongchan: An AudioFrame is created all the time for decoding
and a new AudioBuffer is created all the time.
- Attila: Could use SharedArrayBuffer for transfering data.
- Attila: Another use case is games where lots of audio is
created in the worker. that is sent to webaudio for playback
- Raymond: Then webaudio can just keep them around as long as
needed.
- Hongchan: We should consider adding context to worker
- Raymond: I'd prefer that to just adding AudioBuffer
- Jeff: Any issues with doing that?
- Hongchan: Yes, media stream stuff won't be available. In
particular, mic input.
- Raymond: What's the approach we want to take here? Do
AudioBuffer now and then context? Or just do the context?
I'd prefer the
context that people have been requesting for a long time.
- Hongchan: Not sure
- Jeff: Having context makes AudioBuffer work not necessary
- [Hongchan to talk to codec people about having a full context]
- priority-1 issues
<https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1>
- Render capacity
<https://github.com/WebAudio/web-audio-api-v2/issues/40>
- Hongchan: There's a new API for cpu usage coming mostly for
DOM, but need to keep an eye on that.
- Raymond: What about messages as discussed before?
- Hongchan: What about hysteresis? And user-selectable bounds?
- Raymond: Of course, we need that. Has to be user-selectable
because it very much depends on the application.
- Hongchan: I'm thinking about DAWs that have a cpu meter
- Raymond: Yes, if you have a cpu meter, you really need to
poll constantly. But those who don't have a meter might
not want to poll
and would rather get a message when something bad is happening.
- Jack: Ok to do polling at first
- Hongchan: Suggestions Jack/Chris?
- Jack: Two user cases here: some want constant monitoring,
but some might want messages. [Raymond didn't capture all
of what was
said].
- [Hongchan to write up proposal]
- Chris: Could I try this in a worklet?
- Raymond: Kind of, but it won't have the info you want because
you can only know when the worklet gets called too late.
Say with 1%
usage, the worklet is still called every 3 ms.
- Chris: Oh, right.
- [Time's up]
- AOB
Thanks for attending, and see you all next week!
On Wed, Jan 27, 2021 at 2:24 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:
>
> - CR and Rec status
> - Testimonials
> - New issues
> - setTarget changes depending on previous events
> <https://github.com/WebAudio/web-audio-api/issues/2294>
> - 9 Outstanding issues
> - Interrupted state for AudioContext
> <https://github.com/WebAudio/web-audio-api/issues/72>
> - 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>
> - Issues
> - NoiseGenerator
> <https://github.com/WebAudio/web-audio-api-v2/issues/8>
> - Expose AudioBuffer to DedicatedWorker
> <https://github.com/WebAudio/web-audio-api-v2/issues/111>
> - priority-1 issues
> <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1>
> - 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
>
>
>
Received on Thursday, 28 January 2021 18:30:16 UTC