What problem does this solve?
I absolutely love this program, but this feature not existing blocks my main use case for it right now as there's no way to neatly organize tons of nodes and toggle them on and off.
There's a lot of use cases I have for toggling on/off nodes, but one of those is building my own voice changers for characters. I voice act as a bunch of characters either goofing off, doing actual voice acting for people's projects, or playing live-action roleplay games with friends where being able to toggle effects via a keybind would be the most helpful.
If you've ever played Dungeons and Dragons for instance, say you have to voice a troll while you're in a voice chat with the other party members. It'd be far more immersive if you could easily slap on a voice changer when you talk as the character, and it'd help people distinguish between the characters.
Proposed solution
I think this could come as two different features: Graphs and key inputs
Being able to group up together nodes inside a graph would be very useful just in general for any complex pipelines as nodes get messy, and having a graph system of sorts like Cantabile would be nice for organizing nodes while also allowing users to add their own separate named input/output ports on the graph.
You could have a trigger input/output that just sends a very quick burst from a node. Like the execute pin in Unreal Engine that just triggers whatever is hooked to it.
A key input node could let you select a keyboard keybind or a MIDI event, and it could output a trigger signal off the right end that other nodes can take as an input.
For instance, groups/graphs and other nodes could have an input for the power (the on/off button on nodes currently), and this would allow for keybinds to toggle nodes
You would probably need to think this through a bit as you can go either as simple or as advanced as possible when it comes to solving this problem. You could have the trigger signal simply toggle a node when its fed into the power input, or you could go all the way in and add conditionals and state to the pipelines. Stuff like an if node, a toggle node that keeps its own state and reacts to a trigger signal to flip it, etc.
Alternatives considered
There is no tool that can do what Splitwave can, that has even a barebones version of the features I mentioned.
I've been looking absolutely everywhere for months now. The closest option is Cantabile, but it's proprietary and the only way to use keybinds to toggle a node group/graph is to pay $200 for a license.
Additional context
There's a lot of details I've left out as I'm not sure how you'd prefer to structure a system like this, but these two features would be extremely useful for me and I appreciate if you can consider implementing them whenever you have time!
I'm familiar with Rust and Svelte, however I'm not familiar at all with the hardware/technical side of audio and I don't have much free time so I'm not sure to what extent I could help.
What problem does this solve?
I absolutely love this program, but this feature not existing blocks my main use case for it right now as there's no way to neatly organize tons of nodes and toggle them on and off.
There's a lot of use cases I have for toggling on/off nodes, but one of those is building my own voice changers for characters. I voice act as a bunch of characters either goofing off, doing actual voice acting for people's projects, or playing live-action roleplay games with friends where being able to toggle effects via a keybind would be the most helpful.
If you've ever played Dungeons and Dragons for instance, say you have to voice a troll while you're in a voice chat with the other party members. It'd be far more immersive if you could easily slap on a voice changer when you talk as the character, and it'd help people distinguish between the characters.
Proposed solution
I think this could come as two different features: Graphs and key inputs
Being able to group up together nodes inside a graph would be very useful just in general for any complex pipelines as nodes get messy, and having a graph system of sorts like Cantabile would be nice for organizing nodes while also allowing users to add their own separate named input/output ports on the graph.
You could have a trigger input/output that just sends a very quick burst from a node. Like the execute pin in Unreal Engine that just triggers whatever is hooked to it.
A key input node could let you select a keyboard keybind or a MIDI event, and it could output a trigger signal off the right end that other nodes can take as an input.
For instance, groups/graphs and other nodes could have an input for the power (the on/off button on nodes currently), and this would allow for keybinds to toggle nodes
You would probably need to think this through a bit as you can go either as simple or as advanced as possible when it comes to solving this problem. You could have the trigger signal simply toggle a node when its fed into the power input, or you could go all the way in and add conditionals and state to the pipelines. Stuff like an
ifnode, atogglenode that keeps its own state and reacts to a trigger signal to flip it, etc.Alternatives considered
There is no tool that can do what Splitwave can, that has even a barebones version of the features I mentioned.
I've been looking absolutely everywhere for months now. The closest option is Cantabile, but it's proprietary and the only way to use keybinds to toggle a node group/graph is to pay $200 for a license.
Additional context
There's a lot of details I've left out as I'm not sure how you'd prefer to structure a system like this, but these two features would be extremely useful for me and I appreciate if you can consider implementing them whenever you have time!
I'm familiar with Rust and Svelte, however I'm not familiar at all with the hardware/technical side of audio and I don't have much free time so I'm not sure to what extent I could help.