Possible to save patch cord connections when using pattrstorage and/or scripting?

Using [coll], maybe ?

(Edited)

Hmm. I'm still brand new to coll, so I'm probably misunderstanding. From what I can tell, this is allowing me to make connections with the radio button triggering the script. But what I want to be able to do is manually make my connections and then save those connections (maybe in a column in coll?) and then make a different manual connection and save that in a different column and then be able to toggle between them. Does that make sense? I'm guessing your soultion does that, but i'm just not understanding.

I'm guessing your solution does that, but i'm just not understanding.

No it doesn't. It assumes you have pre-defined every possible connections and call them on request.

By "manually" , I understand that you want to connect 2 objects with the mouse and then save the newly made connection "on the fly". That would imply that the information "inlet x of object A is connected to outlet y object B" is available somewhere. This I don't know.

Using Snapshots, may be an appropriate workaround ?

That would imply that the information "inlet x of object A is connected to outlet y object B" is available somewhere.

Yes. My hope is that I can perhaps I can do something like give every inlet and outlet a scripting name and then Save the connection state somehow to then be recalled later.

you could give any inlet and outlet of a patcher a unique ID...

...and combine that ID with the instance number of the patcher or bpatcher (not shown here)

then you run a global [qmetro 1234] somewhere which continuously triggers all the "outlets" in order to make them announce their idendity to all "inlets" connected to them and store all this info in a [coll] or [text] in order to script-create that whole patch next time.

you could give any inlet and outlet of a patcher a unique ID and combine that with the instance number of the patcher or bpatcher.

But I'm not sure how to translate that to being able to save that "outlet x is connected to inlet y".

you can store that info in any format you wish. all we need to know is "object name, object instance number, inlet number of this object" - and the same for the outlets.

every connection will be saved as one pair of these informations:

"myoscillator no_03 out_2 myfilter no_02 in_1"

the translation to the actual scripting commands can be done later, while you actually want to reassemble things.

be warned that it can get complicated to assign unique instance numbers to abstractions or bpatchers. the only half working solution i´ve found is that at runtime you start counting 1,2,3 for the first 3 oscillator bpatchers - and in case you remove the 2nd oscillator only #1 and #3 shall be left.

when you later use scripting to recreate what you got, you have to process the list of patches and connections alphabetically (as you can not do it from right to left as numbering will then follow right to left then instead of how it was before)

the system will cause a minor overhead as eveything else which goes throught the happy inlets has to cross some additional inlet objects as wel as 2 route objects.

Are your modules fixed in the patch, I mean they don't get inserted or removed

on the fly ?

Are your modules fixed in the patch, I mean they don't get inserted or removed on the fly ?

In an ideal world, I'd be able to add and remove modules on the fly, but that's outside the scope of this specific question, so I'm happy to keep a set number of modules. Still hoping to be able to save the different patch cords that have been manually connected in different ways, but I still don't understand how to do that.