Re: [Agenda] WG/CG Telecon Thurs Oct 7, 9:00 am PDT

Attendees: Christoph Guttandin, Raymond Toy, Chris Lilley, Jeff Switzer

Minutes:

   - TPAC 2020
      - Next week.  See previous email for the schedule.
   - V1
      - Security issue
      <https://github.com/WebAudio/web-audio-api/issues/2254>
         - Raymond: How long to wait?
         - Chris: Not clear, transitions to recommendation may take a few
         weeks, so this can be done in parallel.
      - V2
      - Output device selection
      <https://github.com/WebAudio/web-audio-api-v2/issues/10>
         - Christoph: Mentioned that mediacapture-output API updated to
         support enumerating outputs.
         https://github.com/w3c/mediacapture-output/pull/109/files
      - NoiseGate/Expander
      <https://github.com/WebAudio/web-audio-api-v2/issues/12>
         - Raymond: CG would be really helpful here.
      - Power law automation
      <https://github.com/WebAudio/web-audio-api-v2/issues/22>
         - Just needs spec work
      - PlaybackPosition
      <https://github.com/WebAudio/web-audio-api-v2/issues/26>
         - Where exactly is this taken?  At the beginning of the render?
         Wherever the playback head is at when the request is made?
         - Christoph:  Could create a separate ABSN with a ramp source.
         Then automate both.  The ramp ABSN output would then have the actual
         position.
      - Change outputChannelCount
      <https://github.com/WebAudio/web-audio-api-v2/issues/37>
         - Raymond:  Chrome can't change the number of output channels and
         have it take effect immediately.  There would be a delay of
at least one
         render.
         - Raymond: This doesn't work with outputs now being FrozenArrays.
         Probably implies having to set some value.
      - audio thread overload
      <https://github.com/WebAudio/web-audio-api-v2/issues/40>
         - Raymond:  Devs can already use performance.Now() with a test
         code to determine how powerful your machine is.  This API
wouldn't make it
         worse (I think).
         - Chris:  Do we want privacy review? It's a sprawling thread.
         - Raymond:  Let's make a proposal on what this will be and have
         privacy review for the proposal.
      - Handling of output arrays for worklet
      <https://github.com/WebAudio/web-audio-api-v2/issues/42>
         - Last comment summarizes the current state of things; nothing new
         added.



On Wed, Oct 7, 2020 at 4:15 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 (16:00-18:00 UTC)
>       - Registration is open
>    - V1
>       - New issues
>       <https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs+WG+review%22>
>       - WCAG standards for accessible text
>          <https://github.com/WebAudio/web-audio-api/issues/2257>
>          - Security review
>          <https://github.com/WebAudio/web-audio-api/issues/2254>
>       - Status of outstanding issues that we should fix for v1.
>          - FrozenArrays for AudioWorkletNode
>          <https://github.com/WebAudio/web-audio-api/issues/1933>
>          - ABSN.start control messages
>          <https://github.com/WebAudio/web-audio-api/issues/2248>
>          - Any others?
>       -
>       - Open PRs to be reviewed
>          - ABSN extrapolation
>          <https://github.com/WebAudio/web-audio-api/pull/2256>
>          - Duplicated IDs for decode callbacks
>          <https://github.com/WebAudio/web-audio-api/pull/2253>
>       - V2
>       - priority-1 issues
>       <https://github.com/WebAudio/web-audio-api-v2/issues?q=is%3Aopen+is%3Aissue+label%3Apriority-1>
>       - AOB
>       - No teleconf on Oct 15 and 22
>
>