Re: Sample-accurate JS output (was: scheduling subgraphs)

>
> Having a single JavaScriptAudioNode with multiple channels would be  
> one approach, but it clearly seems less elegant than having more  
> than one JavaScriptAudioNode.  Even now, the API allows for more  
> than one, albeit without some of the fancier scheduling smarts that  
> Joe B has suggested.  I'm concerned about complex implementation  
> details and performance problems in dealing with this case, but I've  
> considered this problem some more and think there may be some  
> interesting tricks to get around some of the issues I was worried  
> about.  If multiple simultaneous JavaScriptNodes can be made to work  
> well (at least no worse than a single JavaScriptAudioNode doing  
> equivalent work) then I think it would be very powerful, especially  
> combined with Joe B's ideas.  But, I think we need to proceed  
> cautiously here until it can be shown to work.
>

Implementation thought:

I was thinking, if all JS nodes process sample batches in lock step,  
can all active JS nodes be scheduled to run in sequence in a single  
thread context switch, instead of context-switching once per node?

... .  .    .       Joe

Joe Berkovitz
President
Noteflight LLC
160 Sidney St, Cambridge, MA 02139
phone: +1 978 314 6271
www.noteflight.com