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.
@c_reider @elifyalvac are these overdubs freeform/async? Or -- if rhythmic -- are you syncing by eye/ear?
@ghostmeet @elifyalvac the latter by ear as everything
@c_reider @elifyalvac nice, can't fault.
@ghostmeet @c_reider Nice to wake up to this thread ha! I agree on separate patch recording to separate channels. also, just to remind, Cardinal can also be good. I will report on that
@elifyalvac @c_reider oh right, Cardinal, I forgot all about that! Please do report back :)
@elifyalvac @c_reider Couple of questions: Do you both use Phasors in VCV? And platform: are you using Mac ARM or Mac intel -- or windows/linux? Curious about this re:performance but also wondering if you'd be up for trying a Phasor module I'm building? Would love some feedback when it's ready. If not, no worries :)
@ghostmeet @elifyalvac i’ve only just recently adopted phasors, switching from clock generators due to Hetrick’s robust set of modules. i’m on mac intel… at least on desktop, i think the macbook is intel as well
@c_reider @elifyalvac similar to my situation, only got into phasors recently. Hetrick's stuff is v good. I just need a module that divides the phasor into steps and let's me reorder the steps, resize them, shape them etc. So like the Hetrick sub-step shaper/phasor randomizer, but with more control. I could try and make a version that'll run on intel (I'll try just for fun, anyway).
@ghostmeet @elifyalvac like a step sequencer for steps? 🤣
@c_reider @elifyalvac when you put it like that... :)
@ghostmeet I checked out those hetrick modules and phasors literally after I saw @c_reider writing about them here. I am on a macbook air with m4. Haven’t delved further into phasors yet. I am also fortunate to work in a place where I am teaching synthesis, including using a studio with roland and buchla at times ☺️
@ghostmeet @c_reider overall, been happy with it but it could be because my laptop is new, or has been new. For many MANY years I had to use very old laptops. Had to always keep things limited, not just vcv, but also with Max.
@ghostmeet @elifyalvac (btw, just got on the laptop and checked - yeah, it's intel as well.)