MarcBoule
commented
4 years ago Hi Artem, it's quite interesting, I'll have to think about all this, but it might indeed fit better than the expnder mechanism. I'm hesitant to implement clock linking through expander mechanism, because it starts getting more abstract to see what's going on behind the scenes, and it's not 100% in the modular philosophy. When I read this from Andrew:
it kind of convinced me that a whole bunch of hidden expander features is not fully in the spirit of the expander concept, and your autoconnect macro seems perhaps better, in the sense that the modules can be anywhere, and we still see the cables, which is a good thing I believe, given the paradigm we are aiming to replicate in a virtual modular.
So I think I'll close issue #11 and keep this one here open, as it seems to fit better with the way I see things. Thanks for your thoughts as always!
vcvrackideas
Eurikon
Hi Marc! I'm still thinking on how to merge all clocked modules in VCV Rack and maybe I have anyhow decent idea) So I usually start a patch with one CLKD module and when I need more dividers I just add another clkd and make three connections and then do a reset on the first one. So I'd to suggest do these three connections and reset just in one macros like function - right click on the first module and press something like "make this instance master". So it also (if possible) can apply to other multiple instance of CLKD when for example we're loading strips that have clkd inside and then this function can make those 3 connections from a master to all of these modules at the one click. It maybe even better than expected expander ability and actually I've got an idea from Seq++ which can hook up connections from clkd and than multiply one of the divider by 4. So technically it seems that possible but who knows, interesting what do you think about it?) Cheers!