"Missing Plug-in" in Sonar

[davekershaw]

I've loaded everything up in Sonar 64 bit, and the plugins are working, but I'm getting a "Missing Plug-in"
message when I start up my old projects. I can re-insert the same plugin, but can't remember each effect setting that was used previously.

I know this is caused my the plugin not being installed to it's original place, but I've tried reinstalling the plugins
where I thought they should have been, and tried moving the .dll files to different locations, but I still get the same message.
Is there any way of changing the location of the plugin in sonar and recovering it's settings?
Has anyone had this problem and found a work around?

[Len911]

When you get a "missing plug-in" message, does it offer you the option of searching or browsing for it? It should, and you should just insert the new path, for example, J/sonar/vst/goobercompressor.

Moving the dll files to new locations and opening up a new instance of a plugin isn't going to recall your old settings because it is a new instance.

In other words, when and where it tells you you are missing the plugin, you have to at that spot and time and place redirect and either search for the new path to your plugin in the new place or add it manually if you know where it is. Opening up another plugin in a different slot will not recall your previous settings, it just opens up another fresh and new plugin. Your sonar project contains the settings for your plugin, not the plugin itself, and it has to be the same plugin in the same slot, right,it doesn't save the settings in slot 1 for plugin A, to slot 2. Same with an audio file. If you were in Sonar in a project file called "Devil", and on track 1 you had a wave file with all your settings, and it was stored on the C drive, and you moved that audio file to your D drive, when you opened the Sonar project "Devil", it would say audio file missing, then you would redirect the path to your D drive and it would search and find it or you could manually make the path. If you found the wave file and put it on track 2, you would have to either move the wave to track 1 or redo all your settings from track 1 to track 2.
If you just close the missing plugin message and just open up another plugin instance that will also clear out the settings you had before.

[davekershaw]

When you get a "missing plug-in" message, does it offer you the option of searching or browsing for it? It should, and you should just insert the new path, for example, J/sonar/vst/goobercompressor.

Thanks Len.

There is, unfortunately, no option to search for the new location. That would indeed be ideal, and is exactly what I have done before when a wave file has been moved.

All I'm getting is a "Cakewalk Missing Plug-in stand-In" with the message "This plug-in is missing or improperly installed on your system.
The original plug-in state is saved by this stand-in, and will be restored if you save the project and subsequently load it on a system where the plug-in is properly istalled"
The stand-in offers no settings of any kind.

Thanks for the suggestions though.
Dave.

[rld]

I've had that happen on occasion. I've fixed it but I can't remember exactly how I did it.
Can you insert the plugin on a new project?
If so, then look at the exact name of the plugin in the fx bin and compare to the one that won't load.
That might give you a clue.
if you can't load in a new project, then your plugin installation is messed up.

EDIT:
I just re read your OP and you can install the plug in apparently.
Still, compare its name with the one that gets the error.
Don't know what plug this is but settings are sometimes saved with certain extensions.
Is this a new computer?

[davekershaw]

I've had that happen on occasion. I've fixed it but I can't remember exactly how I did it.
Can you insert the plugin on a new project?
If so, then look at the exact name of the plugin in the fx bin and compare to the one that won't load.
That might give you a clue.
if you can't load in a new project, then your plugin installation is messed up.

EDIT:
I just re read your OP and you can install the plug in apparently.
Still, compare its name with the one that gets the error.
Don't know what plug this is but settings are sometimes saved with certain extensions.
Is this a new computer?

Yes, it is a new computer.
As I've loaded Sonar 64 bit, it's installed old plugins to Program Files (x86) which may account
for the problem, but I've tried re-installing and moving the plugins and it still won't work.

[brindabella]

Go to the Cakewalk forum, I've solved a few snafus there.

http://forum.cakewalk.com/default.aspx

[davekershaw]

Go to the Cakewalk forum, I've solved a few snafus there.

http://forum.cakewalk.com/default.aspx

I've been searching there, but not found a solution other than those already suggested.
I've got X1 on order. It would be nice if that had the ability to re-assign plugins!
Should be here in a few days.

But thanks anyway Laura.

[Len911]

I wonder if it's because the plugins were 32 bit and you are using sonar 64 bit? I am not sure but isn't there a plugin bridge or something you have to use with 32bit plugins on a 64 bit system?
I just saw this thread, sonar comes with bitbridge and is automatic, but some plugins prefer Jbridge.

http://www.gearslutz.com/board/music-co ... ugins.html

[rnrmachine]

Hey Dave,

The problem is probably due to, Sonar is looking for 32bit versions of the plugins and now it has to look for them through "bit bridge" IF there is no 64bit version. I wish I knew what you could do to remedy this. I looked through Sonar at everything there is... and I found nothing. IF there is a way to open the projects on your old system. Save the Plugin Presets into one folder then transfer them to the new system. It's a fair amount of work but at least you will have them. You can import/export them through the Plugin Manager. Different presets will require different scenarios. Cakewalk plugins you need to use the import/export. Other plugins you can just browse to the preset.

It also is probably due to being a new system as well as 64bit. If all the info don't match up perfectly Sonar thinks it can't find the plugin even IF you put it in the exact same file location. I am sure there is a work around for this but it's probably in the code of each project. IF only there was a "missing plugin" redirect like Len said. Sonar does it for samples but plugins... nada.

In the future I highly recommend saving all presets within the individual project folders.

Rob

[rld]

Yeah...Like Rob I was gonna suggest if you still have your old c: drive handy, you may be able to find out where your old presets are stored.
I always add my old C:drive to my new systems, or put it in a external case so I can access and search it till things get working properly.