- From: s p <sebpiq@gmail.com>
- Date: Thu, 19 Feb 2015 09:16:59 +0200
- To: "public-audio@w3.org" <public-audio@w3.org>
- Message-ID: <CAGKuoCV8JfVEkUgiS26yaXO-VuzuorHw2MRBDyeXy3Udwve-4A@mail.gmail.com>
I copy / pasted the whole discussion to public-audio-dev. Please don't answer here anymore. On Wed, Feb 18, 2015 at 5:01 PM, s <johns@or8.net> wrote: > *beep* > > On 2/18/15 9:53 , s p wrote: > > This is the fact that right now > > audio runs in the main thread, and I was thinking at possibilities to > > run it somewhere else. Unfortunately node doesn't support > > multi-threading, which leaves us with multi-processing as only solution. > > i don't have a lot of experience with node, but i do know the > architecture is event driven. is it even possible to view the current > API from this perspective? > > obviously, each note is an event. but for "music" we need to put events > into a certain larger pattern ... this seems like an interesting type of > problem to me, but i may be misunderstanding it completely. > > -- > \js [http://or8.net/~johns/] - > > > -- *Sébastien Piquemal* -----* @sebpiq* ----- http://github.com/sebpiq ----- http://funktion.fm
Received on Thursday, 19 February 2015 07:17:28 UTC