…it remains on. It is on even if it is turned off in the Master bus. To turn it off the user must remove it from the insert slot. Correct?
Assuming I have this correct, I want to ask a question that involves how a Cubase option operates use of the plugins - specifically the Cubase option to turn off a plugin when it is not in use.
Not to suggest I understand this operation completely, however I will say that it is something that many Cubase uses employ, myself included. It just makes CPU usage sense. Well, until it doesn’t.
My Q: Let’s say I have a event that is dropped into a track in Cubase, and let’s say it is 0db right from the gate - the wave file plays immediately, in other words. Is it possible that the plugin(s) that might be on the inserts of this track will fail to start quickly enough during a Cubase mixdown session - to a point where the first millesecond(s) of the wave file are not reproduced acurately? In fact, might this plugin ‘off/on’ process produce ‘false/inacurate’ artifacts at the start of the wave file?
Not really. In WL you can either bypass or switch off a plugin in the same way as you can in Cubase / Nuendo. In other words, you don’t have to remove a plugin to switch it off.
Not sure i understand how this relates to your previous question about the on/off status. Is this simply a different unrelated question or do you mean for a plugin that has been turned off?
P.S. by the way, sounds like this is a question for the Cubase forum rather than Wavelab.
Stingray, hi. I was hoping PG would respond to my question. This said, as I have understood it, what you say regarding WL and the plugins on the Master bus, the loaded plugins are not turned off when put into the bypass mode. The plugins remain on, just bypassed, and this is not what you said. You said: “In other words you don’t have to remove a plugin to switch it off.”
Now, in Cubase, there’s an option in Preferences to “Suspend VST 3 plug-in processing when no audio signals are received.” Read that sentence a few times, please. To me, that means that in Cubase - if “Suspend VST 3 plug-in processing when no signals are received” means that (in Cubase) if you choose this option in Cubase Preferences, then the plugin is perhaps actually turned ‘off’ until a signal is received. How do you interpret the word ‘suspend’ in this context?
So my question (directed at PG mainly), is asking whether he thinks this “suspend VST 3 plug-in processing” action in Cubase (something he DOES NOT promote in WL), is causing a problem - that might become apparent - when a Cubase project is mixed in Cubase and then brought into WL for final editing. I’m asking this because I think I am experiencing a problem by clicking this box in Cubase.
Hi PG. Yes, I understand this ‘2 methods/2 different results’ of switching options in the WL plugin slots. And I am starting to appreciate why WL is like this.
I know you have Cubase there (in the lab?), but what can you tell me about the Cubase option "Suspend VST 3 plug-in processing when no audio signals are received’? Is this a ‘turning off the plug-in/plugin slot’ when no audio event is playing in the track? And if this is the case, does this option turn on the plug-in the exact moment the program sees audio?
If this is true, then I think there is some opportunity to alter the beginning of the resultant audio as it is suddenly taken out of ‘suspended’ mode. Am I wrong to think this, PG?
Well, that is similar but not identical to the Cubase program. However, the cubase program does not offer any timing variables, only “Suspend VST 3 plug-in processing…etc.”
I am hearing something wrong in the Cubase mixdown as I open it in WL and it centers not on all parts, but on parts where I have edited the original part such that - after complete silence - it has a loud entrance into the part. Do you understand what I am saying?
My PC is powerful enough that I can uncheck this “Supend…” box in Cubase and keep all my mixdown plugins active all the time. In the days ahead I will do more mixdowns and open these in WL to see if my mixes are different using the same tracks that have caused me concern. I was hoping you had some insight, yes, and perhaps confirmation that this Cubase option (which, as best as I can understand, is trying to save CPU) is something that should be avoided at mixdown. Thanks for the response, PG.
