Yes - I am struggling a little bit with the JITLib paradigm. Since it requires new nodes and buses for recursive patching, it ends up being a bit unwieldy.
This recent thread demonstrates how much can end up going into branching off from a synthesizer patch, in order to work within NodeProxy:
Isolating parts of nodeproxy
If you start to think about managing that many NodeProxies for a big, integrated modular system, where they are branching off in many different directions - it’s hard to imagine a good way to keep them organized or visualized.
The JITModular approach seems to offer a different workflow - but I’m curious about how one would handle something like:
~osc <>> ~osc <>> ~osc <>> ~out;
…where the first ~osc and the last oscillator are the “same” and the second is a different modulator.
All of these problems can be coded around, I’m sure - it’s easy enough to do any of these things as isolated functions or one-off SynthDefs., but I don’t know what the best practice would be, in making a fluid, integrated modular system and I would imagine this is the kind of problem that has been solved many times over.