KVR Audio

Space Boy · Post by **Space Boy** » Sat Aug 26, 2006 8:45 am

Hi,

I have been investigating this problem recently. My (Elevayta) VST plug-ins don't show up in Sony Soundforge as VST plug-ins. However, they do show up as DirectX plug-ins (if they have been installed via the Cakewalk wrapper) and they work fine as such.

I've been fiddling around changing all sorts of things in the code (including vendor name) but Soundforge refuses to recognize my plugs as VSTs.

Has anyone had a similar problem and is there something simple I'm missing here?
Is Soundforge looking for a particular property when it scans a plug-in?

morelia · Post by **morelia** » Sat Aug 26, 2006 8:50 am

Yes. Repeatedly. That is why I think the VST implementation in SF sucks.

A possible solution though and one that worked for me. Although painful because it will bring up lots of dll's that you may not want it to. Rather than set "C:\Program Files\Steinberg\Vstplugins" as the plugins folder, try "C:\Program Files\Steinberg", or more likely to work and the one I always HAD to use "C:\Program Files". Good luck.

Space Boy · Post by **Space Boy** » Sat Aug 26, 2006 9:14 am

Morelia,

Nope. That doesn't work for me.

I point it also directly to the folder with my plugs and I even see that it is loading them while scanning. They just don't show up.

There has to be some property that it is looking for that I don't have defined.

morelia · Post by **morelia** » Sat Aug 26, 2006 9:25 am

Space Boy wrote:Morelia,

Nope. That doesn't work for me.

I point it also directly to the folder with my plugs and I even see that it is loading them while scanning. They just don't show up.

There has to be some property that it is looking for that I don't have defined.

The point you make about directing to the folder with your plugs and not seeing that it is loading them while scanning, is exactly what I used to see. It used to ignore everything from some of yours, Ozone, Wavearts, lots of freeware, Voxengo, but strangley it would sometimes detect Amplitube and one other but can't remember what it was. I really wouldn't start blaming your plugin as a first option. I emailed Sony regarding this about a year ago so I guess I should hear back soon. But I guess you have to try something. My suggestion is still to try rescanning at different directory levels. I used to scan several times and get different results each time. Sometimes even "C:\Program Files" wouldn't work but on a second or third go, all my plugins would show up.

plastique · Post by **plastique** » Sat Aug 26, 2006 1:16 pm

Maybe the old "acid method" will work. ACID (another application from Sony) stores (still does maybe ?) the scanned VSTs in the registry, and after a lot of VSTs are installed it kept to ignore newly added ones and you had to delete this registry key/folder where the VST infos were stored. Then after a new rescan all VSTs showed up.

Space Boy · Post by **Space Boy** » Mon Sep 04, 2006 6:47 pm

plastique wrote:Maybe the old "acid method" will work. ACID (another application from Sony) stores (still does maybe ?) the scanned VSTs in the registry, and after a lot of VSTs are installed it kept to ignore newly added ones and you had to delete this registry key/folder where the VST infos were stored. Then after a new rescan all VSTs showed up.

What do I search for in the registry?

plastique · Post by **plastique** » Mon Sep 04, 2006 6:49 pm

let me look, one second, gonna update this post later ...

EDIT: HKEY_CURRENT_USER\Software\Sonic Foundry\ACID\4.0\Metrics\VSTi Synth\Plugs

I guess with later versions or other applications from them it will be a path slightly similar (Sony instead etc.).
For the changes to be recognized you have/had to close the app, delete this "Plugs" folder , close regedit, restart app.

Plug-ins not showing up, as VST, in Sony Soundforge