of course i had to add *just one more part* to this patch and now it's spiking the cpu.

looking for places to trim it up and... not finding.

:(((((

always pushing this shit right to the edge
ok, found a way to delete a couple of modules, now getting max at 89% cpu, which i can live with. i think i hear some clickies though, which is grumblesome.
@c_reider Nice :) Does anything improve if you focus on an empty area of the rack, no modules in view? I swear this helped me once but I can't reproduce it. Not ideal, in any case.
@ghostmeet no, i've never had that experience. usually high load patches, if they're not spiking sometimes will spike with zoom ins/outs

@c_reider 🤔 I wonder why. If only VCV wasn't so conceptually tethered to eurorack representation. I'd love to make it vanilla, Reaktor ca. 2004. But then I could just get into Max. Probably kinder on CPU too.

Also, fyi, a huge part of the CPU problem on my side is that I'm using VCV Host, so I can run VST's in a patch. V expensive.