c.reider 
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.
:(((((
Elif Yalvac@c_reider vcv issues?
@elifyalvac almost always! :D
ghostmeet@c_reider @elifyalvac I forgot you were using VCV -- I'm into it for the last few months and I'm pushing the CPU all the time. On a M1 Max here. I turn off everything I can, including wifi, and it improves but there are some modules that could do with optimizing for cpu.
I've been building modules this past week (using Claude), btw. It's a blast :) Now I'm building a phasor addressor (don't know if you're using phasors).
@c_reider @elifyalvac I also use Claude to check for patch optimizations, to reduce CPU.
@c_reider @elifyalvac One idea I had to reduce patch CPU was to kind of distribute the modules across 2 or more patches, and run multiple VCV instances inside Reaper, with signals sent across channels. It's not ideal but opens up some possibilities (including lots of crashes :) )
@ghostmeet @elifyalvac i've never actually used it in Reaper before, i always end up recording a mixdown and then doing overdubs later in Reaper.
one thing i have done is just split up a patch into two and record them separately - a super-goofy fix, but it works sometimes.
one thing i have done is just split up a patch into two and record them separately - a super-goofy fix, but it works sometimes.
@c_reider @elifyalvac :) fwiw I found VCV performance a little better when hosted in Reaper, even a single instance/one channel.