See also: IRC log
<scribe> Scribe: Olivier
<scribe> ScribeNick: Olivier
<FILT3R> kk
<FILT3R> ok thanks shepazu
F1LT3R, I already set up the meeting :)
<Alistair> ah
<Alistair> lol thankyou! :)
right
<scribe> Agenda: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0547.html
<scribe> Scribe: Olivier
<scribe> Chair: Al
<scribe> ScribeNick: Olivier
<gcardoso> hi! I am trying to reach the call via the Europe bridge +33.4.89.06.34.99... no answer
<jernoble> is the passcode the normal one today? I'm being told it's incorrect.
should be - AUDIO
<jernoble> Zakim aabb is me.
<Al> https://www.w3.org/2011/audio/track/issues/8
Al: seems like you have to create an obscure graph for the realtimeanalysernode to function as expected
CRogers: would not say obscure, but the node does need for it to have an output
… a lot of people think it should just have an input - hang at the end of the graph
… got one e-mail from James, and another out of the blue
… may be more intuitive if it worked that way, even if it's not the way it works now
CRogers: of course you need an input connected for it to work
you could connect the output if you wanted to, as a pass-through
Al: seems like an issue where everybody agrees
[General agreement]
Olivier: are we agreeing that the output should be optional, or none?
[general agreement on optional]
Resolution: make the output for the realtimeanalysernode optional
https://www.w3.org/2011/audio/track/issues/84
Al: question on how to handle sources with different sample rates
CRogers: proposed solution is that the audio context in its constructor could give the desired sample rate as a constructor argument
… currently not the case, the sample rate chosen to be that of the audio hardware
… doesn't mean that each node could have a specific sample rate though, but would solve most of the problem
Jussi: agree it would solve the problem, seems to complicated to add a resample node at this point
CRogers: seems like a good way to go
Al: would a stream be automatically resampled them?
… was assuming from discussion in mailing-list that there could be sources with different sample rates
CRogers: even the current web audio API handles heterogeneous sample rates fine
… the sample rate is converted automatically
CRogers: in most cases it does not matter, but in Jussi's case (decoding an MP3 file at a specific sample rate) it would make sense
Al: I understand your solution would cover Jussi's use case?
CRogers: I believe so. you create a simple graph with a given sample rate
Jussi: it fixes most of the problem. Would have to treat different sources in different graphs
… edge cases would still be complicated, would have to implement resampling
<Al> Olivier: Chris, you said the web audio api implementation already handles hetrogeneous sample rates just fine. Has this been specified / documented at this stage? And is there a risk that would be implemented differently by different developers?
CRogers: we could yes, but it's assumed - it doesn't make sense not to. I don't believe the HTML5 spec covers such a scenario
<Al> Olivier: If there is a good reason to spec. it. If not, fine.
CRogers: I would just leave it as it is
Olivier: fine with me
Al: can we record resolution?
Olivier: seems like we have consensus around a solution that would work for most cases
CRogers: would like to point out that default sample rate is best (performance wise) so the spec should say that it's better not to add it unless needed
Jussi: agreed
Olivier: makes sense
Resolution: add a constructor parameter for audio context to specify sample rate - make sure to specify that default is best unless needed
Al: wondering where we stand on this one
… ROC would have some input but sent regrets
https://www.w3.org/2011/audio/track/issues/46
Jussi: been working on some effects using javascriptnode - would be useful if the javascriptnode could also create audioparams for themselves
CRogers: yes, Jussi came up with the most minimal API that would cover this
… probably nothing wrong with it, but we'll have to be careful, especially in the context of the integration with webRTC
… seems like this may be hard to implement
Al: wondering what we would lose if we don't have it in the 1st version of the spec
CRogers: we would most lose the ability for a javascriptnode to leverage the audioparam API
… you could probably implement it in your own code, probably less performant
… but there are ways to deal with it in JS without it
… would be useful, but sounds like icing on the cake for me
Jussi: agreed - it's more boilerplate for developers
Al: is this something that would be wise to put in 2nd version of the spec
CRogers: happy to leave this open, not focus on it right now
Olivier: we should ask people if they absolutely need it, if not I agree we should close this as LATER
<scribe> ACTION: Al to ask for feedback on making ISSUE-6 a "nice to have" that we may not include in version 1 of the web audio API [recorded in http://www.w3.org/2012/04/02-audio-minutes.html#action01]
<trackbot> Sorry, couldn't find user - Al
<scribe> ACTION: Alistair to ask for feedback on making ISSUE-6 a "nice to have" that we may not include in version 1 of the web audio API [recorded in http://www.w3.org/2012/04/02-audio-minutes.html#action02]
<trackbot> Created ACTION-43 - Ask for feedback on making ISSUE-6 a "nice to have" that we may not include in version 1 of the web audio API [on Alistair MacDonald - due 2012-04-09].
Al: just checking on progress
Jussi: haven't had time to get started - will do ASAP
<Al> https://www.w3.org/2011/audio/track/actions/42
(ACTION-42 postponed 1 week)
<Al> https://www.w3.org/2011/audio/track/actions/41
Al: so far we don't have volunteers to document this issue
CRogers: will be changing the values, they were provisional
… the spec currently doesn't say anything about ranges
… those values probably come from source
Al: or someone testing it
CRogers: the action should be to
update the spec
... I can update that
Al: will update
<jussi> ^^
ADJOURNED
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/rangers/ranges/ Found Scribe: Olivier Inferring ScribeNick: olivier Found ScribeNick: Olivier Found Scribe: Olivier Inferring ScribeNick: olivier Found ScribeNick: Olivier Present: Al Olivier Cwilson Crogers Jussi Jer Gabriel Regrets: Doug Joe ROC WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Agenda: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0547.html Got date from IRC log name: 02 Apr 2012 Guessing minutes URL: http://www.w3.org/2012/04/02-audio-minutes.html People with action items: al alistair WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]