![]() If the 1048 samples buffer you mention actually was added to your real time performance, then it would be high latency and not low latency. If it worked the way you seem to think i does, then you should be able to run CPU hungry applications on bad CPUs. That's why i ask the OP about that in my previous post in this thread. I'm afraid you are misunderstanding the so called Drop out Protection system. Your problem is'nt about Pigments but about Studio One. Quote from: cseder on July 19, 2019, 01:11:10 am I also have some annoyingly high CPU usage numbers when using Pigments in Studio One 4.5 Professional. Now I mostly use Pigments in Stand-Alone mode for playing around, which is a shame, as I hoped this would be my new go-to synth for most things. It's gotten to a point where I rather load a different synth when using Studio One, because Pigments is such a rude boy. Something fishy going on with the VST/AU versions. Using Pigments in Stand-Alone mode demands around 20% CPU at most, even with the heaviest patches loaded. Using a simple patch helps a little, but hey, I have other synths for that! The default patch that loads when Pigments activate ("Synthwave Reverses") totally makes my CPU catch fire. I've tried using both the AU and the VST3 versions of Pigments, but same result. ![]() I manage to get by with turning off the Studio One "Native Low Latency" feature when I'm using Pigments, but it would be nice if it behaved like my other synth plugins, as turning off this feature means I'll also have to change my audio interface block size to keep getting low latency which is a PITA in the middle of a session. This works fine with most other plugins, but Pigments in particular makes the CPU meter jump around and spikes all the time with this setting enabled, causing crackles and pops. This gives Pigments its own process with a 1024k block-size, and I'm using 44.1kHz and some times 48kHz sampling with 24 bit-depth, 64bit processing on a modern MacBook Pro (Intel i7). S1 has this functionality that it gives plugins a separate process with separate block-size settings for instruments and audio while still managing to keep the latency low. I also have some annoyingly high CPU usage numbers when using Pigments in Studio One 4.5 Professional.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |