That’s pretty cool. I’m not trying to hijack this thread (fat chance!), but do want to point out that there are four or more different devs that support a common clipboard format for sequence data. So you can copy from Squinky Labs, Impromptu, Entrian and Aria and paste the same data into emacs Here’s the spec: https://github.com/squinkylabs/SquinkyVCV/blob/main/docs/clipboard-format.md
This is more about having alternate ways of dealing with strips. I’m not, myself, much of a generative/sequence sort of guy. I mainly patch stuff to stick on the end of MIDI keyboards.
I’m afraid just generating strips/patches with scripting could hardly give you meaningful connections. Cables might go into any port, but most modules don’t work well with unexpected types of signals, some ports wants gates, some cv, some audio etc. It is interesting to go against this from time-to-time, but mostly it just results in silence/noise.
So a generator would either need explicit knowledge about which ports expect what, or intuition based on prior examples, which could come from machine learning techniques.
Definitely, didn’t mean to discourage any sort of development in this direction! For me though, the exciting part of a generator like this isn’t that it’d give me random patches based on the 20 modules I use all the time already.
Anyway, it would be nice if ports could be configured/labeled like params (sort of coming), but with the addition to specify what type of port it is. I think this would be useful in general, not only in terms of a patch generator. A lot of us are already using some type of visual clue to distinguish between triggers/cv/audio maybe even v/oct.