Re: [Agenda] Audio WG/CG Telecon Thurs May 5, 2022 9AM (PDT)

Hello Chris,

IMO it's also worth pointing out that both FireFox put Web MIDI behind the
user's explicit permission, even for sending/receiving regular MIDI data.
Chrome will follow this model soon as well.
In terms of the new spec editor for Web MIDI API, I'll follow up with you
once we have a proper discussion within WG charis/editors.

Thanks for the updates!

Cheers,
Hongchan


On Thu, May 5, 2022 at 7:29 AM Chris Lilley <chris@w3.org> wrote:

> My regrets this week due to a conflict.
>
> Regarding the charter formal objections, most have been withdrawn but
> responses remain slow.
>
> I still need to address the "where is WebMIDI going" comment, which I
> will do by pointing out the long-drawn-out deliberations on security
> with SysEx and also the likelihood of an additional editor (I forget
> who, we had a name right). Then I think all the objections will be dealt
> with.
>
> On 2022-05-04 18:59, Hongchan Choi wrote:
> > Hello!
> >
> > Let's get back on track - we have interesting topics and updates to
> share!
> >
> > Meeting venue: https://meet.google.com/yee-dinj-tpq
> >
> > Agenda:
> > - Design discussion:
> >   - https://github.com/WebAudio/web-audio-api/issues/2400
> > - New issues
> >   - https://github.com/WebAudio/web-audio-api/issues/2487
> >   - https://github.com/WebAudio/web-audio-api/issues/2468
> > - Updates
> >   - Chrome updates: AudioContext.outputLatency, DevTools extension
> >   - WG Recharter updates
> >   - Web Audio Conference updates
> > - AOB
> >
> > Cheers,
> > Hongchan (on behalf of Audio WG chairs)
> >
> --
> Chris Lilley
> @svgeesus
> Technical Director @ W3C
> W3C Strategy Team, Core Web Design
> W3C Architecture & Technology Team, Core Web & Media
>
>
>