No I was just programming a patch that happens to really push Pigments' CPU. I wasn't even paying attention to the CPU at the time. It wasn't intentional but does provide a good test of how far Pigments' performance can be pushed.tactile_coast wrote: ↑Sun May 02, 2021 10:18 amThe Teksonic patch uses 512 Partials four times the stated safe CPU maximum. Presumably Teksonic created it to test the extremes of different configurations in handling the new engine. It doesn't in any way reflect on the general performance of Pigments as it falls far outside of the designated operational parameters.
Yes that's an extreme example but I stand by my opinion that Pigments could use some optimizations. It's far more CPU hungry than most other plugins I own. Diversion or luSH101 pushed hard may be the exceptions.
I do like Pigments a lot but like I said I won't be using multiple instances of it like I do with Hive 2 or DUNE 3. My studio system will run any patch I've done for Pigments but when it's eating 50% of the Audio Buffer in one patch it's hard to justify opening another instance.
I was watching a video by JunkieXL and he was talking about Arturia's Buchla plugin and said he could only use one instance of it due to the CPU demand and I assume he's using a pretty powerful system. So apparently Pigments is not the only demanding synth in the Arturia lineup.