VST plugins?

richard-amirault wrote on 5/16/2011, 4:23 PM
I've just purchase my first VST plugin. After going thru some considerable gymnastics I was able to finally successfully install them on one computer. However I can't get Vegas Pro 10 or Sound Forge 8 to recognize them.

Because of the trouble I went thru on the install and the late hour I didn't copy the location of the successfull install. Going to the software web site I found the location it should be .. when I go there in Explorer I see .prg files, not .dll files, and no matter how I tell Vegas where to look it does not see any VST plugins.

Am I doing something wrong? Running Vista 32 on this computer. Plugin format is VST 2.4

Comments

musicvid10 wrote on 5/16/2011, 5:50 PM
Vegas is going to look in c:\Program Files\VSTplugins first, unless you have changed the default location. As far a compatibility, no one will have a clue until you tell us the name of the plugin and who publishes it.
richard-amirault wrote on 5/16/2011, 7:40 PM
Yes, I left the first search location alone and added a second pointing to where I *think* the plugins were installed ... didn't work no matter where I pointed to, but I'm not 100% that where I pointed to is where they are.

That's why I mentioned the file type. From what I read on the web most plugins are .dll files. I see no new .dll files on my computer but .prg files are where I *think* the new plugins are.

The plugin is the BBE D82 Sonic Maximizer.
musicvid10 wrote on 5/16/2011, 8:35 PM
.prg file?
That sounds like something from Atari or Commodore 64 days!
Sorry I couldn't help further.
richard-amirault wrote on 12/16/2011, 7:05 AM
It's amazing what you can do when you RTFM ;-)

I found the correct folder (and file) to point to and now the plug-in works in both Vegas and Sound Forge.
rraud wrote on 12/17/2011, 11:06 AM
On most VST plugs, one only needs to paste or drag and drop the plug-in's <*.dll> file into the VST folder, usually found under 'Program files', if previously created. However some developers insist on doing an install procedure, which essentially does the same thing and occasionally in some convoluted way and, and abnormal location.. that's when problems seem to arise.
Anyway, I'm glad you were able to get it working
richard-amirault wrote on 12/18/2011, 11:24 AM
But I didn't know *where* that .dll was .. until I RTFM. There was another folder that seemed to contain the file/files .. (they were settings for the effects) .. and when I pointed to that folder nothing worked.