[feature suggestion] wiring UI modules in Workspace

[x.iso]

I don't know if it's going to be possible, but it would be cool and useful to have wiring modules that display in/out 'jack' in UI that can be wired to other same type of module, thus simplifying otherwise complex on demand routing between patches in same or different racks.

I understand that it would be bothersome to have wires hanging in UI obstructing other UI elements, so perhaps there should be a switch to see wires and manipulate them, and then hide when they're not needed.

Maybe we can also make patch-specific route module, that can't be routed to anything beyond the patch itself or parent patches, and could have wires always visible.

This sure could bring a lot of modular synth lovers to Usine (although proper CV support may have to follow, to make it blend with hardware routing). Some already are here I suppose.

[gurulogic]

For me it seems there is already lots of ways to set routings from the ui , ie: matrix, combobox or even iml for realtime manipulation of patch wiring but I could see maybe some sort of combo patch / interface mode could be useful in some cases.

[sephult]

Although the visual cable element might not be there, you could always develop a multi-modulation selector for your controls.
I've done this with some synths I've built in the past. You can use selectors and quicklinks, or busses to do this.

Using a bus, you can also pull in the bus name list and select the name to feed the bus. This allows say....for a frequency input to be selectable by either LFO1, LFO2, ENV, OSC2, etc...
Still the same concept of multi-modulation sources...yes more cumbersome than just thinking a wire on the UI...but still all of that same logic will still have to reside under the hood....
More people use the buses and quicklinks and provide bug-reports and suggestions might spark more of a priority-cue to update and evolve this type of thing quicker. dunno.

Hope that helps some...I am the same way...I am used to patching everything...

-s

[x.iso]

Although the visual cable element might not be there, you could always develop a multi-modulation selector for your controls.
I've done this with some synths I've built in the past. You can use selectors and quicklinks, or busses to do this.

Using a bus, you can also pull in the bus name list and select the name to feed the bus. This allows say....for a frequency input to be selectable by either LFO1, LFO2, ENV, OSC2, etc...
Still the same concept of multi-modulation sources...yes more cumbersome than just thinking a wire on the UI...but still all of that same logic will still have to reside under the hood....
More people use the buses and quicklinks and provide bug-reports and suggestions might spark more of a priority-cue to update and evolve this type of thing quicker. dunno.

Hope that helps some...I am the same way...I am used to patching everything...

-s

I use buses myself and pull the lists of buses to just select sources from combobox etc, it's just that there's no other option. But you have to admit, wiring directly makes things way easier and would allow for much quicker improvised rerouting in live performances.

Speaking of buses, I wonder why there's no basic patch for midi bus in and out in stock library. Had to make one for naming bus and sending there and one for receiving from list of buses. Sometimes it doesn't load properly though, so I have wrong bus selected after opening workspace.

[x.iso]

I have to say, there's just one thing that I don't know how to resolve with this idea. Grid integration could be tricky if there's no way to define wire routing change over time in Grid. I would think it can be solved with enabling automation record and each module would record it's own change. But that may require a different kind of automation, not a slope from 0 to 1, but something more similar to trigger sequence with different module names corresponding to what it was connected to. I may construct a patch or just make image later, on how it may look.

[senso]

humm, I think it's hard to implement like that.
I'm more thinking about a 'generalized bind system' using the powerful binds in Usine to do that.
it will be a long way...

[x.iso]

So, back to the original idea, Reaktor recently got similar feature - enabling I/O of the patches on the UI panel for wire-patching as in VCV Rack. This could be useful in Usine for top-level patch I/O, enabling wiring patches from rack to rack or in some peculiar round about way inside the rack.
Also similar idea realised with showing/hiding wires when needed.

[senso]

You'll have big surprises in HH4 about that...
I can't say more for the moment.

[drakh]

You'll have big surprises in HH4 about that...
I can't say more for the moment.

some more details.. ? release date will be enough for me ...

[x.iso]

You'll have big surprises in HH4 about that...
I can't say more for the moment.

Very glad to hear that! Hope I could get it before the end of summer