Follow up
Ardour is said to show DSP as is, not doing anything internally to compensate / produce a lower value when plugins are not being used. From what I understand it is done this way so all of a sudden you do not get these spikes in DSP out of no where when many items are running at once in a song for example. So does that mean that plugins with this “bypass/enable control port” that kind of “bypass themselves” (without user having to click on bypass) are kind of undermining the approach Ardour uses in a way? For example if all VST3 plugins use this type of bypass, and the user used nothing but VST3 plugins in a project, then could those high DSP spike moments occur? Again not important I was just curious.
Thank you guys again for all the information shared in this post.
Consider the following case. You have reverb with long tail.
When you force the plugin to shut down processing, you won’t get this tail when turning bypass off because the plugin starts the processing only at the moment you turn bypass off.
By the way, it could be a good feature for Ardour to perform hard shutdown of the plugin instead of using bypass.
Yes. There are some heavy DSP plugins that do not need to be running during recording and other work, but are necessary for the project. Reverbs, compressors, delays, eq’s and other effects that are needed on the final mix, but not while working on the project.
It would be very helpful to be able to left-click a plugin and select hard bypass. The the plugin could be greyed out with red lettering to show it is hard bypassed.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.