-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to express circular connections #2
Comments
Hey @jussi-kalliokoski, Thanks for reaching out! I think this is a general limitation of expressing a multidirectional graph model using a tree, but I have a couple of ideas to mitigate this. I'll address this properly over the next few days and share my thoughts with you. I agree with your points on refs. I thought of implementing the function-based version (i.e. |
Yeah, good call, people are already struggling with understanding how function
Sounds cool, looking forward to it! |
One idea I have that should work with the existing version of Wax is: const gain = <Gain gain={0.4} />;
return (
<AudioGraph>
<Aggregation>
{gain}
<StereoPanner pan={0.2} />
{gain}
</Aggregation>
{gain}
</AudioGraph>
); This will render a single Perhaps for readability, I would consider introducing a <Circular>
{gain}
<StereoPanner />
</Circular> This would be analogous to the above example using the |
The most common scenario for this is a delay with feedback, often with gain and/or a filter applied before feeding back to the input of the delay, but there are more complex setups too.
Ideally, the solution is not named inputs and outputs, e.g.
<Delay name=”d”/><Gain output=”d”/>
, at least I personally consider string references a design failure in pretty much every scenario due to creating a non-(trivially-)verifiable namespace and an easy error surface, e.g. seeref
in React.The text was updated successfully, but these errors were encountered: