My team and I are running into a continuous issue with batch processors that contain Waves plugins. Each time the Waves plugins are updated, we need to rebuild the batch processors, on each individual machine, otherwise the Batch Processor will not “run” nor will the GUI for the plugin open. There are no error codes when this happens, just an absence of activity. It is not sufficient to build the new processors on one machine and distribute the .batproc files to other users. When opening the .batproc file in this manner, the result is the same as when using the older batch processor. A completely new batch processor has to be rebuilt on each machine. Any advice as to what is happening here and how to prevent each user from needing to do this work on a per update basis?
For what it’s worth, the icons next to the plugins in the batch processor plugin chain are different between the working plugins and the unresponsive plugins. The working plugins have 3 diagonal lines, whereas the unresponsive ones have another symbol shown here, I think master-pass plugin? I have not been able to find out what these mean in the documentation.
Hi!
I think the III diagonal sign is the VST 3 plugins
and the -box- symbol is plugins in the Master Section
regards S-EH
I don’t know what the problem origin is, but in all cases, use VST3 plugins and avoid VST2 plugins.
Ok, I’m pretty sure the change wasn’t from VST2 to VST3, it was just from Waves V14 to Waves V15. And V13 to V14 when that happened.
Forcing plug-ing detection did allow me to open the plug-ins! I’m wondering if Wavelab is trying to reference some version of the plug-in that is incompatible? As if the batch processor is just reaching for the first available plug-in version, and only when re-scanning is it able to link the most current version of the plug-ins. Does the Batch Processor contain information regarding which version of a plug-in to run? This is only happening with Waves, by the way, so perhaps it’s something to do with Waveshell or how they handle updates. I would think references to plug-ins in the Batch Processors should continue to work when updating the plug-ins themselves.
Not at all. Each plugin has a unique ID assigned by the manufacturer, which remains unchanged over time. This is how WaveLab identifies a given plugin. The only thing I can think of is that Waves makes non-compatible presets from one version to the other, but this would be very strange. And I never heard about that before.