Audio WG Teleconference -- 28 Feb 2013

<scribe> Scribe: Olivier

<scribe> ScribeNick: olivier

MIDI security

https://github.com/WebAudio/web-midi-api/issues/3

cwilso: if you read the whole thread in the issue, it didn't seem we could separate out any graduation that would be reaully useful

… since then have talked to a number of people in security and privacy, and figuring out what MIDI devices can do

<cwilso> still here, just a sec

… figured out anything other than system exclusive messages was safe

cwilso: similar to gamepad API

… was important to call out separation between system exclusive messages and other MIDI support

… I added that to the spec, explaining the utility you get from system exclusive messages

… we can't just not support it

… a number of scenarios use it

… so we need to call it out as a separate security model

… let the developer state that they want it or not

… if (by default) they don't need it then they're fine

cwilso: it's mostly a proposal
... Jussi looked at it last night and seemed happy with it

chrislowis: not hearing any objection from anyone else either

cwilso: happy to go ahead and close, and reopen if there is any objection

… goal was to enable as much as possible securely

joe: reviewed it too, think it's a great change

… only question - should there be a way to provide finer grained capability in the future?

cwilso: good question - thought about it

… we are already buried in minutiae of MIDI

… so tried to make it as simple as possible

… avoid "hey do you want to allow MIDI machine control"

… users would go "HUH?"

joe: agreed

RESOLUTION: closing the issue

Logistics for the face to face meeting in March

chrislowis: reminder to register

olivier: 13 registrants so far

… almost all usual suspects except ROC and Jussi, who probably won't make it

cwilso: if you're flying, cheapest way from SFO is caltrain

… don't rent a car unless you have to

… overnight parking is very expensive

… do try to fly to SFO not San Jose

… (especially at rush hour!)

olivier: reminder to tell me if you have to fly at end of second day, so we can have agenda ending early

cwilso: also, book your hotel ASAP

olivier: Mr Kawai from Yamaha will be at GDC, would love to meet with people from the group

cwilso: ditto Tom White from MMA

chrislowis: copy team-audio and we can always schedule some time with them
... do you think there will be appetite for demos at google office while we're there?

cwilso: not sure, will have to ask chrisrogers

zakim: take up agendum 2

Use of EventListener for onaudioprocess

chrislowis: crogers not in today, probably no point looking at this now

… but give people time to look at it

AOB

chrislowis: anything else?

gmandyam_: discussions at [?] meeting about web audio processing

… some of the usual points, already made here, were made there

s[?]/WebRTC

gmandyam_: surprised because there was a joint meeting in 2011 and it was decided that web audio API was suitable

<chrislowis> olivier: doesn't recall exactly that it was agreed then that ...

<chrislowis> ... web audio api would be suitable

<chrislowis> We should get together with them and reassess why we've chosen the web audio api and why we think it's suitable

<chrislowis> and if it's not to take input into what would make it more suitable

gmandyam_: if their concerns are legitimate they should be brought in, but it just seems the 2011 conclusions don't seem to have stuck

<scribe> ACTION: olivier to talk to webrtc chairs, see what their perspective is on web audio API [recorded in http://www.w3.org/2013/02/28-audio-minutes.html#action01]

<trackbot> Created ACTION-59 - Talk to webrtc chairs, see what their perspective is on web audio API [on Olivier Thereaux - due 2013-03-07].

doug: at W3Conf last week, we did something a little bit clever

… we were able to take the pointer events spec to LC just before the conf, the editor came and gave a presentation at the conf

… also published overview and reference on webplatform.org and webplatformdocs

… seems that we could do something similar around web audio

… or web midi API

… thinking of having next W3Conf in 6 months

<chrislowis> olivier: good idea.

<chrislowis> olivier: I think this is something we could try and tie in to the community group

<chrislowis> ... that we just started to have more of a forum for audio developers to talk

<chrislowis> about how they do things with the APIs

<chrislowis> One of the reasons for starting the group was to see if there would be an appitite

<chrislowis> among the developer community to help us with documentation, tutorials, maybe a primer etc.

doug: we were also thinking of having workshops

… for next W3Conf

… which is being organised near me

… would be cool to have web audio workshop in a local club

… hacking sounds together

[hearing a "sounds fantastic" cry of approval]

doug: would be even better if we could get to LC before that

… or even delay it so we can announce it at the conf

… another great thing to announce there would be (experimental) support in another browser

doug: I volunteer cwilso to present at W3Conf

… showing both APIs would be great

… dates Aug 28/29 2013

… Durham, NC

… big tech area in the US

… giving the east coast a little love

Joe: count me in, I'm coming

cwilso: will be giving similar talks in late spring

chrislowis: doug, please send details of the event to the list

doug: still tentative though

<scribe> … pending approval and sponsorship

chrislowis: anything else

[adjourned]

- DRAFT -

Audio WG Teleconference

28 Feb 2013

Attendees

Contents

MIDI security

Logistics for the face to face meeting in March

Use of EventListener for onaudioprocess

AOB

Summary of Action Items

Scribe.perl diagnostic output