- From: Marcus Geelnard <mage@opera.com>
- Date: Wed, 13 Jun 2012 11:16:06 +0200
- To: "Ray Bellis" <ray@bellis.me.uk>
- Cc: public-audio@w3.org
Den 2012-06-13 10:42:58 skrev Ray Bellis <ray@bellis.me.uk>: > On 13/06/2012 08:34, Marcus Geelnard wrote: > >> This is good feedback. Since I'm trying to find good use cases for >> numberOfInputs/Outputs (but so far I've failed), could you please >> elaborate a bit on what you need them for? > > Take a look at the link I sent (http://alnitak73.dyndns.org/) using > Chrome Canary. Really nice! Reminds me of Buzz (http://www.buzzmachines.com/images/screenshots/machineview.jpg), but better looking ;) > I use it to automatically build a visual representation of any AudioNode > by probing the node for its I/O and AudioParam capabilities. I see your point. I guess it COULD be solved by wrapping all audio nodes in custom node objects or something similar. Not sure which is more practical from a code design point of view. Since there are probably lots of other stuff you need to keep track of in a GUI anyway, adding graph data to that representation might be manageable (e.g. since you already need to know the names of the node constructors, you could also supply your own in/out counts etc in the VisualNode() constructor)? /Marcus
Received on Wednesday, 13 June 2012 09:16:35 UTC