<Dick> yes, good morning all. i'm on the telecon also.

aabb is Al

http://www.w3.org/2005/Incubator/audio/track/

http://www.w3.org/2005/Incubator/audio/wiki/Join_the_Audio_Incubator

http://www.w3.org/2005/Incubator/audio/wiki/

Chris Rogers: I have noticed that Mozilla are pushing Data API in Firefox4.

Al: I believe that is true.

Chris Rogers: It will be exciting to see that people can play with these APIs. It might be akward that there are multiple APIs out there.

eric_carlson: I agree with Chris, I think it's unfortunate. I assume that the API will be Mozilla prefixed. It's a shame that we've been making good progress and havn't had a chance to dicuss this.

Al: Yes it is definitely prefexed with "moz"

Chris Rogers: I think this may slow down the standardization process, perhaps adding complications. And I find it unusual that Dave Humphrey has not participated in the group.

Chris Rogers: We are where we are, we should still work towards common interests. We'll work slowly as developments come up and keep discussins on the list.

Al: I will ask Dave if he intends to participate in the group.

AudioNode.js: have Corban's audionode.js demos updated to work with the latest Mozilla build?

Al: Corban is not present, lets dicuss this in the next meeting.

Chris Rogers: Lets ask the BBC to define what use cases they would relevant.

Chris Rogers: I suggest we provide both lists of uses cases on the use-cases page.

Al: I will update this.

Chris Rogers: It's useful to look at all the types of audio on the desktop, and ask is it conceivable to implement this using a Web API. Secondly we should look at what is avilable on the web, such as cloud-based services and think about how they could be used for collaborative applications.

BBC are offering use-case sessions, see: http://lists.w3.org/Archives/Public/public-xg-audio/2010Aug/0018.html, how can we facilitate this?

MGood, I can review that for you.

Al: thanks.

User-feedback suggestions on Wiki: http://www.w3.org/2005/Incubator/audio/wiki/User-feedback, needs completing, reviewing.

General progress with webkit/chrome node-spec?

Chris Rogers: The latest development is that I added JavaScript audio node (sending the buffer to JavaScript) and documentation in the spec for that. It illustrates JavaScript processing. And I have been generally cleaning up the spec over the last couple of weeks and I have organised the use-case section.

Al: You can see links to Chri's progress here: http://www.w3.org/2005/Incubator/audio/track/actions/4

Chris Rogers: The example, though simple, would allow you to port any mozila (buffer based) api demos to the node-based API.

General progress with mozilla/firefox buffer-spec?

Al: As dicussed above, Mozilla have pushed the Audio Data API towards the trunk. Corban is unfortunately not present today, we will dicuss this more next meeting.

Creating a suitable test that compares performance of the native audio-node approach with the buffer-only approach.

Chris Rogers: I have made some measurements. We should keep in mind, CPU usage and latency.

Chris Rogers: The measurements I am making are based on the JavaScript FFT code from the mozilla builds. I am seeing between 5-10% CPU usage for spacializing a single source on top of the line hardware (processing in JavaScript).

Chris Rogers: Doing this natively uses 1% or less in my tests.

Chris Rogers: It will be possible to do a lot of audio tasks in JavaScipt, but when you add things like graphics and physics in JavaScript, it tends to bog down the CPU.

Provide side-by-side code-examples that demonstrate the simplest method of achieving a basic task with the buffer & node based specs.

1) Getting audio from a source, silently.

2) Swapping the left and right channels of the audio.

3) Listening to the resulting swapped channels.

Chris Rogers: in the case that you gave with swapping two channels and would be very similar (if not identical) in both specs. But the node based spec could use the node based splitter and merger.

Al: Chris R. could you work on this action with Corban?

Chris Rogers: Yes I could do this with Corban.

Al: We'll talk about this more on the mailling list.

Frequency & focus of group meetings.

Al: Should we increase the meeting frequency from bi-weekly to weekly?

Chris Rogers: I would prefer to use the mailing list to increase the activity.

MGood: I agree with Chris.

Al: None else? OK lets do that.

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Al
Inferring Scribes: Al
Default Present: +1.650.965.aaaa, +1.617.584.aabb, Eric_Carlson, +1.206.819.aacc, Al, MGood, Dick, dpenkler, +1.510.334.aadd, +1.510.334.aaee
Present: +1.650.965.aaaa +1.617.584.aabb Eric_Carlson +1.206.819.aacc Al MGood Dick dpenkler +1.510.334.aadd +1.510.334.aaee

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

Got date from IRC log name: 23 Aug 2010
People with action items: 

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