<joe> agenda

<scribe> scribenick: ChrisL

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

joe: these ones have to be closed before CR

(7 open issues) are these the right ones? compare to webaudio v1 tag

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

matt: blocker means any other ones could be moved to v.next

<rtoyg_m> https://github.com/WebAudio/web-audio-api/issues/1116

hongchan: need to fix the periodic wave one

jerry: so it is just make the IDL valid

joe: and it has a PR we could review

matt: label added

joe 1138 will be part of fix to 95

scribe: same for 353

hongchan: 32 must/may

ChrisL: yes but don't want to mess up other PRs as it will be a lot of small changes

joe: ok so these are the real v1, vs the more likely to be v.next

matt: ppl can add issue blockers after the call

joe: but we need a cutoff. hoped it was today. what is a good date?

matt: tomorrow!

joe: ok quick status on each blocker
... audio buffer constructor

matt: paul said these four need rays comments to be addressed, mostly done.

joe: date?

matt: no. More time in next 3 months than last 3.

joe: 116 has a PR from ray,

ray: OK to lead on that

joe: 1089

matt: asked at BBC, hoped to have something back, will add once i have their feedback

ChrisL: smpte order for all of them?

matt: yes

jdsmith: we have different orders that may not be the smpte one, yet

joe: 1079 not done yet, but easy to get to now I am back. we downsized it
... 833 has no owner.

ray: editor discretion

(bikeshed vs respec summary)

ray: tab would help us with any conversion issues

matt: should we switch after CR?

ray: respec no longer supports the IDL we use

joe: resolution from call today is that switching to bs is scary and excessive before CR. but we need to fix up the IDL
... issue 95 has its own agenda item today
... dynamics compressor node 10

matt: reads paul - algo is defined, no more outstanding queries, spec remains to be written. not clear if we can use same thing as an expander

<joe> https://github.com/WebAudio/web-audio-api/issues/10#issuecomment-267675496

joe: no spec text to review at this time, just notes

chris: seems there is still an issue on the exact soft knee curve

joe: agreed

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

joe: 1144 and 1143 not finished yet

ray: mostly mine need reviewed

joe: 1147 we are not doing

ray: close, and point to the other one

joe: 1141, why is it not merged yet. paul reviewed it. so I can assign myself to respond
... 1065 waiting on paul and karl

joe; parts of 1024 subsumed by 95

ray: basic algo great when playback rate is positive. but negative rate, it does loop the are backwards, not clear how that falls out from the algorithm given

joe: let me explain why I think this is done

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

joe: lets have a rawgit link to review

<joe> https://rawgit.com/WebAudio/web-audio-api/057d63c29697af76c983702339fd968c225e5e88/index.html

<joe> https://rawgit.com/WebAudio/web-audio-api/057d63c29697af76c983702339fd968c225e5e88/index.html#playback-AudioBufferSourceNode

joe: adjust buffer time by a negative amount. computed pb rate is -1 so we subtract

ray: good so far

joe: effective buffer time does change, as it is getting smaller, and at the point where it gets to - what loop iteration are we in the iddle of?

ray: none, we just started.

joe: ok, but if you played one loop iteration going backwards, you hear just that backwards then nothing. no looping

ray: it would loop if we were going fwds

joe: play backweards from an offset is the reverse of forwards *including* the fact that only some number of loop iterations would have occured.
... can be an attack phase in front of the loop, you should get that too.

ray: agree, but text does not do that. buffer time decrements to zero and there is no check for loop conditions

joe: oh, crap something is missing!
... a change I made to address this is missing - oh, no it sn't. found it
... say effective buffer time is 3 loops on.

ray: so next step is not greater than loop end so is never modified.
... we go back to step 6

joe: right, so offset is in the middle which means there is only one loop iteration
... it would loop if offset exceeded the length of the buffer

chris: so you are unrolling the loop, the virtual buffer has all the loop iterations one after the other

joe: exactly

ray: ebt would wrap to beginning but then gets decremented so it is in the middle of the loop

I think a diagram would be helpful here

joe: step 3 is where the wrapping happens

ray: your algorithm does not do that

joe: if offset exceeds...

ray: it never ever loops

joe: it loops once

ray: should loop forever

joe: wen the playhead is in the loop, you want it to never leave
... not clear how to oget both uses together, we trap the play head and reverse out everything so far

ray: taht is not what people expect
... play the loop, in reverse, forever

chris: can the api express both use cases?

joe: developer needs to indicate what they want

ray: just turning looping off
... but doing it yourself defeats the purpose
... loop end and loop start could be changed live

joe: can add that
... need to think on this. any other opinions on the call?

ray: maybe a new issue om the desired behaviour?

joe: won't help really
... we can see what that language looks like

ray: isolate the different use cases

matt: will send email round about web audio conference

joe: next call in 2 weeks

adjourned

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/ting/thing/
Succeeded: s/0124/1024/
Succeeded: s/warap/wrap/
Present: jdsmith joe rtoyg_m
Found ScribeNick: ChrisL
Inferring Scribes: ChrisL

WARNING: No "Topic:" lines found.

Found Date: 02 Mar 2017
Guessing minutes URL: http://www.w3.org/2017/03/02-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