Sebastien Piquemal

@fmammoli Awesome! Looking forward to see the final result! As for the abstractions I am not sure I understood how you get them to be found in your patch. You...

@domchristie @felixroos thanks for testing this ! As far as I am concerned, that confirms one thing which I was already convinced of since the inception of Web Audio, is...

@felixroos yes sorry ... I was a bit harsh haha ... but I spent so much energy in trying to hack my way around the limitations of WAA for more...

Would be great if this could be merged :)

this will be hard as node doesn't really support threading nor fork. So objects sent between 2 process are all serialized ; deserialized, which is not acceptable in our case.

http://neilk.net/blog/2013/04/30/why-you-should-use-nodejs-for-CPU-bound-tasks/

Try and benchmark solutions for avoiding buffer copies between processes https://github.com/3rd-Eden/node-memcached https://github.com/supipd/node-shm https://github.com/kazupon/node-mappedbuffer

Hmm ... I don't really understand why AudioBuffer#getChannelData() causes a problem. Could you explain to me? Actually, thinking about it, I don't see any operation between audio thread and main...

Yes ... but in SuperCollider buffers are allocated server-side. The client-side instance of buffer is merely a proxy to do a bunch of selected operations. For example you don't have...

To me this is the single most important issue before dev can progress on the library. The architecture should be right, and I think it won't be right if audio...