Waves Plugins V15 do not work in Sound Forge Pro V17

Roy-Weinberg wrote on 6/24/2024, 12:35 PM

I just updated ten of my numerous Waves Plugins to V15.

Sound Forge Pro V17 will not display a dialog box for any of them although they appear in the menu.

Waves Plugins V14 and earlier do work properly.

Yes, the Waves Plugins V15 are properly installed.

Yes, the Waves Plugins V15 work properly in Cakewalk by Bandlab.

Yes, the Waves Plugins V15 work properly in Audacity,

Yes, I rescanned the VST folders and the V15 Waves Plugins are detected.

It appears to be a problem with Sound Forge Pro V17.

NOTE: Waves suggested that they 'improved' their graphics in some of their V15 plugins.

No, I am not upgrading to Sound Forge Pro V18 because none of the 'improvements' are anything that I would use.

Any ideas?

Comments

SP. wrote on 6/24/2024, 12:38 PM

@Roy-Weinberg Does your graphics card support the newest Waves GUIs? Do the plugins display correctly in other audio software?

john_barr wrote on 6/24/2024, 12:43 PM

Waves v15.

VST2 support has not been updated in the latest version and will not be available in future releases.

Sound Forge doesn't work very well with VST3 plugins.

Roy-Weinberg wrote on 6/24/2024, 6:20 PM

@Roy-Weinberg Does your graphics card support the newest Waves GUIs? Do the plugins display correctly in other audio software?

Yes, the Waves Plugins V15 work properly in Cakewalk by Bandlab.

Yes, the Waves Plugins V15 work properly in Audacity,

SP. wrote on 6/25/2024, 12:58 AM

@Roy-Weinberg The only other idea I have is to rescan the VST path in the program preferences of Sound Forge and to reset the program settings under the File menu..

john_barr wrote on 6/25/2024, 6:44 AM

@SP.

Rescan VST path and reset the program preferences won't help. I sent an email to Magix Support and they said they will improve support and performance VST3. So, let's wait.

rraud wrote on 6/25/2024, 9:06 AM

VST2 support has not been updated in the latest version

The third-party 32 bit VST 2 display bug in SF 16/17 was addressed in SFP-18. 'Most' display properly now.

john_barr wrote on 6/25/2024, 10:03 AM

@rraud

Waves plugins will no longer support VST2.

https://www.waves.com/downloads/release-notes#v15

Roy-Weinberg wrote on 6/25/2024, 4:33 PM

I downloaded a 30 day trial version of Sound Forge Pro V18 and the Waves V15 plugins work just fine.

Magix currently wants $200 for the upgrade to Sound Forge Pro V18. That is ludicrous. I haven't used any of the new features when I updated to Sound Forge Pro V17. And Sound Forge Pro V18 does not offer anything new that I plan to use. It would be cheaper to purchase X-Noise V14 from Waves (the only plugin I use in Sound Forge) for $30.

john_barr wrote on 6/25/2024, 7:10 PM

Sound Forge is expensive for what it offers. And the problems that haven't been fixed yet.

Roy-Weinberg wrote on 6/26/2024, 10:49 AM

When Sony owned Sound Forge updates were $99.

rraud wrote on 6/27/2024, 9:23 AM

When Sony owned Sound Forge updates were $99.

Inflation.. have you been to the supermarket or shopping in general lately?

Philip-White wrote on 12/7/2024, 11:04 AM

Are Waves plugins only compatible with SF 18 in the 32-bit version? I can't get them to work in the 64 bit.

rraud wrote on 12/8/2024, 10:57 AM

There is not a 32 bit version of Sound Forge 18.. unlike the other Magix versions of SF which had an option to choose installing one or both, AFAIK, all the 'current' Waves plug-ins are 64 bit only.
The display issue with third-party 32 bit plug-ins that plagued 64 bit SF-16 and 17 was (mostly) resolved with SFP-18. Unfortunately, that issue still exists in the later builds of Vegas.