Questions & Answers

Can we have "Dynamic Plug-in Processing" like in Pro Tools?

+59 votes
asked Mar 24, 2016 in Studio One Feature Requests by stevekitch (1,340 points)

Plugins seem to take up CPU power regardless if there is any audio passing through. This can mean resources quickly get used up. Pro Tools has a great feature called "Dynamic Plug-in Processing". When audio is being processed by the plug-in, it uses CPU power as it normally would. But when no audio is being processed by the plug-in, it ceases to use CPU power. That CPU power can then be allocated to another plug-in or process as needed. The result is much higher CPU efficiency for the system. Large sessions take up much less juice than when using Studio One. This is the only thing keeping me with Pro Tools. 

6 Answers

+7 votes
answered Mar 24, 2016 by justincrosby (1,880 points)
Agreed. Also CPU usage is pretty inefficient in Studio One when compared to Logic. It hit the CPU wall waaaay faster is S One than in LPX.... There has got to be a way to make Studio One more CPU efficient.
0 votes
answered Mar 26, 2016 by niles (54,510 points)
edited Mar 26, 2016 by niles
Is this request for VST2? Since VST3 already (should) do(es) it.
+7 votes
answered Mar 26, 2016 by stevekitch (1,340 points)
VST3 is capable of this. But Studio One doesn't utilise it.
+3 votes
answered Mar 28, 2016 by niles (54,510 points)

stevekitch answer If the plugin developer implemented it in the VST3 version, I doubt Studio One has any control over it. Try the VST3 version of Saturation Knob by Softube, for instance. It will neatly stop processing when there's no signal. Unfortunately most developers did not implement this feature in their VST3's (yet).

+4 votes
answered Aug 29, 2016 by stevekitch (1,340 points)
VST3 does support it but S1 doesn't. Reaper does it very well. If no audio is passing through a track then no CPU is being used.
+1 vote
answered Feb 8, 2020 by jstalcup (3,640 points)
I'm all for reducing DSP use and having S1 be as efficient as possible in using resources, but care needs to be taken with comparing the behavior of AAX plugins to VST and VST3 plugins. I wouldn't be surprised if there aren't some optimizations that Presonus could do for VST3 plugins, but the fact of the matter is that the vast majority of CPU use by plugins is a result of the plugin software sending instructions to the DSP/CPU.

From what I've observed Studio One's Performance Monitor is not measuring real CPU utilization (at least on Windows 10) or disc I/O for that matter. I assume that it is some measure of how much of the DAW's DSP has been consumed.

When you load certain plugins (I'm looking at you Waves Abbey Road reverbs) they consume a bunch of S1 "CPU" just idling. As an iZotope user, I know for a fact that S1 "CPU" use dropped significantly when the latest versions of Neutron & Ozone were released.

I'm all for Presonus implementing as much of the VST3 protocol as they can - just as long as it doesn't break anything - and we should continue to demand that they do so. That said, just keep in mind that AVID uses a proprietary protocol for their plugins, AAX, and can enforce how it works, while Presonus has to support VST and VST3 protocols that they don't control.