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
Hi,
I'm loving Cmajor so far as it removes much of the "boilerplate" and repetitive patterns involved in setting up a typical audio processing project.
With that in mind, I found the documentation a little thin on certain types of connections. What I've found is that connections to a node without an explicit input or output member referenced are only possible for nodes that have exactly one input and/or output?
I would like to propose a feature that aligns with existing library convention and typical shorthand usecases nicely: nodes referenced in a connection should default to the first port (if only one exists) otherwise should seek a port called simply "in" or "out"
This would allow for example chaining a four pole filter out of one pole nodes in a single expression:
// node A, B, C, D are std library onepole filters
connection in -> A -> B -> C -> D -> out;
I hope that makes some sense and I don't think conflicts with any existing features or cases.
The text was updated successfully, but these errors were encountered:
Hi,
I'm loving Cmajor so far as it removes much of the "boilerplate" and repetitive patterns involved in setting up a typical audio processing project.
With that in mind, I found the documentation a little thin on certain types of connections. What I've found is that connections to a node without an explicit input or output member referenced are only possible for nodes that have exactly one input and/or output?
I would like to propose a feature that aligns with existing library convention and typical shorthand usecases nicely: nodes referenced in a connection should default to the first port (if only one exists) otherwise should seek a port called simply "in" or "out"
This would allow for example chaining a four pole filter out of one pole nodes in a single expression:
// node A, B, C, D are std library onepole filters
connection in -> A -> B -> C -> D -> out;
I hope that makes some sense and I don't think conflicts with any existing features or cases.
The text was updated successfully, but these errors were encountered: