- From: Stuart Memo <stuartmemo@gmail.com>
- Date: Mon, 17 Dec 2012 18:08:37 +0000
- To: Srikumar Karaikudi Subramanian <srikumarks@gmail.com>
- Cc: Audio Working Group <public-audio@w3.org>
- Message-ID: <CAHZEqmr0SsZ_5s9RMcn3v6dPVmokOj_XmnXdjQgdHS8yRvV0Sg@mail.gmail.com>
Many thanks for this Kumar. That's great as an interim measure, but I feel that there should be some sort of standard way of doing this. Without a way of wrapping up nodes, sharing created effects or managing large projects becomes much more difficult. Thoughts? On 17 Dec 2012 06:36, "Srikumar Subramanian" <srikumarks@gmail.com> wrote: > You may find the GraphNode maker function in the linked file useful. It > makes an object that mimics the connect/disconnect functions of an > AudioNode, while supporting GraphNode objects, AudioNodes and AudioParams > as connection targets. > > https://github.com/srikumarks/steller/blob/master/steller.js > > The "function GraphNode..." is standalone. > > Best, > -Kumar > > On 17-Dec-2012, at 4:33 AM, Stuart Memo <stuartmemo@gmail.com> wrote: > > Hi all, > > I'm struggling to find a decent solution to packaging a group of nodes > together in a way that can be used similarly to native nodes. For example, > the recent Jam with Chrome article on html5rocks does this : > > var MyCustomNode = function(){ > this.input = audioContext.createGainNode(); > var output = audioContext.createGainNode(); > > this.connect = function(target){ > output.connect(target); > }; > }; > > Which means you have to connect to a node like so: > > gain.connect(customNode.input); > > Which is bananas! By having to specify '.input', it breaks the standard > way of connecting nodes. Is there a better way of doing this? If not, is it > worth discussing a way of packaging groups of nodes in a standard way? > > Thanks! > - Stuart > >
Received on Monday, 17 December 2012 18:09:06 UTC