BUG: Moving Plugin DLL's

[Dan Duskin]

If you are using Cubase or Nuendo, and you move the older UAD-1 plugins to a new sub-folder, they will not work properly anymore... i.e., you will get an error when you load Cubase/Nuendo for every moved plugin, and the GUI will no longer display. This is true for the EX-1, CS-1, DM, and other original OLD plugins.

 

[Mark Edmonds]

Dan - I don't think it is really a bug. There are just interdependencies between the dlls so you have to move them in a block. Long time ago, I tried organising them by functionality rather than name and had the same problem you've got. It isn't a bug, it is just a requirement of the installation.

Mark

 

[Dan Duskin]

errrr.... no.... i call that a bug.

the vst spec states that you should be able to organize the dlls into any subfolder you like

 

[Hexagon]

It works for 'ordinary' VST dlls but UAD-1 dlls being hardware dependant will have registry settings referring to the exact path for the dlls. Moving them breaks the settings, hence the error messages and no GUI.

Hex

 

[Mark Edmonds]

errrr.... no.... i call that a bug.

the vst spec states that you should be able to organize the dlls into any subfolder you like

OK, I'm going to call you on that one. Can you provide the exact text that states this please?

Another point: file dependencies may get broken when moving dlls to new directories. If the plugin expects files at the same location and files are moved, it will obviously fail. This isn't a bug. This is because the user has broken the installation!

Mark

 

[Mark Edmonds]

It works for 'ordinary' VST dlls but UAD-1 dlls being hardware dependant will have registry settings referring to the exact path for the dlls. Moving them breaks the settings, hence the error messages and no GUI.

Hex

The same logic can apply to any plugin, not just UADs. It all depends what is done during installation and the plugins requirements for external dependencies. Why should hardware dependency alone determine the need for file paths in the registry? :?: :?:

Mark

 

[Hexagon]

It works for 'ordinary' VST dlls but UAD-1 dlls being hardware dependant will have registry settings referring to the exact path for the dlls. Moving them breaks the settings, hence the error messages and no GUI.

Hex

The same logic can apply to any plugin, not just UADs. It all depends what is done during installation and the plugins requirements for external dependencies. Why should hardware dependency alone determine the need for file paths in the registry? :?: :?:

Mark

It's of course not hardware dependecy alone that dictates whether a dll can be moved successfully or not, but moving UAD-1 dlls was the topic Dan raised.

Dlls without an installer can be moved without any problems except Cubase may not be too happy about it when opening a project with references to it. (Which can easily be rectified if there are only a few references to it.)

Plugins with an installer can be more unpredictable. Some plugins have an installer because it contains several versions of the plugin, like DX(i), RTAS or AudioUnit in addition to the VST(i). Moving the dll in the VSTplugin folder may only break the uninstall routine but it can also break the plugin.
Proceed with caution!

All the best.
Hex

 

[secretworld]

Sorry but it´s a different problem. It´s that sub plugins like the delay or reverb part from the channelstrip are dependant on the main CS.dll. So if you wan´t to move them, you can, but you have to make shure the all plugs that are derived from the channelstrip are in the same folder. Same goes for nigel and it´s smaller plugs. It works like this, I checked. So it´s no installer or regestry thing, the dll´s of related plugs must be on the same level.
Good luck and happy organising!

Same goes for other vst plugins that seem to break when moved. Most of the time there is a second file or folder wich needs to be moved too. F.E. a preset folder or dat file. I have never experienced a plugin that in the end couldn´t be moved. DX files can never be moved. the are read from the registry with a pointer to their location.

 

[Dan Duskin]

Now THAT'S interesting! (the channel strip thing)

i'm going to run some tests now

i really want to put...
CS-1 in my \"channel strips\" directory
EX-1 in my \"dynamics\" directory (cause i don't use the eq on it)
DM1 in my \"modulation\" directory
gatecomp in my \"dynamics\" directory
preflex in my \"guitar stuff\" directory
etc...

 

[Dan Duskin]

I got it to work! It was tricky.... but I did it!
I fooled my UAD

 

[Akis]

How?

 

[homestudio]

yes I would like to knows How ?
:wink:

 

[Dan Duskin]

here's the trick...

the EX-1, EX-1M, DM-1, DM-1L, and RS-1 all require that the CS-1 be in the same directory. so i copied the CS-1 and put it in every directory i had the above plugins in. did the same with nigel and it's components.

to keep from seeing multiple copies of plugins, i disabled them using the plugin manager in nuendo. i then renamed the CS-1 and Nigel copies i wanted to refererence... and, walla!

 

[Mark Edmonds]

The word is voila :roll:

Glad you got it working though!

Mark

 

[Hexagon]

I'm glad you got it sorted too Dan. Thanks to secretworld for your input.

It would be so much better if Nuendo/Cubase would let us organize the plugin list this way without having to move dlls around.

Hex

 

[homestudio]

or like wavelab do :wink:
how did you rename the plug :?
:wink:

 

[Dan Duskin]

how did you rename the plug :?
:wink:

filename (the dll)