See also: IRC log
<scribe> scribenick: BillHofmann
rtoyg_m: no formal definitions in pull currently
joe: in order to avoid going back and forth, what do you propose?
rtoyg_m: would like to update pull with coefficients and get a yes/no decision
<padenot> cwilso: I don't have much on the audioworker or the like, I was under water with mozilla stuff and travels recently
joe: will record decision in PR
<padenot> cwilso: there has not been a lot of activity on worklets, though, and I'm currently picking up my stuff (processing model, etc.) so we can merge soon
<cwilso> padenot: 'k. I'll start back in on the aw APIs soon, then.
<joe> https://github.com/WebAudio/web-audio-api/pull/620
joe: will specify normalization or not when you do coefficients
<padenot> cwilso: we still need some worklet infra, last I checked, I should ping iank about it
<padenot> who, me ?
<joe> padenot: can you join the call?
<padenot> I'm on
padenot: just wants to get this
done - not sure if we need min/max
... want to merge existing patches (without min/max). Min/max
are useful (to me) to expose controls, but...
joe: in favor of not doing things someone isn't advocating for
rtoyg_m: likes min/max for introspection
padenot: will merge first, then consider min/max/default
<joe> https://github.com/WebAudio/web-audio-api/pull/624
joe: seems uncontroversial - is it ready to commit?
padenot: just need to review and
merge...
... will put it in my todo list for tomorrow
<joe> https://github.com/WebAudio/web-audio-api/pull/627
joe: looks like this is just
pending some minor comments/typo fixes
... will assign to padenot, straightforward
<joe> https://github.com/WebAudio/web-audio-api/pull/632
rtoyg_m: just want to upgrade floats to doubles, more accuracy
<ghaudiobot> [web-audio-api] padenot closed pull request #632: createIIRFilter takes double coefficients (gh-pages...631-createIIRFilter-doubles) https://github.com/WebAudio/web-audio-api/pull/632
joe: any reason to not just go with this?
padenot: done!
<joe> https://github.com/WebAudio/web-audio-api/pull/644
padenot: almost finished, what's
left is the ordering algorithm, almost there (edge case
issues)
... since it's big, we ought perhaps merge except for the
ordering algorithm
joe: we should merge
... who should review?
... action to group to review this pull
... let's get put the review deadline in a week (10 Dec)
<joe> https://github.com/WebAudio/web-audio-api/pull/645
https://github.com/WebAudio/web-audio-api/pull/645
joe: this looks small, can this
just be merged?
... looks contaminated, propose padenot fix
padenot: relies on 644, so should wait til that
<joe> https://github.com/WebAudio/web-audio-api/pull/646
<joe> https://github.com/WebAudio/web-audio-api/pull/647
billhofmann: 647 is the same - also processing model
joe: should these also be reviewed with 644?
padenot: should review 644, 646, 647
<joe> https://github.com/WebAudio/web-audio-api/pull/647
<joe> https://github.com/WebAudio/web-audio-api/pull/649
billhofmann: substantive change
was the first change, rest is tidy changes
... referring to 649
rtoyg_m: good to go
<joe> https://github.com/WebAudio/web-audio-api/pull/651
billhofmann: note added first constructor, discussion of naming
rtoyg_m: only important is name of property
joe: what are the choices?
... notes it is/should be playbackCategory
billhofmann: will fix merge conflicts and merge today
joe: proposes next call in 2 weeks (Dec 17)
<joe> Next call on 12/17
shepazu: do you need staff support?
joe: had asked Chris Lilly to publish a WD, had no response
shepazu: he was speaking in Nov, can push that out
joe: just emailed him, will follow up with shepazu if no response
shepazu: publishing moratorium in a week or two, would be good to work with Chris Lilly to get all the pubs stuff out properly
joe: can you please take this on?
<joe> https://github.com/WebAudio/web-audio-api
shepazu: have a new tool to
autopublish, but need to make sure there are no publishing
issues
... right thing to do is for me to work with Chris to resolve
the issues
... there's a new stylesheet coming in January
<rtoyg_m> validator.w3.org only finds 6 warnings on the current webaudio spec.
<rtoyg_m> Well, 4 warnings and 2 info.
shepazu: slightly narrower, *probably* won't cause any issues, but should check
<shepazu> http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample
<shepazu> New style for 2016: http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample
<joe> http://webaudio.github.io/web-audio-api/
shepazu: let's follow up in a half an hour or later
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. Default Present: BillHofmann, mdjp, hongchan, cwilso, rtoyg_m, jdsmith, shepazu Present: BillHofmann mdjp hongchan cwilso rtoyg_m jdsmith shepazu 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: 03 Dec 2015 Guessing minutes URL: http://www.w3.org/2015/12/03-audio-minutes.html People with action items: 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]