vst effects stopped working

Mike-Jackson wrote on 12/26/2019, 2:45 PM

I have been a Sound Forge user since the beginning. My latest update to SF Pro 13 was working fine initially and then all of the sudden the vst effects stopped working. I can highlight audio, for instance, attempt to apply any kind of eq and nothing happens...it behaves exactly as if you had the bypass box checked. I have tried all restore points in system restore, uninstalled and re-installed countless times and still...the problem remains. I can't get anyone on the phone from Magix. Can anyone out there help me. I have 99% of a major project completed and need to apply the same post production settings to the remaining 1%. Was using Windows 7, upgraded to Windows 10 vers 1903 build 18362.535, AMD Phenom II x4 810 processor 260 GHz, 7.75 GB usable RAM. Thank you, in advance for anyone who can help me...I'm desperate! PS: Also tried previous versions of SF to no avail.

Comments

rraud wrote on 12/26/2019, 5:59 PM

Did SF work prior to the Win 10 install? Was the Win 10 installation a fresh install or an 'update' from Win 7.

Is it the same behavior with 'all' VST plug-ins? (32 bit, 64 bil; VST 2, VST 3). Is it the same behavior with VSTs in the chainer? Both modes?. Do Direct X plug-ins work?

Mike-Jackson wrote on 12/28/2019, 9:41 AM

SF behaved the same before the upgrade from Win 7 to Win 10...The program itself worked but the VST plugins suddenly stopped working. Wave hammer still works. I don't know much about plugins as far as how they work, but I did notice that when I tried to reinstall SF Pro 13 that the installation had a default location that wasn't in the 64 bit directory (it was C/Program Files/Sound Forge). Does that help? Could it be something to do with the folder the VST and Direct X plugins are installed in? Is there something to do (dragging and dropping or copying and pasting the plugins into another location)? Thank you. Sorry I didn't get back with you earlier--I got sick two days after Christmas day and am just now getting better.

rraud wrote on 12/28/2019, 2:05 PM

"I did notice that when I tried to reinstall SF Pro 13 that the installation had a default location that wasn't in the 64 bit directory"

'C/Program Files' is the 64 bit directory. "Program Files (x86)" is for 32 bit apps.
In "Options> Preferences> VST Effects", confirm the default and auxiliary plug-in VST folders are selected and the desired individual plug-ins are check-marked.
If all else fails, you can try installing the 32 bit version of SF Pro 13, I did this since some of my go-to Direct X (DX) plug-ins do not work with 64 bit hosts. Offhand, I cannot detect any speed difference using the 32 bit version of Pro 13. You can have both the 64 and 32 bit versions installed if you so desire. They share the same authorizations and most of the UI settings.
btw, Wave Hammer is a DX plug-in, as is the Noise Reduction NR-2,0 suite. Wave Hammer II, is VST.

Hope you will be fully recovered for the new year.

Mike-Jackson wrote on 12/28/2019, 7:18 PM

Thank you, brother! Problem solved. I don't know what I would have done without you. You saved me hours of having to re-learn in Adobe Audition or some other program! You are truly a life saver!

rraud wrote on 12/29/2019, 9:37 AM

Thank you, brother! Problem solved. I don't know what I would have done without you. You saved me hours of having to re-learn in Adobe Audition or some other program! You are truly a life saver!


You are welcome @Mike-Jackson. Was the problem related to the VST Effects search folders?

Have a healthy and prosperous 2020.