<rtoyg_m> present rtoyg_m

<hoch> (we're muted)

Review Pull Request status (all open ones should have been reviewed by this call)

<joe> https://github.com/WebAudio/web-audio-api/pulls

https://github.com/WebAudio/web-audio-api/pull/1176

<hoch> (sorry we've been muted heh)

joe is there something outstanding here, or does the text cover this?

rtoyg_m additional paragraph to state mono in + mono reponse = mono out

https://github.com/WebAudio/web-audio-api/pull/1170

joe needs tidy = small editorial change.

<joe> https://github.com/WebAudio/web-audio-api/pull/1168

padenot overhaul of constructors, might make sense to wait on this until the rest of the constructors are finished. Blocked by other PRs

<joe> https://github.com/WebAudio/web-audio-api/pull/1161

<ghaudiobot> [web-audio-api] rtoy closed pull request #1168: Fix #1152: Define OfflineAudioContext constructor with dictionary (gh-pages...1152-add-offline-context-dictionary) https://github.com/WebAudio/web-audio-api/pull/1168

joe review has been added, needs approval.

padenot approved.

<ghaudiobot> [web-audio-api] joeberkovitz closed pull request #1161: Clarify normative aspects of AudioNode lifetime. (gh-pages...1079-algorithmic-awn-lifetime) https://github.com/WebAudio/web-audio-api/pull/1161

<ghaudiobot> [web-audio-api] joeberkovitz pushed 1 new commit to gh-pages: https://github.com/WebAudio/web-audio-api/commit/ba35ac1ac62aa4124a39970e270e348f5f47c5c3

<ghaudiobot> web-audio-api/gh-pages ba35ac1 Joe Berkovitz: Merge pull request #1161 from WebAudio/1079-algorithmic-awn-lifetime...

<ghaudiobot> [web-audio-api] joeberkovitz deleted 1079-algorithmic-awn-lifetime at 2859924: https://github.com/WebAudio/web-audio-api/commit/2859924

<joe> https://github.com/WebAudio/web-audio-api/pull/1150

ChrisL concerns that clamping to non zero float may have odd results

ChrisL happy to close and merge

<joe> https://github.com/WebAudio/web-audio-api/pull/1143

<ghaudiobot> [web-audio-api] rtoy closed pull request #1150: Fix #1105: Allow refDistance to be 0 for PannerNode (gh-pages...1105-allow-refdistance-0) https://github.com/WebAudio/web-audio-api/pull/1150

<ghaudiobot> [web-audio-api] rtoy pushed 2 new commits to gh-pages: https://github.com/WebAudio/web-audio-api/compare/ba35ac1ac62a...f0af217bf6ca

<ghaudiobot> web-audio-api/gh-pages e629c03 Raymond Toy: Fix #1105: Allow refDistance to be 0 for PannerNode...

<ghaudiobot> web-audio-api/gh-pages f0af217 rtoy: Merge pull request #1150 from rtoy/1105-allow-refdistance-0...

padenot mostly good couple of minor things joe happy to take care of these. padnot make sure unit tests exist and that implementations behave in the same way

rtoyg_m tests will take a while, lots of corner cases to cover.

joe have addressed some of the corner cases in the diagrams

<joe> https://github.com/WebAudio/web-audio-api/pull/1065

<joe> https://github.com/WebAudio/web-audio-api/pull/1024

joe good to go? padnot going to look into 1065.

Go over new issues and assign to v1/v.next milestones

joe to close this out and review once #95 is resolved

<joe> https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

<joe> https://github.com/WebAudio/web-audio-api/issues?q=is%3Aopen+is%3Aissue+no%3Amilestone

<joe> https://github.com/WebAudio/web-audio-api/issues/1173

rtoyg_m dictionary for periodic wave cant leave unspecified as there is a default value of sine. Text is no longer correct. Either change so you always have to specify type or have to set to custom rather than omitting.

joe we just need to decide if these issues are v.1 or v.next, rtoyg_m we need to fix now

joe which option do people prefer, rtoyg_m option 2, padenot option 2.

joe option 3 does not break existing code, ChrisL also prefers option 3.

rtoyg_m if you don't specify type it makes sense but otherwise you are overiding the type

joe any objections to option 3 - jdsmith votes option 3 rtoyg_m 3 fine. Option 3 choosen - v1 blocker

<joe> https://github.com/WebAudio/web-audio-api/issues/1172

joe don't see this as big deal

joe mark this as v.next let implementaitons do what they think is sensible.

padenot meant that programs would not be interoperable. Forbidding empty string would be preferable

hoch not allowing empty string is the simplest solution - agreed

<ChrisL> yes that seems easier

<joe> https://github.com/WebAudio/web-audio-api/issues/1171

padenot we can proceed with this issue - don't think it will be a breaking change but needs to be fixed, simple idl fix you can use a nicer syntax to specify the value curves. Moved to v.1

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

<joe> https://github.com/WebAudio/web-audio-api/issues/1166

joe should we do this now?

padenot its minor and an edge case, no preference

padenot but its not a lot of work

jdsmith would it be breaking if we did it later padenot technically yes

rtoyg_m in chrome we cannot do what the spec says in this case

rtoyg_m we only have to take care of this particular case can't return TypeError, need to return something else.

joe shall we take this on for v.1 or not?

rtoyg_m this is true in other areas of the spec, but decodeAudio is the only case that need to be handled now.

padenot throw DataClonError if detatched - moved to v.1

<joe> https://github.com/WebAudio/web-audio-api/issues/1165

rtoyg_m move off to v.next

<joe> https://github.com/WebAudio/web-audio-api/issues/1160

rtoyg_m nice to have can move to v.next - no objections

zakim, next agendum

Review existing issues marked as requiring WG Review

<joe> https://github.com/WebAudio/web-audio-api/issues?q=is%3Aissue+is%3Aopen+label%3A%22Needs+WG+review%22

<joe> https://github.com/WebAudio/web-audio-api/issues/1162

rtoyg_m no investigated yet. Moving on

<joe> https://github.com/WebAudio/web-audio-api/issues/787

hoch it is not possible to address this in the WAAPI - padenot our issue is how to talk to the default device

<ChrisL> padenot, got a link to those issues that got closed without discussion?

Go over new issues and assign to v1/v.next milestones

staying in v.next need coordination with other groups

Discuss specific dates for F2F meeting

<joe> matt: most people filled in the poll

<joe> matt: one conflict, no date is perfect. have to choose between Hongchan and ChrisL

<joe> ACTION: looking for Bosnt 20/21 either at Noteflight or MIT Matt Chris and Joe to followup [recorded in http://www.w3.org/2017/03/30-audio-minutes.html#action01]

<trackbot> Error finding 'looking'. You can review and register nicknames at <http://www.w3.org/2011/audio/track/users>.

Review progress on blocking issues

<joe> padenot: can get to compressor after finishing constructor PR

Any other issues for discussion

next call 13th April

trackbot, end meeting

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/this/1065/
Default Present: joe, rtoyg_m, padenot, hongchan, ChrisL
Present: joe rtoyg_m padenot hongchan ChrisL
No ScribeNick specified.  Guessing ScribeNick: mdjp
Inferring Scribes: mdjp

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

Found Date: 30 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/30-audio-minutes.html
People with action items: 20 21 at bosnt chris either for joe looking matt mit noteflight or

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