BrainModular

one thing i would love to be able to do and would be awesome powerful, is to dinamically recall some wirings.
ie i dlike to chain several vsts constantly used . ie A->B->C, then later use another combinaison A->C->B

i can send IML message to wire the stuff, but im facing two problems:

_with iml, there is a risk to create multiple wires and they add together (any protection possible?)
_actually i need to keep a complex tracking of each wiring to unwire before rewiring a new schema.

this lead me to another idea that would simplify a lot:

if we could destruct all wires from a module (ie vst) or ask to destruct all wires connected ie to cut off pin only, i could
clean the stuff then make the new wiring very easily.

globally some reflexion about recalling differents wiring snaphots could be awesome, don't know what you think about that,
probably hard, but never know..

edit mmmm i just thought i could use busses and control their name in most cases, but im thinking a bout a case where
i dlike to freely assign lane of automations (curves modules) to differents vst params, and i feel controlling all via iml is not recommended, and i would like to avoid creating one buss per param, best seems to make some script that wire/unwire
the stuff..

+1 on on some sort of wiring snapshot ability. An option within a preset manager to include wiring within a patch (or something along these lines) would be friggin amazing!
23fx23, I've done some patch bay style routing using busses and it works quite well, the only issue being the one bloc of latency for each buss in a multiprocessing environment. This adds up to phase issues.

It would be nicest to do it without wires at all sort of buss style, some sort of list based routing system that automagicly detected names of VST's and available audio i/o for the VST would be

yeah, i remember one of your patch based on buses. one trick already possible is to create busses and remote their name via combo boxes, then the preset manager can recall differents virtual links as recalling different combo nbers. it can also recall text
of pttextfield to be used as bus name.

but the 'physical' wiring is interesting too: cost less cpu, no latency, visual representation. in my cases, this wouldn't apply only to audio pins only but any pin,ie to link a lfo to different params over time, and also route audio differently too for exemple,
but you give me an idea, im pretty sure a script coud already scan for audio pin and auto wire some bus, then rename the bus..

maybe dreaming too much but indeed some kind of preset manager for wiring: at some point we store a wiring. then we change,
make a new one and store to a new nb.

i suppose this must be hard to implement, that's why i emitted the 'simpler' idea of killing all wires of a module or specified pin on a module, then via iml it is easy to rewire safely.

tons of ideas in my head... but really excited by my new usine setup.
i already have a workaround idea: create dummy simple a+b modules and name them via IML, then it's possible to delete them
to kill the actual wiring, then recreate some and rewire. but i feel it's not really fast and cpu effective for lot's of wiring..

Whao I have to say that if this is some day possible, I will use it a lot ! Just the idea to be able to change wiring and recall it is amazing !

Well there is always 'load patch'.

I had to take it out of my setup tho, because it was too slow.

In the next version 5.50.62 and above, the CREATE_LINK and DELETE_LINK will be protected: it will be impossible to create 2 links between the same inlets with the IML.
I think it will simplify your pb.

I'll put the DELETE_ALL function somewhere in my TODO list but it's, unfortunately, a top priority.