Re: Running WebAudio code outside of a browser?

@johns the fact that many calls in node are asynchronous (as in JavaScript
in the browser) really doesn't cause any problem you can pretty much do
anything with this paradigm. DSP calculations happen synchronously anyways,
so that's not an issue. as for "events" you can perfectly have those
scheduled in a synchronous way as well. Typically asynchronous calls are
for input/output so for example writing a file to a disk (task which
doesn't use the processor) so that is not really a concern here.

On Thu, Feb 19, 2015 at 9:17 AM, s p <sebpiq@gmail.com> wrote:

> Here is the thread, migrated from public-audio
>
>
> -----------------------------------------------------------
> On Wed, Feb 18, 2015 at 5:01 PM, s <johns@or8.net> wrote:
>
> *beep*
>
> 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/] -
>
> -----------------------------------------------------------
> On Fri, Feb 18, 2015 at 3:00 PM, s p <sebpiq@gmail.com> wrote:
>
> Chinmay that's a great idea! If there are people willing to help, I'm
> happy to coordinate the effort.
> However, there is in my opinion one biggie that should be addressed before
> more functionalities are added. 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. However, the major issue with that
> is sharing / transferring of big buffers. There was a discussion going on
> in this thread : https://github.com/sebpiq/node-web-audio-api/issues/16
>
> Once we get the architecture right, I think this up-for-grabs is a great
> idea!
> -----------------------------------------------------------
>
> On Wed, Feb 18, 2015 at 2:55 PM, rl baxter <baxrob@gmail.com> wrote:
> I suppose it's called
> https://lists.w3.org/Archives/Public/public-audio-dev/ and/or
> https://www.w3.org/community/audio-dev/
>
> -----------------------------------------------------------
>
> On Wed, Feb 18, 2015 at 4:43 AM, rl baxter <baxrob@gmail.com> wrote:
> What is "the right way" to redirect a thread from web-audio to
> web-audio-dev? I want to comment on this, though it's obviously not
> spec-related.
>
> -----------------------------------------------------------
>
> On Wed, Feb 18, 2015 at 1:46 AM, Chinmay Pendharkar <notthetup@gmail.com>
> wrote:
> Hey Sebastian,
>
> I think getting the community behind this and maintaining a standards
> compliant nodejs version of WebAudio API would be something very useful and
> powerful to have in the long run.
>
> I will definitely try to spend some weekends trying work on unimplemented
> Nodes.
>
> I was wondering how we could get more people in the WebAudio community to
> help out with implementing parts of this. Would breaking down features and
> tagging them up something like 'up-for-grabs' (http://up-for-grabs.net/)
> help?
>
> -Chinmay
>
> -----------------------------------------------------------
>
> On Fri, Feb 13, 2015 at 10:10 PM, s p <sebpiq@gmail.com> wrote:
> Hi Tristan,
>
> I've been working on this, with help from some other people :
> https://github.com/sebpiq/node-web-audio-api
>
> There is barely any node : ScriptProcessorNode, GainNode and
> BufferSourceNode. Samuel Goldszmidt started adding Oscillators and Delay
> nodes here :
> https://github.com/sebpiq/node-web-audio-api/tree/Oscillator+DelayNodes
> but he said it still needs some work.
>
> So you can use it, but keep in mind that it is really a work in
> progress!!! And also, I think the codebase is pretty clean, and documented,
> so if you feel like implementing more nodes :D
>
> -----------------------------------------------------------
>
> On Thu, Feb 12, 2015 at 5:02 PM, Tristan Strange <
> tristan.strange@gmail.com> wrote:
>
> Is there a JS engine that will let me do this?
>
> Cheers,
> Tristan
>



-- 

*Sébastien Piquemal*

 -----* @sebpiq*
 ----- http://github.com/sebpiq
 ----- http://funktion.fm