W3C

- DRAFT -

SV_MEETING_TITLE

14 Jan 2016

See also: IRC log

Attendees

Present
padenot
Regrets
Chair
SV_MEETING_CHAIR
Scribe
BillHofmann

Contents


I'll scribe

scribenick BillHofmann

<scribe> scribenick: BillHofmann

<joe_> https://github.com/WebAudio/web-audio-api/issues/686

padenot: marked as ready for edit

<joe_> https://github.com/WebAudio/web-audio-api/issues/687

joe: ...687 seems to already be in progress

padenot: I have something for this

<joe_> https://github.com/WebAudio/web-audio-api/issues/688

rtoy_g: display issue with MathJax and Chrome - requires W3C to update

joe: important enough?

BillHofmann: can we just assign to someone in W3C?

cwilso: will follow up

<joe_> https://github.com/WebAudio/web-audio-api/issues/689

rtoy_g: lots of corner cases here... will create specific corner case issues and we can discuss each.

joe: 344 is merged - will close

<joe_> https://github.com/WebAudio/web-audio-api/issues/344

<joe_> https://github.com/WebAudio/web-audio-api/pull/580

joe: agree with the disposition, will comment in-bug

<joe_> https://github.com/WebAudio/web-audio-api/issues/690

<joe_> https://github.com/WebAudio/web-audio-api/pull/691

rtoy_g: have num channels, can't get length until end, but would be good to have earlier
... have a pull

joe_: there are a number of failures of introspection. Paul: are you OK with adding this?

<padenot> it's kind of voiping here sorry

padenot: OK

<joe_> https://github.com/WebAudio/web-audio-api/issues/692

rtoy_g: note distinction between MediaCapture spec and our spec (float vs enum)

BillHofmann: goal was to not overconstrain UAs -

rtoy_g: so many devices - not really practical

padenot: a number doesn't really make sense, because what's good for some devices is bad for otheres

joe_: these are actually hinting *different* things - one is a buffering hit (webaudio) the other about device selection

padenot: well, it controls both, actually

joe_: device selection is an open item in WebAudio...

padenot: if you have a big buffer in the webaudio API, does it make sense to have a low latency device?

jdsmith: isn't latency in MediaCapture a negotiated constraint?

joe_: opening a MediaCapture spec issue is fine, and pointing at our choice. Don't believe it's a requirement. Reconciling the two specs is a post-V1 effort

BillHofmann: proposal is close this issue and open a MediaCapture issue.

jdsmith: their approach is consistent with how they deal with attributes.

<scribe> ACTION: padenot to open issue against MediaCapture re 692 [recorded in http://www.w3.org/2016/01/14-audio-minutes.html#action01]

<trackbot> Created ACTION-123 - Open issue against mediacapture re 692 [on Paul Adenot - due 2016-01-21].

https://github.com/WebAudio/web-audio-api/issues/693

hongchan: this is a disparity between browsers - behavior is not clearly defined.
... e.g. Chrome updates on every rendering quantum

<joe_> https://github.com/WebAudio/web-audio-api/issues/318

joe_: there was an issue (318) that specified this value
... decision was that callers need to do their own calculation
... no-one recalls the decision, alas
... leave this open, will comment 318 that this still needs resolution

padenot: still need some features in Worklet so we can base AudioWorker off it, are really blocked
... propose we contact author and ask him to resume his work on it.
... OR we could write our own bits

joe_: is it possible that we/you could take this on, really?

padenot: definitely key infrastructure

<scribe> ACTION: padenot to email author cc list and see what happens [recorded in http://www.w3.org/2016/01/14-audio-minutes.html#action02]

<trackbot> Created ACTION-124 - Email author cc list and see what happens [on Paul Adenot - due 2016-01-21].

joe_: next item is progress on PRs
... has been reasonable progress offline - does anyone have questions worth surfacing here?

<padenot> wfm

joe_: propose 2 weeks from now for call

works for me

<hongchan> wfm

<jdsmith> fine with me as well

<padenot> bye !

<rtoyg_m> Aloha!

Summary of Action Items

[NEW] ACTION: padenot to email author cc list and see what happens [recorded in http://www.w3.org/2016/01/14-audio-minutes.html#action02]
[NEW] ACTION: padenot to open issue against MediaCapture re 692 [recorded in http://www.w3.org/2016/01/14-audio-minutes.html#action01]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/01/14 17:47:48 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: BillHofmann
Inferring Scribes: BillHofmann

WARNING: No "Topic:" lines found.

Present: padenot

WARNING: Fewer than 3 people found for Present list!


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 14 Jan 2016
Guessing minutes URL: http://www.w3.org/2016/01/14-audio-minutes.html
People with action items: padenot

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]