• SONAR
  • Replace Missing Plugin
2011/08/22 05:10:12
Mr.Oscar.Edward
Hi, I have a Sonar X1 project with a waves plug: Waves VEQ4 Mono/Stereo When I open the project in my Sonar X1c I get the Missing Plugins window indicating that Waves VEQ4 Stereo and Waves VEQ4 Mono are missing! I do believe I have installed Waves 7 and I can open the above plugs! So I found that the project was using an older version of Waves! Since the original plugin name in project is Waves VEQ4 but I have VEQ4 installed! So these must be the same. My question is that how can force Sonar to open new VEQ4 instead of old Waves VEQ4 used in the project? Of course the plugin settings are vital to me, otherwise I could just remove and re-insert the plug! Thank you!
2011/08/22 06:43:07
deanx
Sorry to jump on your thread MR.Oscar.Edward but I have a similar issue.

When I launch projects made in 8.5.3 on 32 bit I keep getting a missing plugin for Ampltitube 3. I remap to the new file path for 64 bit plug ins and Amplitube is found straight away. I save an X1 project but on relaunch it just comes back and for every projectc created on my onld 32 bit system.

It's not life threatening as it only takes 2 seconds to remap, just a bit annoying, I thought saving would remember the new file path for Amplitube .dll file.

Thanks
Dean
2011/08/22 07:01:42
John T
As far as Sonar is concerned (and I think this may be general to VST), a 64 bit version and a 32 bit version of a plug in are not the same. If your old project uses a 32 bit plug in, that's what Sonar will look for. It's not a question of "remembering"; as far as Sonar is concerned, you've replaced plug in X with plug in Y, and plug in Y could be anything.
2011/08/22 07:12:25
Mr.Oscar.Edward
My main DAW is NOT Sonar and I only use it when I really have to! I even don't like to open Sonar because its x64 version is very fussy about plugs! But now, unfortunately I have to open this project and my problem still exists. And I cannot install the 32-bit version :(
2011/08/22 07:14:25
Mr.Oscar.Edward
Well, thank you John, so we suppose X is different as Y, while they are the same plugin but only different version or platform. However I need the old one's settings to map to the new one, is there a way you think?
2011/08/22 07:54:31
John T
I've never found one other than writing them down and re-entering them. However, if you still have the 32 bit version of the plug in, and you set up Sonar 64 bit to scan for that, it should just find it and bit bridge it.
2011/08/22 08:17:30
Noel Borthwick [Cakewalk]
Projects saved in eith the 32 or 64 bit version of SONAR should open fine in each other. The plugins ID should be identical on both unless the vendor specifically coded them not to be.
Normally opening a project saved with an older version of a plugin should load the new plugin automatically. SONAR tolerates minor changes in the plugin file name, (if there is a conflict you will get a dialog asking you to choose the plugin) but if the vendor changes the VST ID for the new version it will show up as missing.
2011/08/22 08:31:15
Mr.Oscar.Edward
Yep Noel, the different in old and new VST is not the platform (32-64-bit). But it's in the version. However, my research revealed that VST ID / CLSID is changed! OK isn't there any way to read the previous settings now?
2011/08/22 08:33:05
mrfitz
You can't open the old version, save the plug in settings as a preset and then load them into the new version?
2011/08/22 08:45:36
Mr.Oscar.Edward
Hey dude, if I had the old version plug, I wouldn't need to save its settings :(
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account