You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, when you use the disconnect method it disconnects all the nodes which can be a bit problematic. If you want to only disconnect one node, you then have to reconnect up everything else. Sometimes this can be difficult, especially if you don't know all of the nodes currently connected.
Do you know a way of getting round this?
Really great work on the new release!
The text was updated successfully, but these errors were encountered:
This is a product of how the Web Audio API is set up (spec). You cannot choose which node to disconnect from only which outlet of the node you want to disconnect.
One way to get around this would be to keep track of all of the nodes an object is connected to so that you can disconnect from a specific one. It would be a matter of disconnecting all of the nodes with disconnect and then reconnecting the ones that you still want to be attached. It's pretty ugly.
If you know you might need to disconnect a node from whatever it's connected to, you can route it through an intermediate GainNode and just disconnect that GainNode instead of all of the attached nodes. The send method (example) will create a GainNode for you which is connected through a named bus to whatever node receives it. send returns that GainNode so you can change the level of the routed signal or disconnect from the receiving node altogether.
Hey Yotam,
Is there a way to disconnect a specific node?
At the moment, when you use the disconnect method it disconnects all the nodes which can be a bit problematic. If you want to only disconnect one node, you then have to reconnect up everything else. Sometimes this can be difficult, especially if you don't know all of the nodes currently connected.
Do you know a way of getting round this?
Really great work on the new release!
The text was updated successfully, but these errors were encountered: