Love this plugin, but what is up with the CPU usage? No lag issues or anything of the sorts…. But the second I start playing a chord or using one of the preset chord patterns my Ableton CPU usage skyrockets from 2 - 3% to roughyl 20% immediately upon opening, than once I actually play notes I have already had a case where it skyrocketed to nearly 50% on my home machine and legit made an Ableton project un-openable due to it just immediately crashing.
I struggle to believe the issue is my PC as this is legit the only plugin which does this… I can have 5 instances of pigments running and STILL not have this much CPU usage.
Windows 11
Ableton Live 12.3
AMD Ryzen 7 7700X 8-Core Processor
16GB Memory.
There is maybe something up with Notes on your system….we did a check against Pigments, Current and Serum 2 using 8 voices and similar patches ( two multisample engines, analog filter, reverb…)
One thing that is heavy is that on some preset we have a high number of default available voices. This means that say you strum a chord, it can end up triggering 12 or 16 voices…this means its like having 4 Pigments running at the same time.
This is Pigments with the 8 voices ( poly 8) and a single wavetable oscillator turned on, analog filter and basic modulation setup playing 5 voices…
Can you do a similar test on your system and if Pigments and Notes are wildly different, then it means something is up with Notes and how it runs on your system….really appreciate the help if you have time to check for us!
Thank you for the fast reply, absolutely love the plugin and see myself using this daily. It seems to be performing a little bit better today with usage maxing out at 28% on my work machine. Again, this seems to be the only plugin that I notice this behavior which is why I brought it up. On my work machine, my usage typically runs between 3-12% when I am actually using the VSTs depending on what specific ones I am using. Notes comes out of the gate at 18% immediately and goes up to 30%.
12th Gen Intel(R) Core™ i7-1265U (1.80 GHz) - (I can understand this processor not liking the plugin as much, I overexaggerated when I said I could run 5 instances on the work machine, I cannot do so. My apologies.
AMD Ryzen 7 7700X 8-Core Processor (4.50 GHz)
Hopefully that helps. Also the lazer effect that was added here is dope!
It was a little bit worse on my 12th gen i7 actually with it peaking at sometimes up to 50%, I will say in the latest update my CPU usage now hovers between 8-20% so there is definitely some improvement. That is on my intel machine, am not home to test the AMD machine.
Nevermind I lied. It just froze my entire machine while using the WurliFlute preset with some more effects added on. Not sure what could be causing this, legit no other plugin does this on my machines……. This is the ONLY VST I have this issue with, I love the plugin, I really do and have zero intentions on trying to return, but this is getting out of hand…… I dont have this issue with SubLab XL and I never had this issue with Circle either…..
The issue lies somewhere in how you guys are implementing the effects… Turning off just the vintage effect brings it down to about 30% CPU usage….
What’s going on with the vintage effect is that it is using impulse responses from actual hardware. Internally, it does some fancy maths to apply the impulse responses. The fancy math is tuned to work on specific processors, but if your setup doesn’t work with the fancy tuned math, then it falls back on something slower. I think this is what is happening here.
I’m going through the vintage effect again and trying to make sure that the fast version is actually working properly….hang in there @kory !
