SF Pro 14 is erroneously looking for ARA Waves plug-ins

joe-patti wrote on 10/17/2025, 2:43 PM

I use SF Pro 14 with Waves VST (v15) plug-ins. For some reason, SFP14 is now showing Waves ARA plug-ins under FX Favorites>Waves. Of course, since I have VST the plug-ins, selecting the ARA entries results in an error. I can't seem to fix this.

I have a message in to Waves support, but have not heard back. Thanks for any help you can provide...

...joe

Comments

SP. wrote on 10/17/2025, 5:29 PM

@joe-patti Waves will probably answer you that they don't support Sound Forge. They have a list of supported software on their website.

I think it's caused by a problem with the way Sound Forge handled ARA plugins in the past. I've tested the Sound Forge Pro 18 trial some time ago and that was the first version that seems to show ARA plugins correctly.

You could try to install the Sound Forge Pro 18 trial on your computer and then copy the different audio_plugin_scan_server EXE files from the SF 18 directory to your SF 14 directory (make a backup of your files first!). Those newer file versions might solve the problem. If this doesn't work, you could try how the Waves plugins work in the SF 18 trial itself.

joe-patti wrote on 10/24/2025, 4:08 PM

Indeed, Waves doesn't support SF any longer. They used to, but no longer. That said, they did provide some things to try. But nothing worked. I did send a message to Magix support, but have yet to hear back from a real person. Only an AI bot with a nonsense answer. Very frustrating as this SFP14/Waves VST3 combo used to work. And having been exposed to the more recent versions of SF at work, I'd rather not upgrade past 14 for my use.

Any other ideas? Just to clarify, I want SFP14 to recognize the VST3 versions of the plug-ins...

SP. wrote on 10/24/2025, 5:11 PM

@joe-patti Like I mentioned, install the free Sound Forge Pro 18 trial and copy the audio_plugin_scan_server EXE files from the SF 18 directory to your SF 14 directory (make a backup of your files first!).

This workaround already helped other users with plugin problems, for example here: https://www.magix.info/us/forum/ozone-12-advanced-plugin-not-recognized-in-sound-forge-audio-studio-17--1349679/