• SONAR
  • Problem with "all" WAVES plugins (Plugin Load Balancing ??)
2016/10/10 05:01:00
THambrecht
Since I have updated to SONAR 2016.09 "ALL" plugins from Waves (V9 R18) no longer work. All 64-Bit VST3.
For example the meters from L3 oder ZNoise work - but there is no difference wheter they are bypassed or not.
I know this is an old version. We are working on a large digitization project over years. Therefore we want to have the same version of all plugins in all projectfiles. (Q10, ZNoise, L3, MV2). Different versions in the projects might cause problems.
Usually the old version of this plugins should never be the problem. Something in Sonar 2016.07 to 2016.09 must have changed  (Plugin Load Balancing ??).
 
Is there a general problem with Sonar and Waves? I don't want to spent money for newer plugins from Waves, if there is a general problem with Sonar and Waves. There is also the problem that the plugins lose their settings if they were moved from track to track.
I never had such problems with other manufactures. If Waves is an ongoing problem I will replace Waves plugins in future projects.
2016/10/10 05:39:17
The Grim
no help to you i know, but i have used sonar platinum a fair bit over the last weekend, and have had no issues wioth any waves plugins i have used, both with the latest update 1 release and it's previous 'parent' release of sonar platinum.
2016/10/10 06:32:58
Zargg
Hi. How did you install the Waves plugins? Did you use Waves Central, or separate installers? Have you tried to do a vst reset and rescan?
I have the latest SONAR Platinum, latest Mercury bundle, and do not have any issues with load balancing. It is working great here.
Did you update to the latest release? http://forum.cakewalk.com/Update-1-for-SONAR-201609-is-now-available-m3495462.aspx
All the best.
2016/10/10 07:01:26
Noel Borthwick [Cakewalk]
Hmm are you seeing issues even with load balancing off? We havent seen any issues with waves plugins but we will double check. Which version of SONAR did you update from - were you running the 08 release earlier?
2016/10/10 08:13:02
THambrecht
The problem is exact the same on 2 PCs.
It does not matter if "load balancing" is off or on. Both do not work.
Version 2016.09 and version 2016.09 (UPDATE 1) don't work with Waves v9 R18.
Version 2016.08 is working with this Waves plugins.
Waves was installed over 2 years ago from a client, The Waves licences are provided and installed from this client and never touched.
For a test I have now installed 2 DEMO plugins (Q10) from Waves. This works very well.
  
Thus, it affects only the old version WAVES V9R18.
Because I need Waves licences on 3 computers it is unacceptable to buy Waves licences. Unlike iZotope where you may use the purchased plugins on multiple computers simultaneously - Waves needs 3 licences for 3 computers. And they are not inexpensive.
And I don't like it that you have to pay attention to the versions of Waves. When you open a project from a year ago there may be problems. Not so with the plugins from other manufactors.
2016/10/10 08:48:46
Rob[at]Sound-Rehab
Waves (V9 R18) is very old indeed. Apr 2014.
 
You can download and install later versions using WAVES Central. This does not affect licensing. If you have a valid license (e.g. USB dongle) WAEVS plugs continue working as before. I did the upgrade from R27 when I upgraded to win10 and had no problems with the upgrade (i.e. new installation of newer WAVES plugs)
2016/10/10 09:20:44
bitflipper
Just checked here...no problems with Waves on this machine (load balancing enabled, 64-bit, slightly newer version 9.6).
 
If you can backrev SONAR to .08 and the problem goes away, then that would indeed point to the latest SONAR update as having done something that Waves doesn't like. This is why I no longer use Waves products: their many layers of license protection make them overly fragile. I've had them abruptly stop working on three separate occasions for no obvious reason. Each time the problem was resolved via the "license recovery" option of the installer, so you might give that a try.
 
I couldn't check VST3, as I only use VST2 plugins. 
 
 
2016/10/10 09:27:56
THambrecht
Thank you. 
Than I have to talk with my customer because I do not own the licenses and I have not his Username for the WAVES central. The licenses are borrowed by the customer.
And the customer wants that all thousend of digitizations projects are in the old WAVES Version. because he is afraid of changing in sound when changing the version.
It is not about music, but about speech from tapes.
First - It must be determinded if there is any sound difference between versions.
Thank you.


2016/10/10 10:12:02
pinguinotuerto
Wouldn't it be easier to just roll SONAR back to the version that was working until you're done with this big project? Never a good idea to update in the middle of a big project. Especially if things are working well.
2016/10/10 10:25:16
bitflipper
First, a correction from my previous post where I said I use no VST3 plugins. I had a look, and this turns out to be untrue - unbeknownst to me I did in fact have several VST3 plugins installed, one of which is WaveShell. And it initializes OK here.
 
Although audible differences between versions seems unlikely, the only way to know with certainty would be a null test. That would require having access to both versions of each plugin in use, which you probably don't. What you could do is pick a short wave file that you could send, unprocessed, to someone who has the newer versions of the same plugins, along with detailed settings. I'd be glad to do such a test for you, but I have only a very limited collection of Waves plugins. I'm sure somebody with a more exhaustive complement of Waves plugins would step up to help.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account