Community Forums Archive

Go Back

Subject:SF8 doesn't recognize BIAS Sound Soap 2 VST
Posted by: JohnnyRoy
Date:2/18/2006 10:14:58 AM

I can’t get Sound Forge 8 to recognize the BIAS Sound Soap 2 VST. It is recognized by Vegas 6 and ACID Pro 5 but not Sound Forge 8. I have totally uninstalled and reinstalled SF8 but nothing seems to work.

Does anyone have a registry hack or something to get SF8 to recognize a VST that all other Sony products can see?

~jr

Subject:RE: SF8 doesn't recognize BIAS Sound Soap 2 VST
Reply by: ForumAdmin
Date:2/20/2006 7:31:12 AM

Have you tried Options->Preferences->VST Effects->Refresh?

J.

Subject:RE: SF8 doesn't recognize BIAS Sound Soap 2 V
Reply by: JohnnyRoy
Date:2/20/2006 12:17:30 PM

Yup. Refresh was the first thing I tried. That’s why I was looking for a registry hack or something. ACID has the same problem with VSTi’s and you need to delete a registry key to get to work properly. I was hoping there was something similar for Sound Forge or can I copy a Vegas or ACID key over to get SF to work because they have no problem finding it and the BIAS SoundSoap VST.dll is in my C:\Program Files\VSTplugins directory.

Does Sound Forge have a black list? Is it possible this VST got black listed somehow and SF is skipping over it?

~jr

Subject:RE: SF8 doesn't recognize BIAS Sound Soap 2 V
Reply by: JohnnyRoy
Date:2/20/2006 1:21:51 PM

OK, I found the registry hack!

Apparently the flags were set wrong. I looked under:

HKEY_CURRENT_USER\Software\Sony Media Software\Sound Forge\8.0\Metrics\VstCache\Mappings

And found the entry for BIAS Sound Soap. The Flags key was set to hex 0x10 (16). I noticed all the other audio VST’s were set to 0x0E (14). I changed the flag for BIAS Sound Soap to 0x0E and it showed up and is working properly. Hooray!!!

Sony, hopefully this is enough information to figure out why your refresh didn't work or what a flag value of 0x10 means.

~jr

Message last edited on2/20/2006 1:22:38 PM byJohnnyRoy.
Subject:RE: SF8 doesn't recognize BIAS Sound Soap 2 V
Reply by: ForumAdmin
Date:2/21/2006 7:55:27 AM

It means the plug-in crashed or hung at some point during enumeration. I've seen several VSTs crash when closed iimmediately after they are opened, which is probably what happened here.

Future updates will tolerate this and will also not hide the plug-in on the prefs page.

J.

Message last edited on2/21/2006 7:56:02 AM byForumAdmin.

Go Back