Hi,
I run Patchwork and add Acustica Audio Nebula 4 VST instances to build up to about 4 instances of N4 in a rack style config. In Reaper it works a treat but have just tried on Studio One and every time I turn knobs on my Nebula interface hosted in Patchwork, the audio glitches quite badly, also a delay in sound of about a second. I am just running one track with a drum loop and one instance of Patchwork with 4 x Nebula instances (its with TimP Surge EQ library which does have high latency I guess?). If I dont use patchwork and just load 4 x instances of Nebula it works as intended. Is this issue with Studio One? I am on Windows 10 and have been producing music for years so PC optimized as expected. Steinberg UR824 running at 1024 samples so that shouldnt be a problem. Cheers!
Patchwork in Studio One Pro4 glitchy compared to Reaper
-
- KVRist
- 217 posts since 12 Jan, 2017 from England
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981 - KVRAF
- 6349 posts since 8 Sep, 2004 from Paris (France)
This could be due to the way Studio One handles parameter changes, since you have all 4 instances inside a single plug-in (PatchWork). Have you also tried to disable undo in PatchWork for the Nebula instances? Maybe it can help.
-
Blue Cat Audio Blue Cat Audio https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=39981
- KVRAF
- 6349 posts since 8 Sep, 2004 from Paris (France)
Another thing you may want to try is to use the VST2 or VST3 version of PatchWork instead of the other. Hosts may behave very differently with different plug-in formats.
-
- KVRist
- Topic Starter
- 217 posts since 12 Jan, 2017 from England
Great, thanks for tips. Will report back
-
- KVRian
- 632 posts since 1 Jul, 2007 from over there
Studio One multi core prosscessing is not that great. S1 is likely using only one CPU. Reaper is better at this than S1. Is your CPU meter maxing out in S1?
-
- KVRist
- Topic Starter
- 217 posts since 12 Jan, 2017 from England
Yeah it was big CPU spikes every time I changed a parameter of the plugin that caused glitching. Disabling Track Undo in preferences as stated above totally fixed it though. Thank you!
(Didn't notice any difference in performance between VST2 and VST3 prior to this btw)
(Didn't notice any difference in performance between VST2 and VST3 prior to this btw)